aparigraha-task
Master workflow walking the Aparigraha gates end-to-end — onboarding, dependency inventory, style detection, reuse-first authoring, surgical diff, audit. Orchestrates the 25-pragmatism category skills. No implementation logic.
#build
23 skills tagged build · lifecycle axis.
api-implementation
When the API contract is ready and needs code behind it — implements handlers/controllers with validation.
auth-implementation
When you need auth that won't become a breach headline — implements JWT, OAuth2, or RBAC safely.
caching-strategy
When the same expensive query runs hundreds of times — implements caching patterns with proper invalidation.
chesterton-fence
Before deleting or refactoring code that looks unused or weird, reconstruct why it exists from history, tests, comments, and call-graph; produce a memo plus an edge-case checklist that gates the change.
cleanup
When the codebase has accumulated cruft — removes noise, enforces formatting, safely renames identifiers.
code-generation
When you have a spec and need idiomatic code — generates from specs with language convention enforcement.
data-access
When your API is fast but your database calls aren't — repository pattern, query optimization, N+1 prevention.
db-tuning
When queries are the bottleneck — index analysis, query plan optimization, connection pooling.
dependency-utility-scout
Mine the project's declared dependencies and produce a per-capability inventory of utilities the team already imports — advisory, never auto-rewrites.
error-handling
When every module handles errors differently — standardizes error types, logging, and response formats.
feature-shipping
Master workflow for shipping a feature end-to-end. Orchestrates prd -> task-decomposition -> tdd-workflow -> code-review -> release-pipeline -> auditor. Composes the release-pipeline master as the delivery sub-workflow.
inline-documentation
When code needs to explain itself to future readers — JSDoc/docstrings, comment quality, self-documenting patterns.
minimal-diff
Smallest correct change that solves the problem. No drive-by formatting or opportunistic refactors; diff-size caps, reversibility checks, and commit splitting when concerns are tangled.
pair-programming
When two heads are better than one — driver/navigator roles, mob programming, knowledge transfer protocols.
progressive-execution
Fast approximate results (Phase 1) then slow enriched results (Phase 2).
refactoring
When code needs restructuring but tests must stay green — safe refactoring with test-first verification.
refactoring-suite
When you need to restructure code without breaking behavior — complex refactors with strict test verification.
refactoring-workflow
Master workflow for refactoring at four named depth levels (cosmetic, micro, meso, architectural) that compose as a ladder. Always runs chesterton-fence + style-conformance up front, closes with characterisation tests + minimal-diff + auditor. No skipped rungs.
resilience-patterns
Circuit breaker, retry with backoff, bulkhead isolation, fallback chains, timeouts.
reuse-first
Before writing any new utility, scan the codebase and declared dependencies for an equivalent. Reuse only after fit and edge-case validation.
style-conformance
Detect the project's existing conventions (naming, formatting, errors, logging, tests) and produce a house-style profile downstream skills consult — awareness, not enforcement.
tdd-workflow
When you want tests to drive the design — Red-Green-Refactor cycle with coverage targets.