standards-kit
Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.
git clone --depth 1 https://github.com/wednesday-solutions/ai-agent-skills /tmp/standards-kit && cp -r /tmp/standards-kit/skills/standards-kit ~/.claude/skills/standards-kitSKILL.md
# Standards Kit (Dev & Design) This kit ensures every line of code and every UI element follows Wednesday Solutions' high-quality standards. ## 🚦 Decision Flow ``` 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.). ``` ## 🛠️ Technical Logic (Core) - **Max Complexity**: 8 (No exceptions). - **Naming**: PascalCase (UI/Types) / camelCase (Logic). - **Forbidden**: No `console.log`, magic numbers, or unused imports. - **Graph Safety**: Mark dynamic patterns with `@wednesday-skills` tags. *Read [references/LOGIC.md](references/LOGIC.md) for remediation and structure patterns.* ## 🎨 Visual Design (Core) - **Mandatory**: Use **shadcn**, **Aceternity**, or **Magic UI** ONLY. - **Identity**: Green-to-Teal gradients, Instrument Serif headlines, DM Sans body. - **Performance**: Animate only `transform` and `opacity`. *Read [references/VISUALS.md](references/VISUALS.md) for tokens and component styling.* ## 🏁 Enforcement Checklist - [ ] Complexity score verified (< 8). - [ ] UI components sourced from approved libraries. - [ ] Naming and imports follow strict patterns. - [ ] Accessibility and performance requirements met.
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.
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.
Pre-deploy and post-deploy checklist skill. Ensures env vars, migrations, CI, rollback plan, smoke tests, and monitoring are verified before and after every deployment.
Parallel persona planning for new projects. Research agent runs first to build domain context, then Architect, PM, and Security agents run in parallel. Synthesis agent combines all perspectives into a detailed GSD-style PLAN.md with Tensions section.
Fix engine for PR review comments. Fetches review comments (Gemini bot or human), categorizes by impact, posts a prioritized fix queue, and applies fixes on dev approval. Called directly for quick fixes, or internally by pr-review-agent as part of full PR review.