create-invokta-engine

Create a standalone TypeScript Action Engine with one deterministic capability and a selected execution profile. Every generated entry point imports the same engine and reaches capability execution through engine.invoke or an official Invokta adapter.

Commands

create-invokta-engine [project-directory]
  [--profile complete|mcp-stdio|mcp-http|cli]
  [--package-manager npm|pnpm|yarn]
  [--no-install]
  [--yes]
create-invokta-engine --help
create-invokta-engine --version

The npm initializer shorthand resolves to this package:

npm create invokta-engine@latest my-engine

When standard input and standard error are TTYs, the command asks for a missing project directory and profile, displays the normalized plan, and requires a final confirmation before writing. An explicit target or profile skips only its question. --yes requires an explicit target and skips every prompt.

Non-terminal execution never prompts or reads standard input. It requires an explicit target and uses complete when --profile is omitted, preserving automation such as:

create-invokta-engine my-engine --no-install

Terminal automation should make its choices explicit:

create-invokta-engine my-engine --profile complete --no-install --yes

The invoking package manager is inferred from npm_config_user_agent, with npm as the fallback. Use --package-manager to choose explicitly. --no-install generates the selected files without starting a process or network operation.

Profiles

| Profile | Execution channels | Entries | | --- | --- | ---: | | complete | Direct, CLI, MCP local over stdio, MCP HTTP | 21 | | mcp-stdio | Direct, MCP local over stdio | 15 | | mcp-http | Direct, MCP HTTP | 18 | | cli | Direct, CLI | 14 |

Every profile contains these common entries:

.agents/skills/develop-invokta-project/SKILL.md
.agents/skills/develop-invokta-project/agents/openai.yaml
.gitignore
AGENTS.md
CLAUDE.md -> AGENTS.md
README.md
package.json
src/capabilities/create-welcome-message.ts
src/direct.ts
src/engine.ts
test/engine.test.ts
tsconfig.json
tsconfig.test.json

CLI adds src/cli.ts and @invokta/cli. MCP local adds invokta.mcp.json, src/mcp-stdio.ts, @invokta/mcp, @invokta/installer, and its stdio/install/uninstall scripts. MCP HTTP adds .env.example, invokta.deploy.json, src/env.ts, src/http-auth.ts, src/mcp-http.ts, @invokta/mcp, @invokta/deploy, and its HTTP/package/probe scripts. Dependencies are set unions and appear once.

HTTP scaffold bytes come from the pure public @invokta/deploy/scaffold planner. The creator merges the complete plan before writing and never runs the deploy CLI. The generated authentication hook fails closed until implemented, and HTTP profiles ignore .env and .env.* while retaining .env.example.

Generated README.md, AGENTS.md, and develop-invokta-project skill guidance describe only the selected channels. CLAUDE.md is a real relative symbolic link to AGENTS.md; unsupported link creation fails and rolls back rather than copying the instructions. Generated Invokta dependencies exactly match the creator version. All generated entries become project-owned and are never updated in place.

Prompt and target safety

Each answer is strict UTF-8 and limited to 4,096 encoded bytes including the line terminator. The directory and profile questions allow three invalid answers. Confirmation accepts case-insensitive y, yes, n, or no; an empty confirmation means no. A negative confirmation writes Creation cancelled. No files were created. and performs no filesystem, process, or network operation.

The target must be relative, absent or an empty real directory. Absolute paths, parent segments, symbolic-link components, non-directories, and non-empty targets are refused. The creator preflights before confirmation and revalidates afterward. Files and the instruction symlink use exclusive creation; a write failure rolls back only entries created by that invocation. Unicode control, format, line-separator, and paragraph-separator characters in an accepted parent path are escaped in the confirmation instead of being emitted as terminal-active text.

Unless --no-install is present, exactly one shell-free foreground package manager install starts after every selected scaffold entry exists. An install failure preserves the complete generated profile for retry.

Exit codes and diagnostics

| Exit | Meaning | | ---: | --- | | 0 | Help, version, creation, or normal cancellation succeeded | | 1 | Prompt interruption, target safety, filesystem, or installation failed | | 2 | Usage, required interaction, prompt input, path, or name was invalid |

Creator diagnostics are INTERACTIVE_REQUIRED, PROMPT_INVALID, PROMPT_ABORTED, TARGET_INVALID, TARGET_UNSAFE, TARGET_NOT_EMPTY, SCAFFOLD_CONFLICT, WRITE_FAILED, and INSTALL_FAILED. They never include a rejected answer or argument, environment value, child error, stack, or cause.