{
  "markdown": "# dev-standards — Claude Code Skill\n\n> **Universal Development Standards (v2.3.0)** — A Claude Code skill that enforces\n> production-grade engineering practices across the full SDLC.\n\n## What it does\n\nWhen invoked, this skill instructs Claude to apply a comprehensive set of development\nstandards to everything it generates or reviews in that session — covering code quality,\nsecurity, performance, API design, testing, DevOps, and more.\n\n**Stacks covered:**\n\n| Layer | Technologies |\n|-------|-------------|\n| Frontend | React, Next.js, React Native, Vue 3, Svelte |\n| Backend | Python/FastAPI, Node.js/Express, Go/Fiber |\n| Database | PostgreSQL, SQLite |\n| Infra | GitHub Actions, Docker, Supabase |\n\n## Standards covered\n\n| # | Section |\n|---|---------|\n| 1 | Product & Project Management (GitHub Flow, Agile, Monorepo, Code Review) |\n| 2 | Design & User Experience (WCAG 2.1 AA, mobile-first, dark mode) |\n| 3 | Engineering Excellence (frontend, backend, API design, error handling) |\n| 4 | Quality Assurance & Testing (unit, integration, E2E, manual QA) |\n| 5 | DevOps & Automation (CI/CD, deployments, smoke tests) |\n| 6 | Security, Safety & Governance (OWASP, vulnerability scanning, GDPR, AI governance) |\n| 7 | Operations & Observability (structured logging, alerting) |\n| 8 | Efficiency Standards (AI resource use, velocity) |\n| 9 | Performance Standards (Core Web Vitals, load testing, slow query thresholds) |\n| 10 | Documentation & Artifacts (architecture.md, RFC templates, test plans) |\n\n## Installation\n\n### Option 1 — Clone directly into your Claude skills directory\n\n```bash\ngit clone https://github.com/YOUR_USERNAME/claude-dev-standards \\\n  ~/.claude/skills/dev-standards\n```\n\n### Option 2 — Manual install\n\n1. Download `SKILL.md` from this repo.\n2. Place it at:\n   ```\n   ~/.claude/skills/dev-standards/SKILL.md\n   ```\n3. Restart Claude Code (or reload the window).\n\n## Usage\n\nIn any Claude Code session, type:\n\n```\n/dev-standards\n```\n\nClaude will immediately apply all standards to the current session. You can also pass\na specific question or request:\n\n```\n/dev-standards review this PR for security issues\n/dev-standards what API design patterns should I use here?\n```\n\n## Example use cases\n\n### Start a new feature with standards enforced\n```\n/dev-standards build a user authentication API with JWT refresh tokens\n```\nClaude will apply REST conventions, Pydantic/Zod schemas, Controller->Service->Repository\npattern, rate limiting, HSTS headers, and structured logging — all without you asking\nfor each individually.\n\n---\n\n### Review existing code for security issues\n```\n/dev-standards review this file for OWASP vulnerabilities\n```\nClaude will check for injection risks, broken auth, XSS, missing CORS/CSP headers,\nhardcoded secrets, and unvalidated inputs — and suggest fixes inline.\n\n---\n\n### Set up CI/CD pipeline\n```\n/dev-standards create a GitHub Actions workflow for my Next.js app\n```\nClaude will generate a workflow with lint, typecheck, unit tests, Lighthouse CI,\nvulnerability scanning (npm audit), secret detection (gitleaks), and staging deploy\n— all gated correctly.\n\n---\n\n### Design a database schema\n```\n/dev-standards design a schema for a multi-tenant SaaS app\n```\nClaude will produce versioned migrations (not raw SQL), add HNSW indexes where\nrelevant, flag any queries that need `EXPLAIN ANALYZE`, and include soft-delete\nwith GDPR erasure support.\n\n---\n\n### Write tests for a service\n```\n/dev-standards write tests for this payment service\n```\nClaude will generate a full test pyramid: unit tests (mocked externals, 80%+ coverage),\nintegration tests against a real test DB, and E2E tests for the checkout flow using\nPlaywright — with a regression test for any known edge cases.\n\n---\n\n### Audit a PR before merge\n```\n/dev-standards apply the code review checklist to this diff\n```\nClaude will run through the full review checklist: logic correctness, no PII in logs,\nno N+1 queries, error paths handled, test coverage, API backwards-compatibility,\nand secrets/credential scan.\n\n---\n\n### Plan an RFC for a complex feature\n```\n/dev-standards write an RFC for migrating from REST to GraphQL\n```\nClaude will produce a structured RFC with problem statement, trade-off analysis,\nschema changes, API contract, security implications, and open questions — ready\nfor team review before any code is written.\n\n---\n\n## Adoption tiers\n\nNot every rule applies to every project. The skill documents two tiers:\n\n| Tier | Sections | Best for |\n|------|----------|----------|\n| **Starter** | 1, 3 (core), 5 (CI basics), 6 | Solo devs, side projects |\n| **Full** | All 10 sections | Teams, production systems |\n\n## Changelog\n\n| Version | Date | Summary |\n|---------|------|---------|\n| 2.3.0 | 2026-04-12 | Code review standards, API design, error handling & resilience, data privacy/GDPR, performance budgets |\n| 2.2.0 | 2026-04-12 | Vulnerability scanning (SAST, dependency scan, secret detection, IaC) |\n| 2.1.0 | 2026-04-09 | Vue/Svelte/Go support, monorepo guidance, MIT license, tiered adoption, RFC + architecture templates |\n| 2.0.0 | 2025-01-01 | Initial public release |\n\n## Contributing\n\nPRs welcome. Please:\n- Open an issue first for significant changes.\n- Follow the section structure in `SKILL.md`.\n- Update the `version` and `changelog` in the frontmatter.\n- Keep rules actionable and tool-specific — avoid vague advice.\n\n## License\n\nMIT — see [LICENSE](./LICENSE).\n",
  "bytes": 5408,
  "sha": "dc1b73e81439464b13379bd9ca41cbd47e1c9d4e78f8110a422a52a91e8a4102",
  "repo_slug": "nsyamala1/claude-dev-standards",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_nsyamala1_claude_dev_standards_claude_de_7001d0f7/readme"
}