mcpbeat

Standards Kit

wednesday-solutions/standards-kit

Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.

2k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
164
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill standards-kit

The instruction itself

5 sections, as written by the author

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 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 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.

How to use it

Copy the folder

Take wednesday-solutions/standards-kit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.