From vibe-generate
Scaffold a new project from a template using vibe-generate. Use when the user wants to create a new project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vibe-generate:new [template] [project-name] [output-dir][template] [project-name] [output-dir]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffold a new project using the `vibe-generate` CLI tool.
Scaffold a new project using the vibe-generate CLI tool.
The user may provide: $ARGUMENTS
Parse the arguments to determine:
nextjs, rust-1.9, java-25)First, make sure vibe-generate is installed. If not, install it:
cargo install --git https://github.com/tiktuzki/project-templates vibe-generate
If no arguments were provided, or they're incomplete, first list available templates:
vibe-generate --help
Then ask the user which template and project name they want.
If both template and name are clear from the arguments, run:
vibe-generate --template <template> --name <name>
If the user specified an output directory, add --output-dir <path>.
After scaffolding, read the generated project's CLAUDE.md to understand the stack, then give the user a brief summary of what was created and suggest next steps (e.g., cd <name> && npm install or cargo build).
/vibe-generate:new nextjs my-app -> vibe-generate --template nextjs --name my-app/vibe-generate:new rust-1.9 my-cli -> vibe-generate --template rust-1.9 --name my-cli/vibe-generate:new java-25 my-service ~/projects -> vibe-generate --template java-25 --name my-service --output-dir ~/projects/vibe-generate:new (no args) -> list templates and ask user interactivelynpx claudepluginhub tiktzuki/project-templates --plugin vibe-generateGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.