| name | standards |
| description | Apply language, framework, database, security, algorithm, Git, automated-testing, HTML, CSS, accessibility, usability, and interaction-design quality standards when writing, editing, refactoring, reviewing, or organizing source code, tests, schemas, migrations, queries, and user interfaces. Detect the active stack and load only its references. Do not use for prose-only or non-code configuration tasks. |
Standards
Improve code clarity, correctness, maintainability, and scalability without expanding the requested scope or adding speculative architecture.
Precedence
Apply standards in this order:
- User requirements and repository instructions.
- Checked-in formatter, linter, compiler, analyzer, test, and build configuration.
- Existing local conventions that are consistent and intentional.
- Current official language, framework, and database guidance.
- The references in this skill.
Do not restyle a repository to match a personal preference. When local practice conflicts with correctness, security, or an explicit official requirement, surface the conflict and make the smallest justified correction.
Load focused guidance
Each technology has its own directory under references/. Open that directory's index.md first, then load only the linked topic files needed for the current decision. Do not load every topic file for a technology by default.
Inspect the files and project manifests before choosing references. Use references/principles/index.md only when deciding abstractions, duplication, file boundaries, refactoring, or structural tradeoffs. Use references/testing/index.md when test design, test doubles, suite reliability, or test boundaries materially affect the work. Use references/ux/index.md when the task includes interaction design, usability, user research, prototyping, or mobile interaction decisions. Then load only the language, framework, and database indexes needed for the current task.
Languages
- TypeScript:
references/typescript/index.md
- JavaScript source files, including mixed TypeScript packages:
references/javascript/index.md
- Python:
references/python/index.md
- Go:
references/go/index.md
- Rust:
references/rust/index.md
- Java:
references/java/index.md
- C#:
references/csharp/index.md
- PHP:
references/php/index.md
- Ruby:
references/ruby/index.md
- Kotlin:
references/kotlin/index.md
Web frameworks
- Framework-independent HTML, CSS, forms, accessibility, or responsive UI:
references/web-ui/index.md
- React:
references/react/index.md
- Next.js:
references/nextjs/index.md
- Vue:
references/vue/index.md
- Nuxt:
references/nuxt/index.md
- Angular:
references/angular/index.md
- Node.js backend code:
references/node-backend/index.md
- Express:
references/express/index.md
- Fastify:
references/fastify/index.md
- NestJS:
references/nestjs/index.md
- Django:
references/django/index.md
- FastAPI:
references/fastapi/index.md
- Flask:
references/flask/index.md
- Spring Boot:
references/spring/index.md
- Ktor:
references/ktor/index.md
- ASP.NET Core:
references/dotnet-web/index.md
- Laravel:
references/laravel/index.md
- Symfony:
references/symfony/index.md
- Rails:
references/rails/index.md
- Go
net/http services: references/go-http/index.md
- chi:
references/go-http/index.md and references/chi/index.md
- Gin:
references/go-http/index.md and references/gin/index.md
- Echo:
references/go-http/index.md and references/echo/index.md
- Axum:
references/axum/index.md
- Actix Web:
references/actix/index.md
Databases
- Relational modeling and portable SQL:
references/sql/index.md
- PostgreSQL:
references/postgresql/index.md
- MySQL:
references/mysql/index.md
- SQLite:
references/sqlite/index.md
- MongoDB:
references/mongodb/index.md
- Redis:
references/redis/index.md
Cross-cutting concerns
- Framework-independent application security:
references/security/index.md
- Algorithms, data structures, and complexity:
references/algorithms/index.md
- Git state, integration, history, and publication safety:
references/git/index.md
For a cross-stack change, load the minimum combination that owns the affected boundaries. Do not load the entire reference set.
Use DDD patterns only as vocabulary for real, changing domain complexity. Simple CRUD does not require repositories, services, aggregates, an event bus, plugin frameworks, or extra layers merely because those patterns exist.
Apply standards
Use references/principles/index.md as the router for the canonical DRY, KISS, YAGNI, cohesion, coupling, abstraction-timing, and size guidance. Use the selected stack indexes for ecosystem-specific rules. Do not restate their guidance from memory or load unrelated topic files.
Work within scope
Apply these standards to new and materially changed code. Avoid unrelated cleanup, repository-wide reformatting, dependency replacement, or architectural migration unless the request requires it. Preserve generated files and vendor code unless their owning workflow says otherwise.
Prefer names, types, structure, tests, and external documentation over source comments. Do not add comments, docstrings, TODO or FIXME markers, placeholder code, or commented-out code to narrate implementation or defer work. Keep only tool-required directives, license notices, public API documentation for an explicit contract, or a concise non-obvious reason that code cannot express and a maintainer or caller must know.
When a standard suggests a larger change than the task permits, keep the local change compatible and report the broader improvement separately.
Verify
Run the repository's formatter, linter, compiler or type checker, focused tests, and relevant broader checks. Use the configured tools rather than manually approximating their output. Inspect the final diff for unnecessary abstraction, duplicated knowledge, hidden behavior, unrelated churn, and violations of the loaded references.
