Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From totto2727
Skill for creating and referencing Architecture Decision Records (ADR). Use when recording design decisions, reviewing past architectural choices, or checking existing ADRs before implementation. Common triggers: "create ADR", "record design decision", "check ADR", "architecture decision", "design rationale". Do NOT use for: general documentation, meeting notes, code comments, or changelog entries.
npx claudepluginhub totto2727-org/monorepo --plugin totto2727How this skill is triggered — by the user, by Claude, or both
Slash command
/totto2727:adrThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Important architectural decisions are recorded as ADRs in `doc/adr/`.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Important architectural decisions are recorded as ADRs in doc/adr/.
If the doc/adr/ directory does not exist, create it before writing the first ADR.
!echo "$(date +%Y-%m-%d)-title.md"
All ADR files must have the following YAML frontmatter:
---
confirmed: false
---
| Field | Type | Description |
|---|---|---|
confirmed | boolean | true: Confirmed (generally immutable), false: Proposed (pending review) |
---
confirmed: false
---
# ADR: Title
## Context
Background on why this decision is needed.
## Decision
The specific design decision. May include table design, API design, route design, etc.
## Impact
The scope of impact from this decision. New tables, changes to existing code, new routes, etc.
confirmed: false and confirm after review.confirmed to true.confirmed: true must not be modified in principle.doc/adr/ directory exists (create if missing)YYYY-MM-DD-title.md file in doc/adr/confirmed: false in the frontmatterconfirmed: trueconfirmed: true