メニュー
Record an architectural design decision in docs/design-decisions/. Use when a code change involves a non-trivial design choice, trade-off, or new pattern that future contributors should understand.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | record-decision |
| description | Record an architectural design decision in docs/design-decisions/. Use when a code change involves a non-trivial design choice, trade-off, or new pattern that future contributors should understand. |
| argument-hint | Short decision title and the domain file, e.g. 'Paginated recent subtitles in streaming.md' |
Use this skill to add or update design decisions following the project template.
Read the template at docs/design-decisions/TEMPLATE.md to confirm the current structure.
Identify the domain file — decisions are grouped by domain (e.g., fairness.md, calendar.md, handlers.md). Pick the existing file that best fits. If no file matches, create a new one named after the domain.
Read the target file to see existing decisions and avoid duplicates.
Write the decision using this structure:
## <Short Decision Title>
**Decision**: One or two sentences describing **what** was decided.
**Rationale**:
- Bullet points explaining **why**
- Focus on trade-offs, alternatives considered, and benefits
**Implementation**: Where and how the decision is realised in the codebase. Reference file paths, interfaces, method names, and key types.
Append the new decision to the end of the file (before any trailing blank lines).
Keep each decision self-contained — a reader should understand it without reading the rest of the file.
docs/architecture.md or docs-site/ — those describe behaviour, design decisions explain why.Guide for setting up a fake/demo SQLite database with sample data for testing the Night Routine application and taking screenshots. Use this skill when you need to create test data, set up a demo database, take screenshots of the UI, or verify the application with sample assignments and calendar data.
Guide for making changes to the fairness scheduling algorithm. Use this skill when you need to modify how parents are assigned to nights, change decision reasons, adjust the fairness cascade, or modify how babysitter/stats work. Covers all required touchpoints: scheduler, tracker, decision reasons, UI, tests, migrations, and design decisions.