/standards-kit
Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.
$ npx -y skills add wednesday-solutions/ai-agent-skills --skill standards-kit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition โ
- You can call itInvoke it directly when you want it.
- Slash command
/standards-kit
Context preview
The summary Claude sees to decide when to auto-load this skill.
Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.
SKILL.md
standards-kit.SKILL.mdname: 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)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.
Read more
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)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.
Transform any repository into an AI-aware, intelligent environment โ a codebase that any AI agent can jump into on day one without making junior-level mistakes.
Repo: wednesday-solutions/ai-agent-skills
Other skills on ai-agent-skills.
- /module-audit
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.
Open skill - /onboard-dev
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.
Open skill - /pr-review-agent
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.
Open skill - /brownfield-drift
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.
Open skill - /codebase-intel
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.
Open skill - /deploy-checklist
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.
Open skill

