Coding Standards
Baseline code quality for Muse across projects: naming, readability, immutability, KISS/DRY/YAGNI, error handling, and code-smell review, with PASS/FAIL pairs.
- What
- Baseline code quality for Muse across projects: naming, readability, immutability, KISS/DRY/YAGNI, error handling, and code-smell review, with PASS/FAIL pairs.
- Cost
- Free
- Needs
- Use "Coding Standards" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: baseline coding conventions that apply across projects, the shared floor every codebase should meet before framework-specific skills take over. Built on four principles: readability first (code is read more than written), KISS (simplest solution that works, no premature optimization), DRY (extract common logic, no copy-paste), and YAGNI (no speculative generality). Concrete rules with PASS/FAIL pairs across TypeScript and JavaScript: descriptive variable and function names (verb-noun pattern), immutability via spread instead of direct mutation, comprehensive error handling with typed errors, parallel async with Promise.all instead of sequential awaits, real types instead of any, plus React best practices (typed components, custom hooks, functional state updates, no ternary hell), REST API conventions (verbs, consistent response envelopes, zod input validation), file organization and naming, comments that explain WHY not WHAT with JSDoc for public APIs, performance habits (memoization, lazy loading, select only needed columns), testing standards (AAA pattern, descriptive test names), and a code-smell catalog (long functions, deep nesting fixed with early returns, magic numbers replaced by named constants). Knows its scope boundaries: defers to frontend-patterns for React specifics and backend-patterns for API design. Use when starting a new project, reviewing code quality, refactoring toward conventions, setting up linting, or onboarding contributors. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: the baseline, not the ceiling; examples lean TypeScript and React, adapt the spirit to your stack; conventions need team buy-in, a skill alone does not enforce them. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Coding Standards" with your Muse. Prerequisites: none to install. Pure guidance; have code to review or a new module to start. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/coding-standards/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review this code against baseline coding standards: [paste code or describe the module]." 3. Ask it to flag naming, mutation, error handling, and code smells with PASS/FAIL pairs, and to defer to narrower skills for framework specifics. Tip: run it on a new contributor's first PR as a teaching review. Safety: a skill is plain-text instructions; it runs nothing by itself. Standards are team decisions; use the review to start the conversation, not end it.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.