A new way to work with AI across every technical area

When: Use when a feature touches API, persistence, UI, tests, and release safety.

vertical-slice-feature-craft -> unit-test-coverage-forcer -> storybook-automator -> cicd-security-hardener

Use this workflow: vertical-slice-feature-craft -> unit-test-coverage-forcer -> storybook-automator -> cicd-security-hardener to run the new fullstack feature workflow for [feature]. Return changed files, tests run, validation evidence, risks, and changelog notes.

When: Use when improving old code without changing behavior or taking a risky rewrite path.

legacy-code-modernizer -> docstring-artisan -> conventional-commit-helper

Use this workflow: legacy-code-modernizer -> docstring-artisan -> conventional-commit-helper to run the incremental modernization workflow for [module]. Preserve behavior, modernize in small steps, add useful docstrings where they reduce maintenance risk, then prepare a conventional commit and changelog summary.

When: Use when slow data access may require schema, query, ORM, or caching changes.

prisma-typeorm-generator -> sql-query-tuning-doctor -> cache-strategy-selector

Use this workflow: prisma-typeorm-generator -> sql-query-tuning-doctor -> cache-strategy-selector to run the data performance workflow for [query or endpoint]. Review ORM model/query shape, diagnose SQL performance, then recommend caching only where it has clear invalidation and consistency rules.

When: Use when connecting to third-party systems, webhooks, queues, or async delivery.

webhook-contract-guardian -> event-driven-orchestrator -> observability-stack-composer

Use this workflow: webhook-contract-guardian -> event-driven-orchestrator -> observability-stack-composer to run the secure external integration workflow for [integration]. Validate contracts, idempotency, retries, event orchestration, failure handling, observability, and operational alerts.

When: Use before committing teams to dates, dependencies, sprint goals, or roadmap order.

backlog-refinement-facilitator -> sprint-capacity-planner -> cross-team-dependency-mapper -> roadmap-priority-orchestrator

Use this workflow: backlog-refinement-facilitator -> sprint-capacity-planner -> cross-team-dependency-mapper -> roadmap-priority-orchestrator to run the delivery planning workflow for [initiative]. Refine backlog items, estimate capacity, map cross-team dependencies, and recommend roadmap priority with trade-offs and risks.

When: Use when analysis must become a decision, metric, dashboard, or governed experiment.

exploratory-data-analysis-guide -> ab-test-evaluator -> kpi-dashboard-storyliner -> ml-experiment-tracking-governor

Use this workflow: exploratory-data-analysis-guide -> ab-test-evaluator -> kpi-dashboard-storyliner -> ml-experiment-tracking-governor to run the data science delivery workflow for [dataset or experiment]. Produce EDA findings, experiment validity checks, KPI dashboard story, and tracking/governance recommendations.

When: Use when papers, grants, or manuscripts need evidence mapping, claim calibration, reviewer objections, and revision strategy.

literature-evidence-mapper -> scientific-claim-auditor -> grant-manuscript-reviewer

Use this workflow: literature-evidence-mapper -> scientific-claim-auditor -> grant-manuscript-reviewer to run the scientific research review workflow for [paper, grant, or research question]. Map the evidence, audit claim strength and causal language, identify missing controls or citations, then recommend manuscript or grant revisions with validation evidence.

When: Use when research data, notebooks, simulations, or calculations need provenance, rerun evidence, unit checks, and sanity validation.

research-data-cleanroom -> computational-notebook-reproducer -> physics-model-sanity-checker

Use this workflow: research-data-cleanroom -> computational-notebook-reproducer -> physics-model-sanity-checker to run the computational science reproducibility workflow for [dataset, notebook, or simulation]. Preserve raw data, document cleaning, make the notebook rerunnable, check model assumptions or units, and return validation evidence plus residual risks.

When: Use when you just received a repository or project and need to understand what it is before planning or changing anything.

repository-intake-cartographer -> architecture-concern-radar -> technical-due-diligence-assessor -> project-kickoff-charter-builder

