smithery.ai

vibe-agents

Generate project agent instructions from agreed requirements and technical decisions. Not for ordinary incremental feature changes.

First seen Mar 17, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Edit, Glob, Grep, Bash, AskUserQuestion

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,382 B
  • docs SUMMARY.md 239 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Vibe Agents

Read the agreed PRD and Tech Design using vibe.project.json paths when available; otherwise inspect docs/PRD--MVP.md and docs/TechDesign--MVP.md. Reconcile conflicts and reuse Handoff Context before asking anything.

Run npx vibeworkflow --dry-run --json to inspect setup changes, then initialize within existing authorization. Existing files are preserved by default. Use --force only for explicitly intended replacement after showing affected files. The CLI installs selected files directly; it does not create a templates/ directory.

Fill required placeholders from decisions. AGENTS.md contains stable rules; MEMORY.md contains current progress; agent_docs contains concise build context. Run npx vibeworkflow doctor and resolve required setup errors. Build and behavior remain Not checked.

For a chat without filesystem access, use the repository's downloadable docs/context-pack.md plus the user's product documents; output clearly separated files to save. Do not invent absent template content. Tool configurations follow the installed client's supported settings; do not enable broad permissions automatically.