Menu
Triggers on: create a bundle, name a bundle, add a new bundle, scaffold a bundle folder
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | create-bundle |
| description | Triggers on: create a bundle, name a bundle, add a new bundle, scaffold a bundle folder |
| allowed-tools | Read, Bash, Write, Glob |
| argument-hint | [description of what the bundle does] |
You are creating a new bundle in this repository. Follow these steps exactly.
The user's description is in $ARGUMENTS. If empty or unclear, ask the user to describe what the bundle will do before proceeding.
Determine whether the bundle is strictly coupled to a single vendor, runtime, or tool.
aws, terraform, postgres, react, etc.)Choose the bounded context from the controlled vocabulary in references/naming-grammar.md:
api-route | database-schema | frontend-component | release-pipeline | incident-response | infrastructure | observability | identity-access
If no existing term fits, propose a new one with a clear definition and justification. You must add it to references/naming-grammar.md after user approval.
Choose the core purpose from the controlled vocabulary in references/naming-grammar.md:
governance | authoring | scaffolding | auditing | orchestration | maintenance | resolution
If no existing term fits, propose a new one with justification and add it to the vocabulary file after approval.
Combine segments in strict order:
[technology]-[domain]-[purpose]
Rules:
Never use any of these in a bundle name: utils, utilities, helpers, misc, tools, manager, core, common, base
If you find yourself reaching for one of these, revisit Steps 2-3 for more precise vocabulary.
Score the proposed name against the four criteria in references/evaluation-rubric.md:
The name must score 10 or higher out of 12. If below 10, revise by re-examining domain/purpose terms and re-score. After two failed attempts, present options to the user with trade-off analysis.
Always present the following to the user and wait for explicit approval before creating any files:
Proposed bundle name: [name]
Rubric score: [score]/12
- Distinctiveness & Collision Risk: [n]/3
- Breadth without Vagueness: [n]/3
- Semantic Discoverability: [n]/3
- Structural Consistency: [n]/3
Rationale: [brief explanation of segment choices]
Do NOT proceed until the user approves.
On approval, create the bundle directory and manifest:
<name>/ at the repository root<name>/README.md following the template in references/bundle-readme-template.mdThe README.md must include:
# {Display Name} — title-cased human-readable namelow, medium, or high based on blast radiusWhen components are eventually added to a bundle, they must follow these conventions:
| Component | Convention | Separator | Example |
|---|---|---|---|
| Tools | verb_noun | underscore | validate_schema |
| Skills | gerund-concept | kebab-case | reviewing-migrations |
| Agents | role_noun | underscore | schema_reviewer |
Summarize git history, staged diffs, or PR changes into clear, human-readable summaries grouped by theme.
Generate Conventional Commits-compliant commit messages from staged changes or a description of work done.
Build marketing-grade code displays for the Musher marketing site -- split-panel code-then-output layouts, CSS-only syntax highlighting, tabbed views, and terminal chrome. Use when implementing IA Section 3 (Mechanism), building code blocks, creating terminal demos, highlighting YAML/CLI output, or adding copy buttons to code. Triggered by: code display, code block, syntax highlighting, code-then-output, split panel code, terminal chrome, YAML highlight, CLI output, code snippet, tabbed code, multi-language code, mechanism section code, bundle yaml, pipeline yaml, marketing code.
Scaffold marketing page sections from IA definitions into Svelte 5 components. Use when building section components from the Information Architecture, translating archetypes to markup, mapping content slots to elements, or creating section scaffolds. Triggered by: scaffold section, build section, IA to component, section component, hero section, mechanism section, value grid, proof block, community block, CTA block, social proof bar, content slot, archetype component, layout pattern, section scaffold, marketing component.
Analyze CSV data by computing aggregations, filtering rows, and generating readable summaries. Use when working with tabular data files in a container environment where the agent creates and manipulates files directly.
Ensure local development environments match CI/CD environments for consistent behavior including shared version sources, devcontainer reuse in CI, reproducible dependency installation, environment variable parity, Docker image sharing, and lock file enforcement. Use when diagnosing works-on-my-machine issues, designing CI pipelines that mirror local dev, or auditing environment parity. Triggered by: CI alignment, CI environment, works on my machine, CI parity, environment parity, CI local match, GitHub Actions, CI pipeline, CI docker, reproducible builds, lock file, frozen lockfile.