⚡ @um1chc5/vibe-cursor

Scaffold a vibe-coding workflow into any project — .cursor/ commands, rules, and docs/ templates.

🚀 Install

Pick whichever method you prefer — they all do the same thing:

# From npm (recommended)
npx @um1chc5/vibe-cursor init

# From GitHub (no npm account needed)
npx github:um1chc5/vibe-cursor init

# Or install globally
npm i -g @um1chc5/vibe-cursor
vibe-cursor init

💡 This copies template files into your current directory. Existing files are never overwritten.

📦 What You Get

🎮 .cursor/commands/

| Command | Description | |---------|-------------| | /start-vibing | 🏁 Onboard a new project — from idea to populated docs and first tasks | | /vibe-code | ▶️ Execute the next task from docs/tasks.md | | /vibe-features | 💡 Brainstorm and plan from docs/features.md | | /big-vibe-code | 🔄 Long-run pipeline: features → tasks → implement → verify → commit | | /update-log | 📝 Add a dated progress entry to docs/logs.md |

📏 .cursor/rules/

| Rule | Description | |------|-------------| | docs-source-of-truth.mdc | 📖 Route information to existing docs; no duplicate specs | | project-code-rules.mdc | ✅ Clean code standards + personal coding preferences |

📄 docs/ Templates

Minimal starter files so the commands and rules can reference them immediately:

| File | Purpose | |------|---------| | docs/features.md | 🎯 Requirements and phased scope | | docs/tasks.md | ✅ Active plan with [ ] / [-] / [x] markers | | docs/questions.md | ❓ Unresolved decisions | | docs/logs.md | 📅 Chronological dev journal | | docs/ux.md | 🖥️ UX behavior and screen flows | | docs/dev/architecture.md | 🏗️ Technical architecture |

🔄 Workflow

1. Init  ─►  2. Plan  ─►  3. Build  ─►  4. Ship

1. npx @um1chc5/vibe-cursor init in your project root
2. Run /start-vibing — the AI walks you through idea → tech stack → features → tasks
3. Use /vibe-code to start executing tasks
4. Use /big-vibe-code for long autonomous sessions

📜 License

MIT