Menü
Create an Architecture Decision Record
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
| name | create-adr |
| description | Create an Architecture Decision Record |
This workflow guides you through creating an Architecture Decision Record (ADR) to document significant architectural choices.
Determine if an ADR is needed
Create an ADR when making decisions about:
Find the next ADR number
ls docs/adr/*.md | tail -1
Increment the number for your new ADR (e.g., if last is 001-..., use 002).
Copy the template
cp docs/adr/ADR-000_template.md docs/adr/ADR-XXX_short_title.md
Replace XXX with the number (zero-padded to 3 digits) and short-title with a snake-case slug.
Fill in the ADR sections
Add inline code references
In the code that implements the decision, add a comment:
// ARCHITECTURE: [ADR Title] (see docs/adr/ADR-XXX_title.md)
// Brief explanation of how this code relates to the decision
Update the ADR index
Edit docs/adr/README.md to add your new ADR to the index:
- [ADR-XXX](ADR-XXX_title.md) - [Short Description]
Commit the ADR
Commit the ADR with your implementation changes, or as a separate commit:
git add docs/adr/XXX_*.md docs/adr/README.md
git commit -m "docs: add ADR-XXX for [decision]"
Add or revise lookup indexes in `src/data.ts` for upstream data. Use when need to expose a new reverse lookup such as 'what objects yield item X', decide between lazy `ReverseIndex` and constructor-built maps, add a public accessor near similar helpers, or update tests/components that consume the new index.
Prepare and open a pull request from the current local branch by analyzing the diff against a target branch, extracting architectural intent from local docs like ADRs or tech specs, drafting a reviewer-facing PR body, pushing the branch, checking for an existing PR, and creating a draft PR by default.
Diagnose JavaScript/TypeScript heap growth, Vitest OOMs, hanging test processes, async lifetime leaks, and worker-pressure failures in Node/Svelte repos. Use when requests mention memory leaks, runaway heap, `JavaScript heap out of memory`, `--logHeapUsage`, tests that pass but never exit, heavy happy-dom rendering, stale module caches or stores, missing teardown or reset logic, or CI failures that disappear with fewer workers.
Create comprehensive, developer-focused architectural documentation.
Investigate and fix manual or CI schema test failures in `src/schema.test.ts` and `src/mod-schema.test.ts`, especially after upstream Cataclysm-BN data changes.
Create issue