shiplens

Audit naming quality (files, functions, types, variables, folders) without reading the code. Takes names as input and reports what Claude understands from each name alone. Judges three axes: Screaming Architecture (does the name reveal the domain?), Clean Code (full words, intention-revealing, no abbreviations), and Ubiquitous Language (vocabulary consistency across the codebase). Useful to validate that names self-document.

Extracts business rules from a module (backend + frontend) and produces three tables: Product view (business concepts), Backend dev view (type + source), Frontend dev view (type + source). Saves to docs/business-rules/.

Strategic DDD guide for this project (fullstack — backend + frontend share the same bounded contexts). Use to slice the domain into bounded contexts, define ubiquitous language, create a new business module, analyze boundaries between contexts. Tactical patterns follow Clean Architecture (see architecture-backend and architecture-frontend skills).

Runs a Big Picture Event Storming session on a bounded context or the entire codebase (backend + frontend). Discovers domain events, commands, entities, context boundaries, frontend projections (hooks, presenters, views). Produces a structured document in docs/ddd/.

Autonomous frontend feature implementation via spec-driven development. Orchestrates a frontend-planner and a frontend-implementer with architecture-frontend preloaded. Applies Humble Object pattern to views, MVVM structure with Presenter classes + Zod ViewModels, singleton registry DI. Consumes specs produced by /product-manager. For backend features, use /implement-feature instead.

Feature challenge and specification. Use to define a feature, write acceptance criteria, scope a ticket, produce INVEST specs with custom DSL in docs/specs/. Refuses vague scopes and forces clarification.

Discover implicit team conventions (tribal knowledge) in a codebase. Spawns parallel sub-agents to analyze 6 axes: naming, error handling, testing, architecture, git workflow, and code idioms. Generates a structured report in docs/tribal-knowledge/.

Clean Architecture guide for the React frontend. Use to create frontend modules, entities, use cases, presenters, hooks, views, gateways, guards. Applies Humble Object pattern (Uncle Bob) — views are untestable glue, hooks and presenters hold all logic. For backend architecture, use architecture-backend instead.

Clean Architecture (Uncle Bob) guide for the NestJS backend. Use to create backend modules, entities, use cases, presenters, controllers, gateways, guards. Contains tactical patterns and structure conventions. For frontend architecture, use architecture-frontend instead.

Local self-review of modified code. 5 sequential audits (Clean Arch, DDD, SOLID, Testing, Code Quality) with report. Ideal before creating a PR.

Autonomous backend feature implementation via spec-driven development. Orchestrates a planner and a TDD implementer with architecture-backend preloaded. Consumes specs produced by /product-manager. For frontend features, use /implement-feature-frontend instead.

Structured refactoring with Mikado, Strangler Fig, and Parallel Change patterns. Decomposes a blocked refactoring into a prerequisite tree, produces an independent branch plan, and executes in TDD. Takes P3 items from debug-workflow or a direct restructuring request as input.

Guide for creating effective skills. Use when users want to create a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Structured progressive debugging workflow. Bug discovery, priority classification, and independent branch plan without regressions. Adapted to the Shiplens stack (NestJS 11, Prisma, Vitest).

Sync DDD documentation (event storming, ubiquitous language) to the GitHub wiki. Clones the wiki repo, updates pages, commits and pushes.

Scan code to detect secrets before commit. Checks tokens, API keys, credentials and sensitive data.

Ship - Commit and Push in one command. Chains staging, conventional commit, and push. Checks quality gates before any commit.

Interactive guide for TDD Detroit School. Use whenever the user asks to write or modify code - new feature, bug fix, debug, refactoring, modification. Activates a RED-GREEN-REFACTOR workflow with validation at each step.

Git worktree management for working on multiple branches in parallel. Create, list, remove, and synchronize worktrees. Isolates in-progress features to avoid conflicts.