Menú
Scaffold a new plugin in this repository with all required wiring. Use when creating a new plugin from scratch. Do not use for adding skills to an existing plugin or for modifying plugin metadata.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | scaffold-plugin |
| description | Scaffold a new plugin in this repository with all required wiring. Use when creating a new plugin from scratch. Do not use for adding skills to an existing plugin or for modifying plugin metadata. |
| allowed-tools | ["Read","Write","Edit","Bash","Glob","Grep","AskUserQuestion"] |
Create a new plugin with all the required files and registry wiring so it is ready for skills to be added.
Ask the user for the plugin name if not already provided. The name must:
trogonstack-Ask for a one-line description if not already provided.
plugins/{plugin-name}/
├── .claude-plugin/
│ └── plugin.json
├── skills/ (empty, ready for skills)
└── README.md
Do NOT create a CHANGELOG.md — release-please manages that automatically.
{
"name": "{plugin-name}",
"description": "{description}",
"version": "0.0.1",
"author": {
"name": "TrogonStack",
"url": "https://github.com/TrogonStack"
}
}
# {plugin-name}
{description}
```bash
claude plugin install {plugin-name}@trogonstack
```
Add an entry to .claude-plugin/marketplace.json in the plugins array:
{
"name": "{plugin-name}",
"description": "{description}",
"source": "./plugins/{plugin-name}",
"category": "development"
}
Add the package to .github/release-please-config.json in the packages object:
"plugins/{plugin-name}": {
"component": "{plugin-name}"
}
Add the initial version to .github/release-please-manifest.json:
"plugins/{plugin-name}": "0.0.1"
It must be 0.0.1.
Use conventional commit format:
feat({plugin-name}): scaffold plugin for {short purpose}
plugins/{plugin-name}/plugins/{plugin-name}/.claude-plugin/plugin.json exists with correct name, description, version 0.0.1, and authorplugins/{plugin-name}/README.md exists with install commandplugins/{plugin-name}/skills/ directory exists (empty).claude-plugin/marketplace.json has the new plugin entry.github/release-please-config.json has the new package.github/release-please-manifest.json has the new version entry at 0.0.1Ask structured questions one at a time to gather requirements, context, or clarification. Each question includes the intention behind it and current assumptions. Use when the user wants to be interviewed about a topic, gather requirements, or needs help thinking through a problem step by step.
Design new Datadog dashboards, redesign existing ones, or audit dashboards for operational readiness. Covers widget selection, layout organization, template variables, group structure, tab organization, alert threshold validation, and zero-knowledge readability. Uses pup CLI for inspecting dashboards and validating designs. Use when designing new dashboards, redesigning existing ones, auditing before on-call handoff, or reviewing after dashboard changes. Do not use for: (1) Datadog agent installation or configuration, (2) monitor/alert rule design, (3) APM instrumentation or tracing setup, (4) log pipeline configuration.
Review or create event definitions for event-driven architecture. Covers event names, payload field names, event_type identity, stream naming boundaries, and record metadata/context/payload placement for both domain events (event-sourcing) and integration events (cross-service). Use when designing a new event definition, reviewing an existing event definition, or auditing event definition consistency across a catalog. Do not use for full event modeling workflows (use trogonstack-eventmodeling skills), event schema evolution or migration strategy, or event store implementation design.
Step 6 of Event Modeling - Apply Conway's Law with swimlanes. Organize events into autonomous system parts that different teams can independently own. Use after defining inputs/outputs. Do not use for: planning feature slice implementation order (use eventmodeling-slicing-event-models) or defining command/read model boundaries (use eventmodeling-designing-event-models).
Step 1 of Event Modeling - Brainstorm all domain events from requirements. Extract every state-changing event the system could have. Use when starting event modeling from requirements or a new domain. Do not use for: arranging events in sequence (use eventmodeling-plotting-events), designing commands or read models (use eventmodeling-designing-event-models), or when a complete event list already exists.
Step 8 of Event Modeling - Completeness Check. Verify every field has origin and destination. Ensure complete event model before code generation. Use after all scenarios defined. Do not use for: architectural validation against event sourcing principles (use eventmodeling-validating-event-models) or elaborating Given-When-Then specs (use eventmodeling-elaborating-scenarios).