Use a Markdown file in the repo as persisted agent memory across chats. Use when the user wants session-spanning context, a decision log, or to resume work without re-pasting history.
End-to-end project-level vibe workflow with split on-disk state under .cursor/project-vibe-master/ for resume; state template and optional generated data live in this skill (initial-state/, data/). Combines rules, shell/scripts, MCP, hooks, subagents, HITL,…
Full agile lifecycle with MCP: use MCP to fetch current docs/API schema during discovery and development. Use when building a project from a rough idea that depends on external APIs or libraries and you want up-to-date references via MCP.
Full agile development lifecycle at project level: rough idea → requirements → development → unit/integration/e2e tests → feedback loop with human-in-the-loop until completion. Replit-style iterative flow. Use when building a project from a rough idea with…
Fixes bugs or test failures using debugger → fix → verify. Use when the user reports an error, test failure, or unexpected behavior and wants a fix confirmed.
Review code for correctness, style, and maintainability. Use when the user asks for a code review, PR review, or feedback on changes.
Run a pre-deploy checklist (tests, build, env). Use when the user asks to deploy, prepare for release, or run a deploy checklist.
Implements a feature using plan → implement → verify. Use when the user wants to add a new feature with a clear plan and verification.