25 skills tagged build · lifecycle axis.
Master workflow for any change touching an existing project. Walks the Aparigraha gates end-to-end — onboarding, dependency awareness, style detection, reuse-first authoring, surgical diff, post-execution audit — by orchestrating the foundation `pragmatism` philosophy and the `25-pragmatism` category skills. Contains no implementation logic.
Implement API handlers/controllers based on an existing API contract (OpenAPI spec). Generates route handlers, validation, and error handling.
Implement authentication and authorization safely: JWT, OAuth2, RBAC, or API key strategies.
Design and implement caching layers using Redis, Memcached, or in- memory caches with proper invalidation strategies.
Before deleting, refactoring, or "cleaning up" code that looks unused, redundant, or weird, investigate why it exists. Produces a why-it-exists memo plus an edge-case checklist that must be confirmed before any change to the existing code is committed. Implements the Chesterton's-Fence side of Validate-Before-Trust under Aparigraha.
Remove noise, enforce formatting, and safely rename identifiers. A mixed-mode skill: cosmetic fixes run in Eco, renaming runs in Power.
Generate production-ready code from specifications, templates, and domain models. Enforces language idioms, DRY principles, and project conventions.
Implement data access layers using the Repository pattern. Prevents N+1 queries, manages transactions, and optimizes reads.
Database performance tuning: index analysis, query plan optimization, connection pooling, and configuration tuning.
Mine the project's declared dependencies (BOM, package.json, requirements.txt, Pipfile, go.mod, Cargo.toml, etc.) and produce a curated inventory of the utilities they expose, so reuse-first and other Aparigraha skills can decide quickly without rediscovering the graph each time. Consults; never auto-rewrites.
Standardize error types, logging formats, and error response structures across the project.
Master workflow for shipping a feature end-to-end. Orchestrates PRD authoring, task decomposition, TDD implementation, code review, and the release pipeline as a single named sequence ending in an audit. Contains no implementation logic.
Analyze, generate, and improve inline code documentation including JSDoc, docstrings, type annotations, and comment quality.
Generate the smallest correct change that solves the stated problem. No drive-by formatting, no opportunistic renames, no "while I'm here" expansions. Implements the Surgical-Before-Sweeping gate of Aparigraha with diff-size guardrails, scope checks, and reversibility validation.
Name scripts, tools, and files so their name tells you when and how to use them. CLI tools you run are verb-noun; imported libraries are nouns; internal helpers start with an underscore. Apply when adding or renaming any script.
Facilitate effective pair and mob programming sessions including role rotation, session structure, and knowledge transfer practices.
Return fast approximate results immediately (Phase 1), then enhance with slower enriched results (Phase 2). Phase 1 is standalone. Phase 2 is optional enhancement. If Phase 2 fails, Phase 1 stands.
Safely restructure code while preserving external behavior. Applies proven refactoring patterns with mandatory test verification.
Complex refactoring operations with strict test verification. Every refactor follows: Test → Refactor → Test → Revert-on-Fail.
Master workflow for refactoring at four named depth levels — cosmetic, micro, meso, architectural — that compose as a ladder. Always runs chesterton-fence and style-conformance up front; always closes with a characterisation/test safety net, minimal-diff scope checks, and the auditor. Contains no implementation logic; orchestrates only existing category skills.
Graceful degradation when external dependencies fail. Circuit breaker state machine, retry with backoff, bulkhead isolation, fallback chains, and timeout management.
Make a web page work on every screen — phone to ultrawide — without text or media ever escaping its container. Invoke whenever building or changing any page/CSS that will be viewed on more than one screen size (i.e. always). Overflow and word-wrap bugs are treated as correctness bugs, not polish.
Before authoring any new utility, helper, wrapper, or abstraction, scan the project's existing source and declared dependencies for an equivalent. Reuse only after fit and edge-case validation; otherwise document why nothing fit and write fresh. Implements the Check-Before-Create and Validate-Before-Trust gates of Aparigraha.
Detect the project's existing coding conventions — naming, formatting, error handling, logging, test structure, comment style, module layout — and produce a "house style profile" that downstream skills consult when writing or modifying code. Awareness, not enforcement: the agent conforms within the scope of the change and surfaces deviations rather than auto-fixing them.
Drive implementation through the Red-Green-Refactor cycle. Write failing tests first, implement minimal code to pass, then refactor.