New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Build a New-Project Slice

by KhazP in KhazP/vibe-coding-prompt-template

Builds one working slice of a new project from the brief, runs the affected checks and the user journey, and reports what was and was not verified.

MITAuto-check: notesDevelopment

Install Build a New-Project Slice

skills CLI
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install KhazP/vibe-coding-prompt-template vibe-build --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vibe-build .claude/skills/vibe-build && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-build
GitHub stars
3.1k
Token cost
~353 tokens
SKILL.md length
173 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Builds one working slice of a new project from the brief, runs the affected checks and the user journey, and reports what was and was not verified.

  • Starting a new project and implementing its first feature slice end to end
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Making sure a new feature works as a user would see it, not just that it builds
  • Getting an honest report of what was checked and what remains unverified

What it does

This skill takes one slice of a new project from brief to working behavior. The agent first fixes the requested outcome and acceptance criteria from your brief and earlier project decisions, reads the repository instructions and only the documents that slice needs, and treats a missing or stale MEMORY.md as no reason to rebuild the whole planning workflow. It then implements the behavior with the chosen stack, keeps unrelated work intact and makes a recovery checkpoint when the change is big enough to warrant one.

Accounts, databases, infrastructure, paid services and AI features are added only when requirements justify them, and work continues until the slice truly works, not merely until files exist. The agent runs the checks the change affects and, where runtime access allows, walks the relevant user journey, since a passing build does not prove interactive behavior. It separates failures it caused from older ones, updates progress notes where the repository keeps them, and reports the outcome, checks run, unverified behavior and blockers. Sending anything externally, changing production, submitting to a store and deploying still need your authorization for that specific effect.

When your agent uses it

  • Starting a new project and implementing its first feature slice end to end
  • Making sure a new feature works as a user would see it, not just that it builds
  • Getting an honest report of what was checked and what remains unverified

Example prompts

  • “Build the signup and login slice for the new app from the brief in docs/brief.md, and check the user journey.”
  • “Implement the first screen of the habit tracker and tell me what you verified.”
  • “Add the checkout slice, run the affected tests and report any pre-existing failures separately.”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

What it can do on your machine

