claude-plugins

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]

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'

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]

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

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

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]

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.

Disena controles falsificables para graphs y arneses: METHOD observable obligatorio (sin method el estado es 'No ejecutado', nunca un puntaje), falsification_test ejercitado antes de que 'Pasó' signifique algo, satisfacibilidad al nacer (pass, regression o debt_budget decreciente) y proxies que reportan lo que miden. Usar al pedir 'disena controles', 'criterios verificables', 'gate que pueda fallar', 'metricas sin puntajes inventados'. NO para estrategia de testing de software (testing-strategy) ni escenarios BDD (bdd-full-spectrum).

Disciplina de ejecucion de un graph aprobado: gate de aprobacion con graph_id+version exactos, ejecucion por olas topologicas con enforcement de write_set, receipts observables con paths_written, fallos tipados (12 codigos), integracion sin outputs sueltos y loop maker/checker con stop conditions. Usar al pedir 'ejecuta el graph aprobado', 'olas de ejecucion', 'enforcement de write set', 'receipts de nodos'. NO para compilar el DAG (graph-spec-compiler) ni coordinar agent teams (agent-team-orchestration).

Compila un objetivo en lenguaje natural a un DAG validado: objective_contract, nodos con write_set declarado, edges con payload nombrado, olas topologicas, guardian de contexto fresco con manifiesto cerrado y controles falsificables — con validador determinista y paquete de aprobacion APROBAR/REVISAR/CANCELAR. Usar al pedir 'compila mi objetivo en un graph', 'DAG con olas paralelas', 'write sets disjuntos', 'graph engineering'. NO para diagramas mermaid ni para workflows JavaScript (dynamic-workflow-forge).

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 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 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 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 scaffold a Claude Code plugin, design plugin structure, develop a command/agent/hook/MCP/skill, validate a plugin, or review a skill — routing to the plugin-dev plugin under toolkit governance.

This skill should be used when the user asks to review a PR or diff for code quality, comments, tests, error handling, type design, or simplification — routing to pr-review-toolkit's specialized agents under toolkit governance.

This skill should be used when the user asks to create a skill from scratch, optimize an existing skill, run skill evals, or benchmark skill performance — routing to the skill-creator plugin under toolkit governance.

Design current Claude Code hooks with nested matcher-entry schema, five handler types, matcher/if boundaries, permissions-aware policy, portable scripts, MCP timing checks, and deterministic validation.

Scaffold and validate hookify rule files (.claude/hookify.NAME.local.md) that turn a prose guideline into a pattern-matched hook message, via scripts/scaffold_rule.py and scripts/validate_rule.py. Use when the user asks to create, write or validate a hookify rule, or to turn a rule of thumb into an enforced hook. [EXPLICIT]

Scaffold and validate Claude Code hooks blocks deterministically (scripts/scaffold_hook.py, scripts/validate_hook.py) for event-driven automation: format-on-save, file guards, notifications, quality gates. Use when the user asks to create, validate or fix a hook or a settings.json hooks block; hook-engineering owns the design rationale, this skill owns the emitted JSON. [EXPLICIT]