Use this workflow: repository-intake-cartographer -> architecture-concern-radar -> technical-due-diligence-assessor -> project-kickoff-charter-builder to run the unknown project intake workflow for [repository or project]. Scan files and docs first, map the stack, architecture, entrypoints, scripts, dependencies, risks, unknowns, and delivery concerns, then produce an onboarding brief, evidence-backed concern matrix, kickoff charter, and next investigation steps.

When: Use when front-end patterns are scattered and the team needs a centralized design system that contributors can learn and follow.

ui-pattern-inventory-mapper -> design-token-governor -> design-system-didactic-centralizer -> storybook-automator

Use this workflow: ui-pattern-inventory-mapper -> design-token-governor -> design-system-didactic-centralizer -> storybook-automator to centralize the front-end design system for [project]. Inventory current UI patterns, normalize tokens and component rules, create didactic usage guidance for contributors, define migration steps, and add Storybook/documentation coverage with validation evidence.

When: Use when a student or developer needs to work in a programming language, framework, or repository they do not know yet.

repository-intake-cartographer -> language-ramp-up-guide -> programming-concept-explainer -> docstring-artisan

Use this workflow: repository-intake-cartographer -> language-ramp-up-guide -> programming-concept-explainer -> docstring-artisan to run the new language ramp-up workflow for [language, repository, or task]. Map the project and language conventions, explain unfamiliar syntax and concepts, identify safe first tasks, and add learner-friendly documentation with validation evidence.

When: Use when code needs to be easier for students, juniors, or new language learners to understand without changing behavior.

programming-concept-explainer -> didactic-code-simplifier -> docstring-artisan

Use this workflow: programming-concept-explainer -> didactic-code-simplifier -> docstring-artisan to run the didactic code simplification workflow for [code sample or module]. Explain the concept, simplify the code while preserving behavior, add useful comments or docstrings, and return before/after reasoning plus validation evidence.

When: Use when a teacher or mentor needs to plan, create, validate, or review programming exercises and assessments.

learning-path-curriculum-designer -> exercise-lab-builder -> assessment-rubric-reviewer -> unit-test-coverage-forcer

Use this workflow: learning-path-curriculum-designer -> exercise-lab-builder -> assessment-rubric-reviewer -> unit-test-coverage-forcer to run the teacher exercise studio workflow for [topic, language, or class]. Plan the learning path, create exercises with starter code, hints, tests, teacher notes, and rubrics, then review assessment fairness and validation evidence.

When: Use when starting a project, evaluating a client request, or deciding whether work is ready to build.

project-kickoff-charter-builder -> scope-readiness-checker -> technical-due-diligence-assessor -> delivery-feasibility-evaluator

Use this workflow: project-kickoff-charter-builder -> scope-readiness-checker -> technical-due-diligence-assessor -> delivery-feasibility-evaluator to run the project start and evaluation workflow for [project]. Build the kickoff charter, assess scope readiness, perform technical due diligence, and evaluate delivery feasibility.

When: Use when someone asks 'what is missing?' or 'what necessity am I not seeing?' before implementation.

gap-discovery-facilitator -> hidden-requirement-radar -> scope-readiness-checker

Use this workflow: gap-discovery-facilitator -> hidden-requirement-radar -> scope-readiness-checker to run the diagnostic pre-build workflow for [idea or plan]. Identify visible gaps, hidden requirements, missing owners, risk areas, validation gaps, rollout needs, and readiness blockers.

When: Use when asking what breaks first at 100k users or before a growth event.

scalability-failure-profiler -> cache-strategy-selector -> observability-stack-composer

Use this workflow: scalability-failure-profiler -> cache-strategy-selector -> observability-stack-composer to run the scale readiness workflow for [system]. State traffic assumptions, rank first failure points, decide whether caching is justified, and define missing metrics, dashboards, alerts, and load-test evidence.

When: Use when bringing juniors into a project without exposing them to unclear or high-risk work.

junior-onboarding-path-builder -> backlog-refinement-facilitator -> conventional-commit-helper

Use this workflow: junior-onboarding-path-builder -> backlog-refinement-facilitator -> conventional-commit-helper to run the junior ramp-up workflow for [team or project]. Create a 30/60/90 path, safe starter tasks, review checkpoints, mentorship rhythm, backlog items, and commit conventions.