Read from SKILL.md and the folder at commit d26fb0d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • Bash
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Build a New-Project Slice loads about 353 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 173 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~353

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from KhazP/vibe-coding-prompt-template at commit d26fb0d, republished under its MIT licence (© KhazP). 173 words, ~353 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-build/SKILL.md (or your agent's skills folder).
name
vibe-build
description
Implement a new-project slice through the relevant checks and working user journey.
allowed-tools
Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

Build a new-project slice

Establish the requested outcome and acceptance criteria from the user's brief and relevant project decisions. Read applicable repository instructions and only the documents needed for this slice. An absent or stale MEMORY.md does not require rebuilding the whole planning workflow.

Implement the intended behavior using the chosen stack. Preserve unrelated work and make a recovery checkpoint when the change warrants it. Add accounts, databases, infrastructure, paid services, and AI only when requirements justify them. Continue until the requested slice works, not merely until files exist.

Use the project's affected checks and exercise the relevant user journey when runtime access permits it. Fix failures caused by the change, distinguish pre-existing failures, and reuse results that remain valid. A setup validator or passing build alone is not evidence of interactive behavior.

Update project progress when the repository maintains it. Report the outcome, actual checks, unverified behavior, and any concrete blocker or recovery note. External sends, production changes, store submission, and deployment remain subject to authorization for their specific effect and target.

© KhazP, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/vibe-build of KhazP/vibe-coding-prompt-template.

Open the folder on GitHubat commit d26fb0d

Compare with similar skills

Build a New-Project Slice next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Build a New-Project Slice compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Build a New-Project Slice this skillKhazP/vibe-coding-prompt-template3.1k—~353Automated safety check: NotesMIT
Bulletproof Workflowartemiimillier/bulletproof153—~3.5kAutomated safety check: PassMIT
Spec-Driven Feature Developmenttech-leads-club/agent-skills7k—~4.3kAutomated safety check: PassCC-BY-4.0
TLC Implementtech-leads-club/agent-skills7k—~4.3kAutomated safety check: PassCC-BY-4.0
Task Workflowikarenkov/Modo343—~2.4kAutomated safety check: PassNone
Spec Drift CheckJuliusBrussee/cavekit1.2k—~666Automated safety check: PassMIT

Similar skills

  • Bulletproof Workflow

    artemiimillier/bulletproof

    Applies a 12-stage verified workflow, from research to deploy, to non-trivial coding tasks, scaled to lightweight, standard or full mode by task size.

    153 GitHub stars~3.5k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed

  • Spec-Driven Feature Development

    tech-leads-club/agent-skills

    Plans and implements a feature through four phases, specify, design, tasks and execute, with testable requirements, atomic commits and a separate verifier checking the work.

    7k GitHub stars~4.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • TLC Implement

    tech-leads-club/agent-skills

    Turns an already-planned ticket or spec into a checklist, builds it, and has a fresh verifier agent prove each check independently.

    7k GitHub stars~4.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Task Workflow

    ikarenkov/Modo

    Spec-driven workflow for non-trivial work. An agent skill from ikarenkov/Modo.

    343 GitHub stars~2.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Spec Drift Check

    JuliusBrussee/cavekit

    Read-only detector that compares SPEC.md with the code and reports invariant, interface and task drift grouped by severity, without changing anything.

    1.2k GitHub stars~666 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • agtx Execute Phase

    fynnfluegge/agtx

    Carries out an approved plan for an agtx-managed task: implements the changes, runs tests, commits, writes a summary to .agtx/execute.md and then stops.

    1.7k GitHub stars~439 tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed

More from KhazP/vibe-coding-prompt-template

All 11 skills in this repo

  • MVP Product Requirements Writer

    KhazP/vibe-coding-prompt-template

    Writes or revises an MVP product requirements document, sized to the product, with observable acceptance criteria and no repeated questions.

    3.1k GitHub stars~455 tokensUpdated 5 days ago
    Auto-check passed

  • Vibe Research

    KhazP/vibe-coding-prompt-template

    Researches an app idea or settles product and technical uncertainties before a design is fixed, and saves the findings with a handoff for the next stage.

    3.1k GitHub stars~473 tokensUpdated 5 days ago
    Auto-check passed

  • MVP Technical Design

    KhazP/vibe-coding-prompt-template

    Writes an MVP technical design from agreed requirements, covering architecture, data ownership, integration contracts, deployment and tradeoffs, then hands off to the next stage.

    3.1k GitHub stars~512 tokensUpdated 5 days ago
    Auto-check passed

  • Vibe Debug

    KhazP/vibe-coding-prompt-template

    A short debugging procedure for an existing project: reproduce the failure, test one hypothesis at a time, make the smallest fix, add a regression check and re-verify.

    3.1k GitHub stars~403 tokensUpdated 5 days ago
    Auto-check: notes

  • Vibe Workflow Router

    KhazP/vibe-coding-prompt-template

    Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.

    3.1k GitHub stars~544 tokensUpdated 5 days ago
    Auto-check: notes

  • Vibe Agents Instructions

    KhazP/vibe-coding-prompt-template

    Writes project agent instructions and tool setup from decided requirements and the existing repo, keeping only stable, non-obvious guidance in always-loaded files.

    3.1k GitHub stars~421 tokensUpdated 5 days ago
    Auto-check: notes

Categories

Questions about Build a New-Project Slice

What does Build a New-Project Slice do?

Builds one working slice of a new project from the brief, runs the affected checks and the user journey, and reports what was and was not verified. This skill takes one slice of a new project from brief to working behavior.md as no reason to rebuild the whole planning workflow.

When should I use Build a New-Project Slice?

Build a New-Project Slice fits situations like: starting a new project and implementing its first feature slice end to end; making sure a new feature works as a user would see it, not just that it builds; getting an honest report of what was checked and what remains unverified.

How do I install Build a New-Project Slice in Claude Code?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a claude-code`. Or copy the skill folder (.agents/skills/vibe-build in KhazP/vibe-coding-prompt-template) into .claude/skills/vibe-build in your project. Claude Code loads it when a task matches its description.

How do I install Build a New-Project Slice in Codex?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a codex`. Or copy the skill folder (.agents/skills/vibe-build in KhazP/vibe-coding-prompt-template) into .agents/skills/vibe-build in your project. Codex loads it when a task matches its description.

Can I use Build a New-Project Slice in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-build, .gemini/skills/vibe-build, .github/skills/vibe-build and .opencode/skills/vibe-build in your project.

What does Build a New-Project Slice need to run?

SKILL.md names no scripts, command-line tools or credentials: Build a New-Project Slice is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion.

Does Build a New-Project Slice access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Build a New-Project Slice safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Build a New-Project Slice use?

Build a New-Project Slice is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build a New-Project Slice use?

About 353 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Build a New-Project Slice?

Skills that share tags, products or a category with Build a New-Project Slice: Bulletproof Workflow (artemiimillier/bulletproof, 153 stars), Spec-Driven Feature Development (tech-leads-club/agent-skills, 7k stars), TLC Implement (tech-leads-club/agent-skills, 7k stars) and Task Workflow (ikarenkov/Modo, 343 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build a New-Project Slice?

KhazP (a GitHub user) maintains it in KhazP/vibe-coding-prompt-template, which has 3,131 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 4, 2026.

Source: KhazP/vibe-coding-prompt-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.