dev

name	dev
description	Full sequential dev pipeline — understand, plan, implement, verify, review

You are executing a full development pipeline. Follow every step in order automatically without asking for confirmation unless genuinely ambiguous.

Task: the task/scope the user described when invoking this skill (if none given, ask or infer from context)

Phase 1: Understand

• Scan project structure, tech stack, and architecture patterns.
• Find and read the files directly related to the task.
• Synthesize findings.

Phase 2: Design (UI 작업 포함 시에만)

Skip entirely for backend-only, bug-fix, or refactor tasks with no UI change.

• design-system/MASTER.md가 있으면 로드해 재사용 (필요 시 page override 추가).
• 없으면 ~/.codex/skills/ui-ux-pro-max/ (reasoning-rules.md → styles.md)로 디자인 토큰을 확정하고 design-system/MASTER.md를 생성.
• 구현은 MASTER 토큰 100% 준수 (raw hex 금지, 시맨틱 토큰만, 이모지 구조 아이콘 금지, 터치 타겟 ≥44pt).

Phase 3: Plan

Create a brief implementation plan: files to modify, approach, risks. Identify the dependency order of components.

Phase 4: Implement

Implement sequentially, starting with the foundation (types/interfaces → logic → UI). Follow existing project conventions (naming, structure, patterns).

Phase 5: Verify

Run in order and fix failures automatically (up to 3 attempts): build, lint/type-check, tests. For UI changes also run the /design-audit checks.

Phase 6: Review

Review your own changes across two lenses:

• Quality: single responsibility, no duplication, clear naming, proper error handling, no dead code, no N+1 / obvious perf issues, consistent with the codebase.
• Security: no hardcoded secrets, no injection risks, input validation on external inputs, no sensitive data exposure. Fix any CRITICAL or WARNING findings.

Phase 7: Finalize

Summarize: files changed/created, key decisions, review findings addressed, what to test manually.

Rules

• Do NOT ask for permission between phases — just execute.
• If build/test fails, fix it automatically (up to 3 attempts).
• If genuinely ambiguous (multiple valid approaches), ask once then proceed.
• Commit is NOT included — the user decides when to commit.