@mauriciodmo/create-framekit

Scaffold a new FrameKit project with one command:

pnpm dlx @mauriciodmo/create-framekit my-project
cd my-project
pnpm dev

The creator is interactive: if no project name is given, it asks for one. It detects which package manager you are using from your environment (pnpm or npm); if it cannot detect it, it asks you to choose. It then asks whether to install dependencies, and if you are using pnpm, whether to run pnpm approve-builds. Finally, it asks whether to initialize a Git repository with an initial commit.

Use -y to accept all questions or -n to reject them all. When either flag is used without a project name, the project is created in ./framekit; an undetected package manager defaults to pnpm in this non-interactive mode.

pnpm dlx @mauriciodmo/create-framekit -y
pnpm dlx @mauriciodmo/create-framekit my-project -n

After copying the template, the creator runs install and framekit generate automatically if you chose to install dependencies. If either step fails, the partially-created project directory is preserved so you can diagnose the issue.

To update the official agent skills in an existing project, run this from the project root:

pnpm dlx @mauriciodmo/[email protected] update-skills

You can pass another project directory as the second argument. The command replaces the official FrameKit skills, removes the legacy framekit-project-setup, framekit-studio-usage, and framekit-template-creation directories, and preserves other skill directories.

For template authoring patterns, see the Template Authoring Guide.

For full documentation:

• Documentation
• Documentación

Test locally

From the repository root, build and run the local CLI without publishing it:

pnpm --filter @mauriciodmo/create-framekit build && node packages/create-framekit/dist/cli.js ./my-local-framekit