Applies Domain-Driven Design tactical and strategic patterns to model complex business domains. Identifies bounded contexts, aggregates, domain events, and establishes ubiquitous language shared by developers and domain experts. [EXPLICIT] Trigger: 'bounded context', 'aggregate', 'domain event', 'ubiquitous language', 'DDD'

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'

Designs data architecture, governance frameworks, quality standards, and pipeline strategies. Covers data modeling, cataloging, lineage tracking, and analytics enablement. [EXPLICIT] Trigger: 'data architecture', 'data governance', 'data quality', 'data pipeline', 'data strategy'

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.

Data pipeline architecture — ingestion, orchestration, quality, lineage, SLAs. Use when the user asks to 'design data pipelines', 'architect ingestion', 'set up orchestration', 'plan data lake', 'design lakehouse', or mentions Airflow, Dagster, CDC, data lineage, or pipeline SLAs. [EXPLICIT]

Router de extensiones Claude Code para decidir y componer command/skill, scope, context fork y controles de invocacion. Deriva la autoria a claude-command-authoring o claude-skill-authoring y permisos a tool-permission-policy; no cubre Claude Platform.

Designs frontend module boundaries, interface contracts, and composition patterns for scalable component hierarchies. Covers smart/dumb patterns, compound components, and dependency injection. [EXPLICIT] Trigger: 'component architecture', 'module boundary', 'composition pattern', 'interface contract'

Cloud-native design -- containers, service mesh, serverless, multi-cloud, FinOps. Use when the user asks to 'design cloud-native architecture', 'containerize the application', 'evaluate service mesh', 'plan serverless migration', 'implement multi-cloud strategy', 'optimize cloud costs', or mentions Kubernetes, Istio, Docker, Helm, Terraform, FinOps, or 12-factor. [EXPLICIT]

Cloud migration planning -- 7R assessment, workload classification, wave planning, cutover. Use when the user asks to 'plan cloud migration', 'assess workloads for migration', 'design landing zone', 'create migration waves', 'plan cutover strategy', or mentions 7R, rehost, replatform, refactor, lift-and-shift, or migration factory. [EXPLICIT]

This skill should be used when the user asks to 'author a Claude Code skill', 'write a SKILL.md', 'design skill frontmatter', 'choose allowed-tools or context fork for a skill', 'convert a command into a skill', or 'make a skill pass validation'. Teaching companion for SKILL.md authoring; defers heavy repair/hardening work to toolkit-hardener and packaging to plugin-builder.

Inventory and route Claude Code, Cowork, and Claude Platform capabilities, including Messages API runtime, server/client tools, Files/PDF, context/cache/compaction, skills, commands, agents, hooks, MCP, SDK, plugins, and output. Cowork claims still require a Cowork-session probe.

This skill should be used when the user asks to 'create a slash command', 'author a Claude Code command', 'decide command vs skill', 'choose project vs user scope', 'version custom commands for my team', or 'design command frontmatter'. Covers commands/*.md authoring and the command-vs-skill decision; unifies the custom-commands kata with the extension decision tree.

This skill should be used when the user asks to build, audit, or harden a Claude Platform Messages API client-side tool execution loop, handle tool_use and tool_result messages, correlate tool_use_id values, stream partial tool JSON, enforce strict:true schemas, handle stop_reason values, or design retry/error behavior for Anthropic Messages API tools. Do not use it for Claude Code headless CLI or Agent SDK automation, prompt-cache design, MCP server design, tool catalog descriptions, or individual tool implementations.

Use this skill to design, audit, or validate Claude Platform server-tool plans for server-tools, web search, web fetch, code execution, advisor, tool search, or the mechanical server-side portion of programmatic tool calling. It owns server_tool_use/result correlation, pause_turn continuation, versioned definitions, caller/container rules, domain controls, and source-supported privacy, retention, and cost controls. It does not own the application agent loop; route loop ordering and budgets to claude-api-tool-runtime and katas-deterministic-agent-loop.

This skill should be used when the user asks to design, audit, or harden Claude Platform Files API upload/reference/lifecycle flows or PDF document requests using file_id, URL, or base64 document sources. Use it for file metadata, deletion, conditional downloadability, PDF request limits, MIME-to-content-block contracts, and source/platform compatibility. Do not use it for text-editor operations, fetching web pages, generic object storage, document authoring, or arbitrary binary processing.