메뉴
Enforces MVP development principles — speed over perfection, utility first, simplicity. Use proactively when planning features, architecting solutions, reviewing code, or evaluating technical decisions to prevent over-engineering.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Audit a React/TSX repository for React anti-patterns by loading rule cards from the brainstormer card library, scanning via each card's declared detect strategy, and filing one grouped GitHub issue per `(skill, rule_id)` via the `gh` CLI. Phase 3 adds the full re-run lifecycle: `findIssueByLabel` lookup, in-place body rewrite bounded by `react-audit:managed:start/end` sentinels (human comments survive), close-with-dated-resolution on emptied findings, regression-with-backlink on resurfaced findings, label-collision protocol under concurrent runs, never-reopen invariant. Phase 2c grouped body (15 MVP cards, per-occurrence severity, `<details>` collapsibles) and Phase 2b smart scan (`SMART_SCAN_THRESHOLD=50`) unchanged. Manual invocation only — no hooks. Triggers on `/react-audit`, "audit this repo for react anti-patterns", "run a react audit". Skip design questions, scaffolding, audits of non-React frameworks (Vue, Svelte, Solid).
Discovery interview and requirements gathering session. Pressure-test an idea, architecture, or design decision through structured client interviews. Use when the user wants to be challenged on their thinking, explore trade-offs, or vet a plan before committing.
Create a Product Requirements Document through structured interview. Use when the user wants to write a PRD, define requirements, or plan a new feature.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Convert a PRD into independently-grabbable GitHub issues using vertical slices. Use when the user wants to create issues from a PRD, break down a PRD into tasks, or create GitHub issues from requirements.
Test-Driven Development workflow using vertical slices. Use when implementing features with TDD, writing tests before code, or doing red-green-refactor cycles.
| name | lean |
| description | Enforces MVP development principles — speed over perfection, utility first, simplicity. Use proactively when planning features, architecting solutions, reviewing code, or evaluating technical decisions to prevent over-engineering. |
| Rule | Test |
|---|---|
| Speed > Perfection | "Ugly but useful" ships; perfect never does |
| Utility First | v1.0 = "not-stupid", not brilliant |
| One Task Rule | Handles one complete process A→Z |
| 5-Min Test | Needs 5 tools to launch → dead; works in 5min → chance |
| No Over-Engineering | Build minimum needed, nothing more |
Over-engineered: [specific issues found]
Simplify to: [concrete alternatives]
MVP path: [minimum implementation to ship]
Skip sections with no issues. Be direct — "this is fine" if nothing to flag.
"We need a plugin system with dependency injection, event bus, and config schema validation for our MVP notification feature."
Over-engineered: Plugin system + DI + event bus for a notification feature. Three abstractions for one task.
Simplify to: Single function that sends notifications via one channel.
MVP path: `sendNotification(userId, message)` → hardcode email provider → ship today, add SMS/push when users ask.
"Add a
/healthendpoint that returns 200."
Clean. One task, ships in 5 minutes, no abstractions.