Claude Skills by thedixitjain

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.

This skill should be used when the user asks to \"create a spec\", \"write requirements\", \"design a feature\", \"plan implementation\", \"use EARS notation\", \"create user stories\", \"break down tasks\", \"write a PRD\", \"technical specification\", or mentions \"spec-driven development\", \"feature spec\", \"requirements phase\", \"design phase\", or \"tasks phase\". Provides structured 3-phase workflow for feature development.

Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.

Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/.

Backend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to \"understand this backend\", \"map the API\", or \"assess code quality\".

API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to \"review this API\", \"code review\", \"review backend\", or \"pre-launch backend check\".

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

使用JUnit 5、Mockito、MockMvc、Testcontainers和JaCoCo进行Spring Boot的测试驱动开发。适用于添加功能、修复错误或重构时。

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

Desarrollo guiado por pruebas para Spring Boot usando JUnit 5, Mockito, MockMvc, Testcontainers y JaCoCo. Usar al agregar funcionalidades, corregir bugs o refactorizar.

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage.

Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.

'Collect WebContainer diagnostic info: boot state, file system, process list. Use when working with WebContainers or StackBlitz SDK. Trigger: \"stackblitz debug\". '

'Optimize WebContainer boot time, file system mounts, and process spawning. Use when working with WebContainers or StackBlitz SDK. Trigger: \"stackblitz performance\". '

'Production architecture for WebContainer-powered browser IDEs and playgrounds. Use when working with WebContainers or StackBlitz SDK. Trigger: \"stackblitz architecture\". '

'Migrate between WebContainer API versions and StackBlitz SDK updates. Use when working with WebContainers or StackBlitz SDK. Trigger: \"upgrade stackblitz\". '

'WebContainer lifecycle events: server-ready, port changes, error handling. Use when working with WebContainers or StackBlitz SDK. Trigger: \"webcontainer events\". '

Run a factual, staff-level review of a local branch, diff, repo, directory, or file. Use for code review, deep review, review-my-changes, or staff-review requests.

First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.

Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.

Show DAG state, agent progress, and branch status for an AgentHub session. Use when the user runs /hub:status or asks how the AgentHub agents are doing.

Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes /steno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding/tutorial content, stakeholder or customer-facing copy, or teaching-focused explana...

Applies stewardship virtues (Care, Curiosity, Humility, Diligence) to plugin work. Use when authoring plugins or reviewing code quality.

End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

'Collect Supabase diagnostic info for troubleshooting and support tickets. Use when debugging connection failures, auth issues, Realtime drops, Storage errors, RLS misconfigurations, or preparing a support escalation. Trigger: \"supabase debug\", \"supabase diagnostics\", \"supabase support bundle\", \"collect supabase logs\", \"debug supabase connection\". '

>- Execute Supabase incident response: dashboard health checks, connection pool status, pg_stat_activity queries, RLS debugging, Edge Function logs, storage health, and escalation. Use when responding to Supabase outages, investigating production errors, debugging connection issues, or preparing evidence for Supabase support escalation. Trigger with \"supabase incident\", \"supabase outage\", \"supabase down\", \"supabase on-call\", \"supabase emergency\", \"supabase broken\", or \"supabase c...

'Optimize Supabase query performance with indexes, EXPLAIN ANALYZE, connection pooling, column selection, pagination, RPC functions, materialized views, and diagnostics. Use when queries are slow, connections are exhausted, response payloads are bloated, or when preparing a Supabase project for production-scale traffic. Trigger with phrases like \"supabase performance\", \"supabase slow queries\", \"optimize supabase\", \"supabase index\", \"supabase connection pool\", \"supabase pagination\"...

\"Implement enterprise Supabase reference architectures \\u2014 monorepo\\ \\ layout, multi-tenant RLS,\\nmicroservices with cross-project access, framework\\ \\ integration, edge functions, caching,\\nqueue patterns, and audit logging.\\nUse\\ \\ when designing a new Supabase project from scratch, reviewing project structure\\ \\ for\\nproduction readiness, planning multi-tenant isolation, or establishing team\\ \\ architecture standards.\\nTrigger with phrases like \\\"supabase architecture...

\"Upgrade Supabase SDK and CLI versions with breaking-change detection\\ \\ and automated code migration.\\nUse when upgrading @supabase/supabase-js (v1\\u2192\\ v2 or minor bumps), migrating auth/realtime/storage\\nAPIs, or updating the Supabase\\ \\ CLI. Trigger with phrases like \\\"upgrade supabase\\\",\\n\\\"supabase breaking changes\\\"\\ , \\\"migrate supabase v2\\\", \\\"update supabase SDK\\\".\\n\"

Standing house style to enforce dense, correct, and idiomatic code on all coding tasks. Minimizes code bloat and agent operation overhead.

>- Supplier Corrective Action Request (SCAR) — escalate a supplier non-conformance to a formal corrective action request, define response requirements, evaluate the supplier's 8D response, and verify effectiveness. Use when an NCR escalates to a SCAR, when a supplier delivers repeated non-conformances, or when a field failure is traced to a supplier. Covers ISO 9001 §8.4 and IATF 16949 §8.4.1.

Finish a SolidWorks task by invoking sw-learner, honoring the saved feedback preference, asking the exact three-option consent question when required, and submitting validated feedback with retries. Use after the CAD result has been delivered for every task that involved SolidWorks modeling, API work, generated CAD code, engineering decisions, or debugging.

Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.

Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file. Concrete actions include adding Sendable conformance, applying @MainActor annotations, resolving actor isolation warnings, fixing data race diagnostics, and migrating completion handlers to async/await.

Review and fix Swift concurrency issues such as actor isolation and Sendable violations.

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.

Audit SwiftUI performance issues from code review and profiling evidence.

Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage. Use when cleaning up a SwiftUI view, splitting long bodies, removing inline actions or side effects, reducing computed `some View` helpers, or standardizing `@Observable` and view model initialization patterns.

Refactor SwiftUI views into smaller components with stable, explicit data flow.

Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes

Use when encountering any bug, test failure, or unexpected behavior — before proposing fixes.

> 提供系统化根因定位流程，避免在复杂缺陷里靠猜测叠加修补。 当问题难复现、跨模块、连续修错或需要先证明根因再改代码时使用。

4-phase root cause debugging: understand bugs before fixing.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing

Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.