Loading...
Loading...
Found 47 Skills
Enforce project code standards when writing code
Setup universal code quality standards in your project. Use when the user wants to generate coding standards files (CLAUDE.md, AGENTS.md, GEMINI.md, etc.) or mentions 'code standards', 'code review setup', or similar intent in any language.
TypeScript, React, and JavaScript best practices enforced by Ultracite/Biome.
Use when writing code changes, sweeping or shortening comments (including file-size or comment-cap findings), or asked to apply house code standards.
Universal coding standards — naming, structure, immutability, error handling, type safety, backend layering, frontend architecture — that fill the gaps after the project's own conventions. Use when starting a module, refactoring to team conventions, setting up lint rules, onboarding, or 'стандарты кода'. Do not use for a repo-wide comment cleanup pass (awesome-code-cleanup) or for designing the API error contract (awesome-error-standards).
Human Made engineering principles and code quality standards. Apply when writing code, reviewing code, planning implementations, or discussing architecture. Covers code quality priorities, simplicity over complexity, and avoiding over-engineering.
Human Made React component standards. Apply when writing React components, reviewing React code, or building WordPress block editor interfaces. Covers functional components, hooks, PropTypes, and component organization.
Complete project planning and execution framework. Automatically includes all 14 planning sections (planning/0-Master-Index.md through planning/13-Lessons-Learned-Continuous-Improvement.md) plus all 9 Claude Skills (tech-stack-selector, architecture-decisions, code-standards-enforcer, ci-cd-pipeline-builder, agile-executor, project-risk-identifier, automation-orchestrator, webapp-testing, web-artifacts-builder). When installed, all planning templates and execution skills are immediately available.
Read-only audit of a database layer — schema anti-patterns (EAV, generic keys, imprecise types), query and index fit (SELECT *, N+1, unindexable predicates), integrity and concurrency, migration and tenancy hygiene — with evidence per finding and a SHIP / FIX / BLOCK verdict. Use when asked to audit the database, review the schema or migrations, judge a data model, or 'проверь схему базы'. Never edits schema or data. Do not use for runtime profiling (awesome-performance-audit), SQL injection (awesome-security-audit), or data-access style (awesome-code-standards).
Read-only audit of performance and reliability — event-loop discipline, streaming and backpressure, memory and CPU diagnostics, shutdown/timeout/job habits, resilience topology (circuit breakers, retry budgets, queue bounds), and frontend delivery (Core Web Vitals, bundle size, hydration) — with evidence per finding and a SHIP / FIX / BLOCK verdict. Use when a service or page is slow, memory climbs, tail latency is bad, a worker OOMs, before a load event, or 'почему тормозит'. Measures and reports; rewrites no hot paths. Do not use for retry/idempotency contracts (awesome-error-standards) or render style rules (awesome-code-standards).
World-class design and motion. Use when designing interfaces, building front-ends, or when craft matters. Triggers on "design this", "make it beautiful", or "be french claude".
Multi-language code quality standards and review for TypeScript, Python, Go, and Rust. Enforces type safety, security, performance, and maintainability. Use when writing, reviewing, or refactoring code. Includes review process, checklist, and Python PEP 8 deep-dive.