Menü
Scaffold the rules-ex extended-rules infrastructure (.claude/rules/rules-ex-authoring.md and .claude/rules-ex/README.md) required by the engineering plugin's inject-extended-rules hook.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Record an architecture/design decision as an ADR (Architecture Decision Record) in the target repository's docs/adr/. Use when the user wants to document a design decision, its alternatives and consequences, or says "record this decision" / "write an ADR".
Generate a self-contained HTML manual-testing guide for an implemented change — environment setup, a visual test-flow diagram, step-by-step scenarios with expected results, and interactive pass/fail checkboxes with a Markdown results export. Use when the user wants to verify an implementation by hand, asks "how do I test this", or wants a verification document for a feature/branch/PR.
Generate a self-contained HTML onboarding tour of a repository — architecture diagram, directory map, key flow walkthroughs, and a recommended reading order — for new team members. Use when the user wants onboarding material, asks for a codebase overview/architecture tour, or wants to explain a repo to someone new.
Generate a self-contained HTML code-review guide for the current changes — big-picture overview, architecture diagram of affected modules, a file/class responsibility map, and an annotated change walkthrough — so a reviewer can grasp the whole implementation before diving into the diff. Use when the user wants review material for a branch/PR, asks to "explain the changes for review", or wants a visual summary of what was implemented where.
Investigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".
Capture a reusable, non-obvious project insight into the rules home where it will auto-inject in future sessions. Use when investigation or implementation surfaces knowledge worth persisting (a gotcha, a convention, the "why" behind a decision), or when the user asks to remember a project learning.
| name | setup-rules-ex |
| description | Scaffold the rules-ex extended-rules infrastructure (.claude/rules/rules-ex-authoring.md and .claude/rules-ex/README.md) required by the engineering plugin's inject-extended-rules hook. |
| disable-model-invocation | true |
| allowed-tools | Read Write |
Scaffold the two files that enable the rules-ex extended-rules system for this
project. Both files are templates — they will not be overwritten if they already
exist. The canonical template content lives in this skill's assets/templates/
folder (also used by the setup-all skill's Phase 4 — treat it as the single
source of truth and edit it there, not inline in either SKILL.md).
What gets created:
.claude/rules/rules-ex-authoring.md — a native path-scoped rule that
auto-injects an authoring guide whenever you Read/Edit a file under
.claude/rules-ex/. Required so the guide fires for the current repo
(native .claude/rules files only govern the repo they live in)..claude/rules-ex/README.md — explains what the rules-ex folder is and how
to author rules in it. Has no paths: front matter intentionally, so the hook
ignores it.Read .claude/rules/rules-ex-authoring.md.
assets/templates/rules-ex-authoring.md (in this
skill's folder) and write its exact contents to .claude/rules/rules-ex-authoring.md.Read .claude/rules-ex/README.md.
assets/templates/rules-ex-readme.md (in this
skill's folder) and write its exact contents to .claude/rules-ex/README.md.Print a summary table after completing both steps:
| File | Status |
|---|---|
.claude/rules/rules-ex-authoring.md | created / already existed |
.claude/rules-ex/README.md | created / already existed |
Then remind the user:
*.md files under .claude/rules-ex/.
Each file must have a paths: front matter (workspace-relative globs) — see
the authoring guide that auto-injects when you edit files there.inject-extended-rules hook fires on Read/Edit/Write; rules take effect
immediately in the current session without a restart.