Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from steph-frtech/cdesign-expo
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from jleechanorg/claude-commands
Forces Claude to match output scope exactly to what was requested. Triggers before adding error handling for impossible edge cases, extracting one-time abstractions into classes,…
Use when editing existing code — making a fix, adding a feature, or changing behavior in a file that already has working code.
Refactor/rename/migration discipline — enumerate all call sites before editing, separate mechanical from judgment edits, keep the build green, verify by absence and presence.
Autonomous multi-agent workflow system for complex coding tasks. Use when the user requests non-trivial changes that would benefit from autonomous execution with built-in review…
Swift code quality rules for mach-mono — 300-line file limit, @Observable, no singletons in views, no direct Defaults access, protocol-based services.
Reviews Swift code for concurrency safety, error handling, memory management, and common mistakes. Use when reviewing .swift files for async/await patterns, actor isolation,…
Align SwiftFormat, SwiftLint, formatter and linter responsibility, checked-in style config, Git hooks, and CI formatting policy for Swift repositories.
Reviews SwiftData code for model design, queries, concurrency, and migrations. Use when reviewing .swift files with import SwiftData, @Model, @Query, @ModelActor, or…
Use swiftfindrefs (IndexStoreDB) to list every Swift source file referencing a symbol. Mandatory for “find references”, “fix missing imports”, and cross-module refactors.
Expert semantic engineering and MBSE skill for Reqvire. Use when (1) exploring engineering knowledge graphs, (2) adding capabilities with proper ontology, requirement, an — from…
Periodic evidence-based self-audit of the whole agent system — the orchestrator, its docs/SSOTs, rules, memory, subagents, tools, infra and the work it claims to have delivered —…
Go up one layer of abstraction and explain how a local piece of code fits into the larger system. Use when the current focus is too narrow, the user is unfamiliar with an area, an…
Detects anemic domain models, validates and refactors them into rich domain models, and enforces tactical DDD patterns (Entities, Value Objects, Aggregates, Domain Servic — from…
Generate test scenarios, write the test file, and run it for a specific source file using the tailtest R1-R15 rule layer.
Exhaustive completion discipline for long, complex, or multi-item tasks (1:1 ports, migrations, sweeping refactors, batch changes) - mechanical inventory of every work unit, a…
Use for QUICK PR reviews with structured checklists (architecture, patterns, security, performance). Provides step-by-step review process, git diff commands, and review report…
Unified team skill for tech debt identification and remediation. Scans codebase for tech debt, assesses severity, plans and executes fixes with validation.
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks abo — from…
Full codebase technical debt audit using 11 parallel specialized agents. Identifies dependency issues, code smells, architecture problems, test gaps, error handling flaws,…
Quantify and communicate tech debt as a business decision. Use when engineering needs investment in infrastructure and you need to make the case to leadership.
Systematic technical debt inventory and prioritization. Use when asked to "find tech debt", "show me the TODOs", "how healthy is this codebase", "what should we fix first", "find…
Strategic technical debt management - understanding the debt metaphor, knowing when to take on debt, when to pay it down, and how to communicate debt decisions to stakeholdersUse…
Expert in making the business case for technical debt reduction. Covers quantifying debt costs, getting stakeholder buy-in, prioritizing what to fix, and negotiating engineering…
Track technical debt deliberately by framing each item as interest owed and budgeting steady paydown.
Loop automatizado de melhoria contínua que usa o Chat RAG para identificar débitos técnicos, implementa correções, reingere a base de conhecimento e valida até eliminar 100% dos…
Run a focused tech debt reduction sprint — inventories all technical debt (TODOs, outdated deps, missing tests, god objects), fixes code smells, removes dead code, then hardens…
Scan all Python repos for tech debt, deduplicate against existing tickets, create Linear epics and tickets by category
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.
Aide à identifier, prioriser et planifier le remboursement de la dette technique avec des métriques de suivi.
Expert guide to detecting, categorizing, and prioritizing technical debt in Rails applications. Use when: (1) Auditing codebase health, (2) Planning refactoring sprints, (3)…
Use when reviewing or refactoring code that queries object state and makes decisions outside the object that owns the data.
Delete tests that don't catch real bugs — the inverse of TDD. Use when reviewing legacy test suites, slow CI investigations, refactor-driven test sweeps, or evaluating whether a…
Triggered when the user submits code or requests a code review. Automatically analyzes code quality, identifies potential bugs, security vulnerabilities, and performance issues,…
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it shoul — from…
Use TGlider for TypeScript and JavaScript semantic navigation, references, diagnostics, dependency topology, impact analysis, and refactoring.
Use when you need coding, implementation, refactoring, patching, or test work; the Builder turns concrete repo context into the smallest verified change and follows local…
Fetch structured context from Jira issues, Confluence pages, and GitHub issues/PRs. Auto-loads when a prompt or argument references a ticket key (e.g.
Invoked by /tidy-code. Reviews source code for structural quality violations (hidden dependencies, god functions, silent failures, deep nesting) across any language.
Reviews tokio async runtime usage for task management, sync primitives, channel patterns, and runtime configuration.
Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.
Behavior-preserving refactoring under characterization tests, plus severity-rated code review. Use when the user says "refactor", "clean up", "tech debt", "code review",…
ACTIVATE whenever writing or modifying TypeScript code in src/. ACTIVATE for code review, formatting, or 'coding standards'.
A skill designed to review TypeScript code for quality, maintainability, and adherence to best practices, providing feedback and recommendations for improvement.
TypeScript Compiler API via ts-morph for structural code manipulation. Navigate class/interface/function AST nodes, add/remove/rename declarations, batch refactor across a…
Use for TypeScript structure/code review, TS PR review, architecture boundary review, type-contract drift, error-handling review, duplication/shape drift review, and test…
Multi-agent app builder with 7 modes - greenfield, iteration, bugfix, refactor, UI polish, migration, and audit. PM orchestrates specialized agents with feature branches.
t_wada スタイルの TDD でコードを書く。テストを先に書き、Red→Green→Refactor サイクルで進む。リファクタリングの設計判断も t_wada の考え方に従う。
Use when the user wants to whole-codebase 3-lens simplification (Reuse/Quality/Efficiency). Packs the repo into a fixed fleet of byte-balanced areas (default 8), audits each area…
Tactical user interface design guide for fixing layouts, selecting colors and fonts, and creating professional UIs.
Use when refactoring existing React Native, Next.js, or TypeScript UI code to apply modern design principles and aesthetic excellence - analyzes current implementation, applies…
Ultimate parallel code review — orchestrates 10 specialized agents simultaneously, with triple-pass correctness analysis and systematic coverage gap detection for near-100% catch…
Use when writing or modifying code — implementing features, refactoring, or fixing bugs — to prevent over-engineering: unrequested abstractions, options, config, dependencies, and…
Use when the user explicitly asks for adversarial review, \u6575\u5bfe\u7684\u30ec\u30d3\u30e5\u30fc, ship-blocker review, ship blocker review, strict pre-ship review,…
Formal, evidence-based software engineering audit producing a scored, gated release verdict. Use when asked for a "full audit", "production audit", "release audit", "formal…
Reviews code for quality, security, and maintainability. Use after implementing features, completing significant work, or when user asks for code review.
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way.
Design a rigorous, auditable playbook when no narrower skill fits: a large migration, multi-part change, or work a human will review after stepping away.