Menu
Generate .claude/rules/ files — the constraint layer of the workflow system. Produces focused rule files that hooks enforce and agents follow. Scoped by topic and optionally by file path. Invoked by scaffold or standalone via /generate-rules.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Generate .workflow.js scripts that compose agents into automated pipelines using the Claude Code Workflow DSL. Produces both .js scripts and equivalent skills by default. Covers full DSL surface (agent, pipeline, parallel, phase, log, workflow, budget, args), sandbox constraints, anti-patterns, and production-ready generation guidance. Invoked by scaffold or standalone via /generate-workflows.
Generate hooks native to the target tool's runtime — shell hooks, Python register(ctx), TypeScript pi.on(), hookify rules, or quality tool integrations (ruff, pyright, eslint, pytest). Detects the active tool and emits the correct format. Invoked by scaffold or standalone via /generate-hooks.
Generate tool configurations across all categories — MCP servers, CLI commands, internal code tools, and custom scripts. Maps the project's full tool surface for agents, skills, and workflows.
Generate agent definitions native to the target tool's runtime — Claude Code .claude/agents/*.md, Antigravity/Gemini agents with kind field, Hermes plugin-provided agents via register(ctx), Codex agent definitions, or Pi agent configs. Detects the active tool and emits the correct format. Invoked by scaffold or standalone via /generate-agents.
Generate a project CLAUDE.md file — the shared memory layer of the workflow system. Produces minimal, high-signal instructions that every other primitive (rules, skills, hooks, agents, workflows) references. Invoked by scaffold or standalone via /generate-claudemd.
Generate .claude/skills/ definitions — the capability layer of the workflow system. Identifies recurring workflows and creates SKILL.md files that agents execute and workflows compose. Invoked by scaffold or standalone via /generate-skills.
Baseado na classificação ocupacional SOC
| name | generate-rules |
| description | Generate .claude/rules/ files — the constraint layer of the workflow system. Produces focused rule files that hooks enforce and agents follow. Scoped by topic and optionally by file path. Invoked by scaffold or standalone via /generate-rules. |
Produce .claude/rules/ files. Each rule file is focused on one concern and loaded automatically alongside CLAUDE.md.
Rules are the constraints — the laws that hooks enforce and agents follow. Every rule exists to protect a workflow invariant. Hooks are the enforcement mechanism; rules are what they enforce. Agents consult rules to stay within boundaries.
Rules (constraints)
← Declared from CLAUDE.md standards
→ Enforced by Hooks (automatic)
→ Followed by Agents (by instruction)
→ Respected by Skills (by convention)
Scan results, grill decisions, and the workflow design that determines what invariants need protection. Read .claude/scaffold-decisions.md if it exists — this is the primary source for resolved grill decisions. If standalone, scan first.
Files in .claude/rules/ with optional paths frontmatter for scoping:
---
paths:
- "src/api/**"
- "src/middleware/**"
---
# API Conventions
[Rules specific to these paths]
Generate only categories that apply (based on scan + grill):
| Category | File | When |
|---|---|---|
| Code style | code-style.md | Style rules beyond CLAUDE.md basics |
| Testing | testing.md | Test conventions, coverage requirements, framework-specific patterns |
| Security | security.md | Auth patterns, input validation, secret management |
| Git workflow | git-workflow.md | Commit format, branch naming, PR process |
| Architecture | architecture.md | Module boundaries, dependency rules, patterns |
| Performance | performance.md | Perf-critical paths, caching rules, query patterns |
| Accessibility | accessibility.md | A11y requirements, ARIA patterns, testing |
paths frontmatter to scope rules to relevant directoriesUse paths frontmatter when rules only apply to specific directories:
---
paths:
- "src/components/**" # React components
- "src/hooks/**" # Custom hooks
---
Rules without paths apply globally.
/generate-rules — scan + generate. Use --quick-grill for abbreviated interrogation.
$ARGUMENTS:
--category=security,testing — Generate only specified categories--quick-grill — Abbreviated interrogation (3-5 questions)