Agent skill · Content & Marketing

not-a-vibe-coder

Turns vague prompts into 8 structured planning files for brand new projects. DO NOT use on existing codebases.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill not-a-vibe-coder --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/not-a-vibe-coder/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Not-a-Vibe-Coder A skill that turns any project idea — no matter how vague — into 8 living planning documents that act as the project's persistent memory across a long context window. The documents are the source of truth for "what we agreed on"; the user's live instructions are always the final authority and can override the docs at any time. ## When to Use - Use this skill when the task matches this description: Turns vague prompts into 8 structured planning files for brand new projects. DO NOT use on existing codebases. ## Core Principles (never violate these) 1. **User command > files > AI assumptions.** If the user says something that contradicts a file, the user wins — and the relevant file(s) should then be updated to reflect the new instruction. 2. **No silent additions.** Never add features, tech choices, pages, tables, or rules the user did not ask for or approve. If something seems missing, ask — don't assume. Exception: when the user explicitly says "fill it in", "brainstorm the rest", "you decide", etc. — see Phase 3. 3. **Design.md is special.** NEVER fill Design.md with your own taste. Always ask the user for style direction (e.g. minimal, playful, corporate, dark

What's inside
Steps it walks through
  1. When to Use
  2. Core Principles (never violate these)
  3. The 8 Files
  4. Workflow
  5. Phase 0 — Detect intent
  6. Phase 1 — PRD.md first
  7. Phase 2 — Remaining files, one by one (except Design.md)
  8. Phase 2.5 — Design.md (always interactive)
  9. Phase 3 — Final review
  10. Phase 4 — Build
  11. Quick Reference: Decision Rules
  12. Limitations
More from agentic-awesome-skills
All skills →
About this skill
What does the not-a-vibe-coder skill do?

Turns vague prompts into 8 structured planning files for brand new projects. DO NOT use on existing codebases.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill not-a-vibe-coder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going