create-custom-tooling

/create-custom-tooling — Pattern-Based Tooling Generation

Purpose: Transform recurring code patterns detected during /audit-workflow into reusable project-specific skills, slash commands, or hooks.

Command: /create-custom-tooling [skill|command|hook] [pattern-name] [--from-audit <epic-slug>]

When to use:

• After /audit-workflow identifies recurring patterns (3+ occurrences)
• When you notice repetitive code structures across features
• To codify project-specific conventions into reusable tools

---

Check for audit reports: !ls -la epics/*/audit-report.xml 2>/dev/null | head -5

Existing custom tooling:

• Skills: !ls .claude/skills/project-custom/ 2>/dev/null || echo "none"
• Commands: !ls .claude/commands/project-custom/ 2>/dev/null || echo "none"
• Hooks: !cat .claude/settings.json 2>/dev/null | grep -A5 '"hooks"' || echo "none"

Tooling Types:

• Skill: Reusable knowledge/templates that Claude loads on-demand (e.g., service boilerplate, CRUD patterns)
• Command: Executable slash command for specific actions (e.g., /generate-crud, /create-migration)
• Hook: Automated triggers on tool events (e.g., auto-format on file save, validate on commit)

Step 1: Parse Arguments and Determine Mode

Parse $ARGUMENTS:

const args = "$ARGUMENTS".trim().split(/\s+/);
const toolingType = args[0]; // skill, command, or hook
const patternName = args[1]; // e.g., "service-boilerplate"
const fromAuditFlag = args.includes('--from-audit');
const epicSlug = fromAuditFlag ? args[args.indexOf('--from-audit') + 1] : null;

If no arguments provided, enter discovery mode:

{
  "question": "What type of tooling do you want to create?",
  "header": "Tooling Type",
  "multiSelect": false,
  "options": [
    {"label": "Skill", "description": "Reusable knowledge/templates (e.g., service boilerplate)"},
    {"label": "Command", "description": "Executable slash command (e.g., /generate-crud)"},
    {"label": "Hook", "description": "Automated trigger on tool events (e.g., auto-lint)"}
  ]
}