software-standards
Skill1 starsChanged 13 days agoMITView on GitHub
Loads the software standards that apply to every project (product design, UI/UX, .NET, React, mobile, API, backward compatibility, database, testing, Playwright, Maestro, PR/review, DevOps, security/OWASP, performance, observability, setup/secret inventory, Cloudflare/edge, hardening, backup). Use it before writing code, while reviewing, when planning a setup or deploy, or whenever "best practice", "standard" or "the rules" come up.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AlexHorovitz/skillstheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- AlexHorovitz/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- board-planSkill
- configSkill
- test-inventorySkill
- working-modeSkill
The file
Files
Software standards
Why this exists
Left alone, every session and every agent writes code by its own idea of "best practice", so two features in the same project — or the same feature on web and mobile — come out different. This rule set keeps one standard per topic, but loading all of them into every session would burn tokens on text the task never needs. This skill is the index: it names the one standard the task is about, and only that file is read. Same rules in every project, every session and every agent; context spent only where the work is.
Contributions are welcome: https://github.com/adyusuf/claude-code-standards
The standards live under ${CLAUDE_PLUGIN_ROOT}/standards/, one file per topic. Do not
read them all — read the one the task is about.
Index
| Task | Read |
| New feature, scope, acceptance criteria, ADR | 01-product-design.md |
| Screen, component, styling, accessibility, i18n | 02-ui-ux.md |
| General coding, naming, error handling, logging | 03-coding-general.md |
| .NET endpoint/service/EF Core/DI/config | 04-dotnet.md |
| React page/component/state/data fetching/forms | 05-react.md |
| React Native / Expo / store release | 06-mobile.md |
| Endpoint contract, error format, pagination, idempotency | 07-api-design.md |
| Changing a field/endpoint, deprecation, expand-contract | 08-backward-compatibility.md |
| Schema, migration, index, transaction, soft delete | 09-database.md |
Unit/integration/contract tests, flaky policy, screen-by-screen test audit (/adyusuf:test-inventory) | 10-test-strategy.md |
| Web e2e | 11-playwright.md |
| Mobile e2e | 12-maestro.md |
| Commit, branch, PR, code review | 13-pr-and-review.md |
| Environments, CI/CD, deploy, rollback, single-origin topology | 14-devops.md |
| AuthN/AuthZ, OWASP Top 10, the scanning chain, data-protection law | 15-security.md |
| Slowness, cache, bundle, Core Web Vitals, load testing | 16-performance.md |
| Logs, metrics, traces, alerts, incidents, post-mortem | 17-observability.md |
Setup, prerequisites, secret/token inventory, .env | 18-setup-and-environment.md |
| Cloudflare DNS/TLS/WAF/cache/Tunnel/Workers/R2 | 19-cloudflare-and-edge.md |
| Server + application hardening, security headers, IIS/Docker | 20-hardening.md |
| Backup, restore drill, RPO/RTO, disaster recovery | 21-backup-and-recovery.md |
Templates: ${CLAUDE_PLUGIN_ROOT}/standards/templates/
(project-claude-md.md, setup-md.md, pr-template.md, adr-template.md, user-story-template.md)
Common combinations
- New feature (end to end): 01 → 07 → 08 → (04 or 05/06) → 10 → 02
- Code review / merge: 13 → 08 → 15
- New project setup: 18 → 14 → 19 → 20 → 21
- Preparing a production release: 15 (§15 checklist) → 20 → 21 → 17 → 14
- A "it's slow" complaint: 16 → 09 → 17
- Security review: 15 (OWASP §12-13) → 20 → 19
Precedence
The user's instruction right now > the project's CLAUDE.md > the global rules (${CLAUDE_PLUGIN_ROOT}/CLAUDE.md)
these standards. If you are knowingly breaking a standard, write the reason into the code or the PR — there are no silent exceptions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.