comprehensive-tracing
Enforces thorough code analysis with all entry points, complete flow tracing, architectural reasoning, and consumption tracking
Discover Research skills, compare source repositories and read the instructions for each workflow.
Enforces thorough code analysis with all entry points, complete flow tracing, architectural reasoning, and consumption tracking
Defense-in-depth validation pattern for Crispy CRM. Validates data at EVERY layer - API boundary (Zod with strictObject, .max() limits, coercion), form state (schema defaults, useWatch), database (RLS/soft-dele...
Comprehensive Supabase CLI reference for local development, migrations, Edge Functions, type generation, and deployment. Triggers on supabase, npx supabase, migrations, db push, db pull, db reset, edge function...
Use pre-computed discovery files at .claude/state/ for codebase inventory questions. Triggers on component, hook, schema, form, type, inventory, what exists, list all, how many. Saves 90%+ tokens vs source scan...
Comprehensive full-stack codebase audit for Crispy CRM. Triggers on audit, deep audit, codebase review, quality check, after refactoring, new feature complete. Phased approach (Critical > Improvements > Polish)...
Use when implementing features, handling errors, adding validation, creating forms, writing database migrations. Enforces fail-fast (NO retry logic, circuit breakers), single entry point (unified data provider,...
Plan execution skill with subagent parallelization, checkpoint/rollback, TodoWrite tracking, and intelligent agent routing. Triggers on execute-plan, run plan, implement plan, execute tasks.
Plan authoring skill with quality gates and AI estimation. Triggers on write-plan, implementation plan, design plan, feature plan, execution plan. Enforces zero-context clarity, TDD requirements, constitution c...
Evidence-based completion claims - BLOCKS claiming tests pass, builds succeed, features work, or tasks are done without running verification commands first. Enforces TDD for implementation tasks. Triggers on do...
Supabase backend patterns for Crispy CRM - RLS policies, Edge Functions, query optimization, and migration best practices. Focuses on PostgreSQL 17 patterns with soft deletes and multi-tenant architecture.
Data Provider architecture rules for Crispy CRM. Use when creating data handlers, adding new resources, modifying unifiedDataProvider, implementing CRUD operations, or working with React Admin handlers and Supa...
Diagnose and resolve build failures, performance issues, and deployment problems using the RAPID framework. Covers TypeScript/build errors, performance bottlenecks, Edge Functions, environment configs. Parallel...
Use when designing UI, auditing UI/UX, choosing colors, implementing buttons/forms, or making layout decisions. Covers WCAG 2.1 AA form accessibility (aria-invalid, role="alert", aria-describedby, focus managem...
Systematic backward tracing through call chains to find where bugs originate. Triggers on debug, trace, root cause, call stack, error, exception, bug, investigate, find the source, test pollution, flaky test, b...
Use when receiving or giving code review feedback, implementing review suggestions, addressing PR comments, or evaluating technical suggestions. Covers both directions - receiving feedback (verify before implem...
仕様駆動開発(SDD)ワークフローを自動発動で強制。Subtask開始時にAC確認、TDD実行、完了時にACチェックを実施。スコープ外実装を禁止。Use when implementing features, creating new functionality, or when "実装して", "...
ブランチ作成Skill。仕様策定用(spec/*)または実装用(impl/*)のブランチを作成。/spec や spec-workflow から呼び出される。
PR作成Skill。仕様レビュー用または実装レビュー用のPRを作成。/spec や spec-workflow から呼び出される。
仕様策定Skill。自然言語の要件から構造化された仕様書(EPIC/Story/Subtask)を段階的に生成。完了時に /branch と /pr を自動呼び出し。Use when "specを作成して", "仕様を策定して", "要件を整理して" keywords appear.
Guide experienced developers on test structure, patterns, assertions, and test doubles for effective test-driven development
Guide experienced developers through TDD failure scenarios and recovery procedures when tests behave unexpectedly
Guide experienced developers through GREEN phase of TDD cycle - writing minimal implementation to pass failing tests
Guide experienced developers through REFACTOR phase of TDD cycle - improving code quality while maintaining green tests
Guide experienced developers through RED phase of TDD cycle - writing failing tests and verifying expected failures
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.