claude-plugins

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 '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.

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]

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]

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'

Adversarial consistency audit of a multi-document package across symbol lineage, bidirectional cross-references, brand discipline and naming drift, via scripts/audit_full.sh and the four dimensional audit_*.sh scripts. Use when the user asks to audit a documentation, proposal or discovery package for orphan references, asymmetric links or naming drift before release. [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 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 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]

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 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]

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'

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.

Demo skill that loads.

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]

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

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]

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'

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.

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]