This skill should be used when the user asks to commit, push and open a PR, or clean gone git branches — routing to the commit-commands plugin under toolkit governance.

This skill should be used when the user asks to audit, improve, or update CLAUDE.md files with session learnings — routing to the claude-md-management plugin under toolkit governance.

This skill should be used when the user asks to scaffold or verify a Claude Agent SDK app in Python or TypeScript — routing to the agent-sdk-dev plugin under toolkit governance.

This skill should be used when the user asks to automate Claude Code headlessly, run claude -p in CI or scripts, parse json or stream-json output, use --bare, configure non-interactive permissions, compare CLI vs TypeScript or Python Agent SDK usage, wire MCP or hooks for automation, resume sessions programmatically, or harden reproducible Claude Code automation.

This skill should be used when the user asks to operate Claude Code /goal, write a goal completion condition, compare /goal with /loop, Stop hooks, or auto mode, diagnose a stuck goal loop, set stop conditions, resume or clear an active goal, or define safe continuation gates for autonomous Claude Code sessions.

Generative AI architecture — RAG patterns, LLM orchestration, multi-model tiering, agent workflow design, vector database architecture, knowledge connectors, and GenAI quality assurance. This skill should be used when the user asks to 'design RAG architecture', 'architect LLM system', 'select vector database', 'design AI agents', 'implement knowledge retrieval', 'plan GenAI quality', or mentions RAG, embeddings, vector search, LLM orchestration, agent framework, context-aware generation, hallucination reduction, or multi-model routing. [EXPLICIT]

Functional specifications. MVP modules, 8+ use cases, business rules, acceptance criteria. Data models (relational/NoSQL). [EXPLICIT]

Build on Firebase: Auth, Cloud Functions, Firestore security rules and query optimization, Hosting, Storage, scheduled jobs, emulator suite, and cost control. [EXPLICIT] One of the three target platforms (Firebase + Vercel + Hostinger). Trigger: 'firebase', 'firestore', 'cloud functions', 'firebase auth', 'firebase hosting', 'security rules'.

Cloud financial operations assessment and strategy using FinOps Foundation framework. Use when the user asks to 'assess cloud costs', 'optimize cloud spending', 'FinOps assessment', 'cloud cost analysis', 'rightsizing', 'reservation strategy', 'showback/chargeback model', 'cloud unit economics', 'cost allocation', or mentions 'cloud financial management', 'cost optimization', 'FinOps maturity'. [EXPLICIT]

Performs 7-dimension technical feasibility assessment covering architecture, team capability, timeline, cost, risk, integration, and scalability. [EXPLICIT] Produces go/no-go recommendations with confidence levels. [EXPLICIT] Trigger: 'feasibility', 'technical assessment', 'go/no-go', 'viability'

Event-driven architecture — event catalog, schema registry, eventual consistency, saga, CQRS, event sourcing. Use when the user asks to 'design event-driven system', 'build event catalog', 'implement CQRS', 'design saga patterns', 'set up schema registry', 'implement event sourcing', or mentions Kafka, RabbitMQ, Pulsar, event bus, dead-letter queue, consumer groups, or event replay. [EXPLICIT]

This skill should be used when the user asks to 'map business capabilities', 'build a technology radar', 'define architecture governance', 'prioritize strategic initiatives', or mentions capability mapping, DDD domains, ARB, DORA metrics, or target operating model. [EXPLICIT] It generates enterprise architecture alignment artifacts including capability maps, domain decomposition, governance frameworks, technology radars, and strategic initiative roadmaps. [EXPLICIT] Use this skill whenever the user needs to align technology initiatives with business strategy, even if they don't explicitly ask for 'enterprise architecture'. [EXPLICIT]

This skill should be used when the user asks to create, review, save, or validate Claude Code dynamic workflows, asks to use the Workflow tool, mentions ultracode, /workflows, saved workflows, background workflow runs, resumable workflow orchestration, or needs to distinguish dynamic JavaScript workflows from workflow-forge static slash-command workflows.

Doc-as-code strategy design, documentation taxonomy, content governance, and knowledge base architecture. Use when the user asks to 'design documentation strategy', 'build knowledge base', 'create doc-as-code pipeline', or mentions documentation governance, content taxonomy, or technical writing standards. [EXPLICIT]

Coordinates full analysis pipeline (phases 0-6). Sequences skills 009-023. Manages G1 gate. Does NOT analyze. [EXPLICIT]

DevSecOps pipeline architecture — CI/CD design, shift-left security, supply chain integrity, release management, and compliance automation. Use when the user asks to 'design the CI/CD pipeline', 'integrate security into delivery', 'set up SBOM and artifact signing', 'automate compliance', 'measure DORA metrics', or mentions SAST, SCA, DAST, secrets scanning, IaC scanning, canary deployment, or policy-as-code. [EXPLICIT]

This skill should be used when the user asks to create Claude Code deep links, build claude-cli://open onboarding links, prefill Claude Code prompts with cwd or repo, document clickable runbook links, audit deep-link safety, troubleshoot Claude Code protocol handlers, or choose between deep links, headless claude -p, scripts, channels, hooks, scheduled tasks, or Remote Control.

Designs database schemas, indexing strategies, and data models across the target platforms — relational (MySQL/MariaDB on Hostinger, Postgres/Neon on Vercel) and NoSQL document stores (Firestore on Firebase, MongoDB). [EXPLICIT] Covers normalization, denormalization trade-offs, and query optimization. [EXPLICIT] Trigger: 'database', 'schema', 'data model', 'indexing'

Data quality framework — profiling, validation, anomaly detection, data contracts, SLA monitoring. Use when the user asks to 'design data quality framework', 'set up data contracts', 'plan data validation', 'detect data anomalies', 'define data SLAs', or mentions data profiling, quarantine patterns, or remediation workflows. [EXPLICIT]

Data privacy governance: privacy-by-design, PII/PHI classification and minimization, encryption, anonymization, retention, access evidence, and tamper-evident audit trails. Routes data quality to data-quality and catalog/lineage strategy to data-strategy.