메뉴
Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Unified Git workflow. Manages the entire task lifecycle: branch creation (sprint), atomic commits (git-os), and PR opening (pr-create).
Unified codebase intelligence. Handles all questions about structure, logic, risk, and dependencies. Combines natural-language Q&A with deterministic lookups and pre-edit blast radius checks.
Use when asked to audit a module, check its health, or assess whether it should be refactored. Runs structural query, risk check, and test generation automatically.
Use when a dev is new to the project, asks for an overview, or wants to get oriented quickly. Fills graph gaps then runs a guided codebase interview.
Full PR review orchestrator. Use when asked to review a PR or check if it is ready to merge. Runs blast radius + drift check on changed files, then hands off to pr-review for comment triage and fixes. Do NOT use pr-review directly for full reviews — use this.
Enforces architecture boundaries defined in PLAN.md. Use when a PR crosses module/service boundaries, when the dev asks "are we following the architecture?", or as a scheduled architecture health check. Not for querying what a module does — use brownfield-chat for that.
| name | standards-kit |
| description | Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries. |
| license | MIT |
| permissions | {"allow":["Bash(npm run lint)","Bash(npm run format:check)","Bash(npm run test)"]} |
This kit ensures every line of code and every UI element follows Wednesday Solutions' high-quality standards.
1. DO NOT create custom UI components.
Check references/VISUALS.md for approved libraries.
2. Keep Cyclomatic Complexity < 8.
Check references/LOGIC.md for refactoring strategies.
3. Use PascalCase for UI/Types and camelCase for Logic.
4. Follow strict Import Ordering (React -> Next -> State -> UI -> Alias -> etc.).
console.log, magic numbers, or unused imports.@wednesday-skills tags.Read references/LOGIC.md for remediation and structure patterns.
transform and opacity.Read references/VISUALS.md for tokens and component styling.