ai-design-context 0.4.0

package/observations/finance/market-interface-adaptive-trading-surfaces.md

@@ -0,0 +1,55 @@
+---
+id: OBS-00014
+alias: OBS-MARKET-ADAPTIVE-TRADING
+slug: market-interface-adaptive-trading-surfaces
+title: Market Interfaces Adapt Trading Controls By Density And Risk
+object_type: observation
+status: draft
+version: 0.1.0
+category: ux
+tags:
+  - finance
+  - market-interface
+  - responsive
+  - trading
+created_at: 2026-08-12
+updated_at: 2026-08-12
+last_reviewed_at: 2026-08-12
+owner: ai-design-rules
+maturity: seed
+risk_level: high
+platform:
+  - web
+product_type:
+  - fintech
+  - trading
+surface:
+  - market-detail
+  - chart
+  - order-entry
+applies_to:
+  - dense-market-interfaces
+does_not_apply_to:
+  - static-analytics-cards
+relationships: []
+---
+
+# Market Interfaces Adapt Trading Controls By Density And Risk
+
+## Source
+
+Market-interface charting research and mobile layout review note captured on 2026-08-12.
+
+## Observed Behavior
+
+Market-interface research separates product data shapes from chart-engine data shapes, treats the graph as a functional trading surface, and reserves future paths for multi-series and candle/OHLC charts. Mobile behavior shifts dense controls into bottom sheets and tablet modals with tested viewport thresholds instead of squeezing desktop trading controls into a narrow layout.
+
+## Why It May Matter
+
+Finance and market-trading interfaces need responsive contracts that preserve decision context, not only visual resizing. Dense chart, filter, and order controls require explicit mobile presentations, focus recovery, safe-area spacing, and disabled/frozen states.
+
+## Evidence
+
+- Market-interface charting note captured on 2026-08-12.
+- Mobile dropdown test note captured on 2026-08-12.
+- Compact trading layout test note captured on 2026-08-12.

package/observations/interaction/chrome-scoped-view-transitions.md

@@ -0,0 +1,52 @@
+---
+id: OBS-00009
+alias: OBS-CHROME-SCOPED-TRANSITIONS
+slug: chrome-scoped-view-transitions
+title: Scoped View Transitions Preserve Context During Local State Change
+object_type: observation
+status: draft
+version: 0.1.0
+category: ux
+tags:
+  - motion
+  - web
+  - state-transition
+  - context
+created_at: 2026-07-24
+updated_at: 2026-07-24
+last_reviewed_at: 2026-07-24
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - web
+product_type:
+  - consumer
+  - productivity
+surface:
+  - state-transition
+applies_to:
+  - local-state-change
+does_not_apply_to:
+  - unsupported-browser-assumptions
+relationships: []
+---
+
+# Scoped View Transitions Preserve Context During Local State Change
+
+## Source
+
+Chrome 147 element-scoped View Transition documentation.
+
+## Observed Behavior
+
+Element-scoped transitions can animate a specific subtree while the rest of the page remains interactive. Chrome positions this capability as useful for local state morphing and micro-interactions that preserve context.
+
+## Why It May Matter
+
+The product value of motion is continuity, not animation volume. A transition should make an object's state or location easier to follow without blocking unrelated work, and implementation guidance must account for platform support.
+
+## Evidence
+
+- https://developer.chrome.com/blog/element-scoped-view-transitions
+- https://developer.chrome.com/docs/css-ui/view-transitions/element-scoped-view-transitions

package/observations/interaction/figma-motion-as-system-capability.md

@@ -0,0 +1,53 @@
+---
+id: OBS-00008
+alias: OBS-FIGMA-MOTION-SYSTEM
+slug: figma-motion-as-system-capability
+title: Figma Treats Motion As A Design System Capability
+object_type: observation
+status: draft
+version: 0.1.0
+category: ux
+tags:
+  - motion
+  - design-system
+  - handoff
+  - figma
+created_at: 2026-07-24
+updated_at: 2026-07-24
+last_reviewed_at: 2026-07-24
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - web
+  - mobile
+product_type:
+  - consumer
+  - productivity
+surface:
+  - state-transition
+applies_to:
+  - purposeful-product-motion
+does_not_apply_to:
+  - decorative-animation
+relationships: []
+---
+
+# Figma Treats Motion As A Design System Capability
+
+## Source
+
+Figma Motion launch materials from Config 2026.
+
+## Observed Behavior
+
+Figma places timelines, easing, timing, and keyframes beside components and variables. Motion can be reused through systems, inspected during handoff, and exported to implementation formats instead of being described informally after static screens are complete.
+
+## Why It May Matter
+
+Motion becomes more reliable when its purpose and parameters are part of the component or transition contract. Agents should specify the state relationship, implementation values, and reduced-motion behavior rather than request generic polish.
+
+## Evidence
+
+- https://www.figma.com/blog/introducing-figma-motion/
+- https://www.figma.com/blog/config-2026-recap/

package/observations/mobile/mobile-bottom-sheet-choice-contracts.md

@@ -0,0 +1,55 @@
+---
+id: OBS-00016
+alias: OBS-MOBILE-SHEET-CHOICE
+slug: mobile-bottom-sheet-choice-contracts
+title: Mobile Choice Controls Need A Bottom-Sheet Contract
+object_type: observation
+status: draft
+version: 0.1.0
+category: ux
+tags:
+  - mobile
+  - bottom-sheet
+  - responsive
+  - accessibility
+created_at: 2026-08-12
+updated_at: 2026-08-12
+last_reviewed_at: 2026-08-12
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - mobile-web
+product_type:
+  - fintech
+  - consumer
+surface:
+  - chooser
+  - filter
+  - action-sheet
+applies_to:
+  - compact-mobile-choice-controls
+does_not_apply_to:
+  - simple-inline-binary-toggles
+relationships: []
+---
+
+# Mobile Choice Controls Need A Bottom-Sheet Contract
+
+## Source
+
+Mobile dropdown, compact layout, and media-capture planning note captured on 2026-08-12.
+
+## Observed Behavior
+
+Dense choice controls become full-width mobile sheets with safe-area space, reachable rows, labels, close controls, and tested viewport thresholds. In chat/media capture, the attachment sheet owns gallery/file choice while voice and video recording remain part of the existing composer state instead of becoming a parallel composer.
+
+## Why It May Matter
+
+Mobile sheets are often introduced as visual polish, but they define an interaction contract: ownership, focus, safe-area spacing, row target size, dismissal, and relationship to the triggering control.
+
+## Evidence
+
+- Mobile dropdown test note captured on 2026-08-12.
+- Compact layout test note captured on 2026-08-12.
+- Media-capture planning note captured on 2026-08-12.

package/observations/performance/reserved-loading-space.md

@@ -0,0 +1,51 @@
+---
+id: OBS-00002
+alias: OBS-PERF-RESERVED-SPACE
+slug: asynchronous-content-layout-stability
+title: Reserved Loading Space
+object_type: observation
+status: draft
+version: 0.1.0
+category: performance
+tags:
+  - performance
+  - loading
+  - layout-stability
+created_at: 2026-07-14
+updated_at: 2026-07-14
+last_reviewed_at: 2026-07-14
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - web
+product_type:
+  - consumer
+surface:
+  - loading-state
+applies_to:
+  - asynchronous-media
+  - lazy-loaded-content
+  - loading-placeholders
+does_not_apply_to:
+  - user-initiated-layout-changes
+relationships: []
+---
+
+# Reserved Loading Space
+
+## Source
+
+web.dev, Optimize Cumulative Layout Shift.
+
+## Observed Behavior
+
+Asynchronous images, embeds, and other content move visible controls and text when their layout space is unknown before they load. Reserving space with known dimensions or a layout-matching placeholder keeps nearby content stable.
+
+## Why It May Matter
+
+Unexpected movement makes a product feel unreliable and can cause users to lose their place or activate the wrong control. A placeholder only improves the experience when its reserved space approximates the arriving content.
+
+## Evidence
+
+- https://web.dev/articles/optimize-cls

package/observations/product-repos/pinned-ai-design-rules-integration.md

@@ -0,0 +1,49 @@
+---
+id: OBS-00012
+alias: OBS-PINNED-RULES-INTEGRATION
+slug: pinned-ai-design-rules-integration
+title: Mature Codebases Use Pinned AI Design Rules Snapshots
+object_type: observation
+status: draft
+version: 0.1.0
+category: product
+tags:
+  - adoption
+  - agent-workflow
+  - design-rules
+created_at: 2026-08-12
+updated_at: 2026-08-12
+last_reviewed_at: 2026-08-12
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - repository
+product_type:
+  - agent-instructions
+surface:
+  - project-integration
+applies_to:
+  - product-repository-agent-guidance
+does_not_apply_to:
+  - backend-only-maintenance
+relationships: []
+---
+
+# Mature Codebases Use Pinned AI Design Rules Snapshots
+
+## Source
+
+Implementation review notes for AI Design Rules adoption.
+
+## Observed Behavior
+
+AI Design Rules does not need one fixed integration mode. One adoption mode keeps a pinned snapshot under a local design-rules directory. Another uses a local bridge skill that points agents at a minimal snapshot. A third treats the repository as an optional product/design reasoning layer and explicitly keeps local architecture, API, security, routing, testing, and verification rules higher priority.
+
+## Why It May Matter
+
+Adoption works better when AI Design Rules offers integration modes instead of assuming one full starter-kit copy. Product repositories need reproducibility, local precedence, and a lightweight path for narrow UI changes.
+
+## Evidence
+
+- Implementation review note captured on 2026-08-12.

package/observations/visual/apple-liquid-glass-functional-layer.md

@@ -0,0 +1,52 @@
+---
+id: OBS-00005
+alias: OBS-APPLE-LIQUID-GLASS-LAYER
+slug: apple-liquid-glass-functional-layer
+title: Apple Uses Liquid Glass As A Functional Layer
+object_type: observation
+status: draft
+version: 0.1.0
+category: visual
+tags:
+  - apple
+  - liquid-glass
+  - hierarchy
+  - materials
+created_at: 2026-07-24
+updated_at: 2026-07-24
+last_reviewed_at: 2026-07-24
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - apple
+product_type:
+  - consumer
+surface:
+  - navigation
+  - controls
+applies_to:
+  - layered-interface-materials
+does_not_apply_to:
+  - unrestricted-glassmorphism
+relationships: []
+---
+
+# Apple Uses Liquid Glass As A Functional Layer
+
+## Source
+
+Apple Human Interface Guidelines for materials and the WWDC26 design guide.
+
+## Observed Behavior
+
+Apple describes Liquid Glass as a distinct layer for controls and navigation above content. The guidance warns against using the material throughout the content layer and recommends applying custom glass effects sparingly, with accessibility settings such as reduced transparency and increased contrast preserved.
+
+## Why It May Matter
+
+The visible trend is not a license to cover every surface with transparency. Its reusable signal is that expressive material can separate interaction from content when hierarchy, legibility, and platform behavior remain clear.
+
+## Evidence
+
+- https://developer.apple.com/design/human-interface-guidelines/materials
+- https://developer.apple.com/wwdc26/guides/design/

package/observations/visual/chrome-content-first-adaptive-ui.md

@@ -0,0 +1,51 @@
+---
+id: OBS-00007
+alias: OBS-CHROME-CONTENT-FIRST-UI
+slug: chrome-content-first-adaptive-ui
+title: Modern Web UI Maximizes Content And Adapts To Form Factor
+object_type: observation
+status: draft
+version: 0.1.0
+category: visual
+tags:
+  - web
+  - content-first
+  - responsive
+  - layered-ui
+created_at: 2026-07-24
+updated_at: 2026-07-24
+last_reviewed_at: 2026-07-24
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - web
+product_type:
+  - consumer
+  - productivity
+surface:
+  - product-ui
+applies_to:
+  - responsive-web-apps
+does_not_apply_to:
+  - hiding-required-actions
+relationships: []
+---
+
+# Modern Web UI Maximizes Content And Adapts To Form Factor
+
+## Source
+
+Chrome for Developers, What's new in web UI at Google I/O 2026.
+
+## Observed Behavior
+
+The guidance groups new UI capabilities around guided navigation, reduced visual noise, layered secondary actions, and adaptation to form factor and input method. It also distinguishes available capabilities from experimental features.
+
+## Why It May Matter
+
+A modern surface should not gain perceived quality by adding chrome. It should preserve content priority, keep required actions discoverable, and adapt layout and interaction to the active device rather than only shrinking dimensions.
+
+## Evidence
+
+- https://developer.chrome.com/blog/new-in-web-ui-io26

package/observations/visual/material-3-expressive-system.md

@@ -0,0 +1,52 @@
+---
+id: OBS-00006
+alias: OBS-MATERIAL-3-EXPRESSIVE
+slug: material-3-expressive-system
+title: Material 3 Expressive Combines Emotion With System Constraints
+object_type: observation
+status: draft
+version: 0.1.0
+category: visual
+tags:
+  - android
+  - material
+  - expressive-design
+  - design-system
+created_at: 2026-07-24
+updated_at: 2026-07-24
+last_reviewed_at: 2026-07-24
+owner: ai-design-rules
+maturity: seed
+risk_level: medium
+platform:
+  - android
+product_type:
+  - consumer
+surface:
+  - product-ui
+applies_to:
+  - expressive-system-design
+does_not_apply_to:
+  - decorative-novelty-without-product-purpose
+relationships: []
+---
+
+# Material 3 Expressive Combines Emotion With System Constraints
+
+## Source
+
+Google Material Design and Android developer guidance for Material 3 Expressive.
+
+## Observed Behavior
+
+Material 3 Expressive expands theming, typography, shape, motion, dynamic color, and responsive components while retaining semantic color roles and accessibility guidance. Google presents expression as flexible: it can be quiet or prominent depending on product context.
+
+## Why It May Matter
+
+Modern product UI can carry more personality than neutral component assembly, but the personality needs reusable roles, accessible combinations, and context-sensitive intensity.
+
+## Evidence
+
+- https://developer.android.com/develop/ui/compose/designsystems/material3
+- https://design.google/library/design-notes-material-3-expressive-liam-spradlin
+- https://blog.google/products-and-platforms/platforms/android/material-3-expressive-android-wearos-launch/

package/package.json

@@ -0,0 +1,65 @@
+{
+  "name": "ai-design-context",
+  "version": "0.4.0",
+  "description": "Evidence-driven design knowledge and context retrieval for AI coding agents.",
+  "license": "MIT",
+  "author": "Dev Ik",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/dev-ik/ai-design-rules.git"
+  },
+  "homepage": "https://github.com/dev-ik/ai-design-rules#readme",
+  "bugs": {
+    "url": "https://github.com/dev-ik/ai-design-rules/issues"
+  },
+  "keywords": ["ai", "design", "ux", "ai-agents", "knowledge-graph", "codex", "cursor", "cli"],
+  "engines": {
+    "node": ">=20"
+  },
+  "bin": {
+    "ai-design-context": "tools/cli.mjs"
+  },
+  "files": [
+    "*.md",
+    "assets/logo.svg",
+    "benchmarks/",
+    "checklists/",
+    "docs/*.md",
+    "evidence/",
+    "examples/",
+    "graph/",
+    "observations/",
+    "patterns/",
+    "prompts/",
+    "registry/",
+    "research/",
+    "reviews/",
+    "rules/",
+    "schema/",
+    "skills/",
+    "starter-kit/",
+    "templates/",
+    "tools/cli.mjs",
+    "tools/context.mjs",
+    "tools/init.mjs",
+    "tools/validate-knowledge.mjs",
+    "tools/validate-benchmark-evidence.mjs",
+    "tools/designlint.mjs",
+    "tools/generate-indexes.mjs"
+  ],
+  "scripts": {
+    "prepack": "npm run check && npm test",
+    "validate": "node tools/validate-knowledge.mjs",
+    "lint:design": "node tools/designlint.mjs",
+    "benchmark:validate": "node tools/validate-benchmark-evidence.mjs",
+    "context": "node tools/context.mjs",
+    "generate:indexes": "node tools/generate-indexes.mjs",
+    "check": "npm run validate && npm run lint:design && npm run benchmark:validate",
+    "test:validate": "node --test tools/validate-knowledge.test.mjs",
+    "test": "node --test tools/*.test.mjs"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module"
+}

package/patterns/GENERATED_INDEX.md

@@ -0,0 +1,13 @@
+# Generated Patterns Index
+
+This file is generated from registry metadata. Do not edit manually.
+
+| ID | Alias | Title | Category | Status | Maturity | File Path | Required Rules | Related Research |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| PAT-00001 | PAT-001 | Daily Home Surface | product | draft | seed | patterns/daily-home-surface.md | PRD-001 / RULE-00001 Daily Actions First<br>IA-001 / RULE-00003 One Stable Home Surface<br>UX-002 / RULE-00006 Progressively Disclose Power<br>A11Y-001 / RULE-00009 44x44 Touch Targets<br>VIS-001 / RULE-00008 Semantic Tokens Only<br>VIS-002 / RULE-00014 Keep Expression Subordinate To Content | THINGS-3 / RESEARCH-00002 Things 3<br>TELEGRAM / RESEARCH-00001 Telegram<br>APPLE-REMINDERS / RESEARCH-00003 Apple Reminders<br>LINEAR / RESEARCH-00004 Linear<br>EXPRESSIVE-SYSTEM-UI-2026 / RESEARCH-00009 Expressive System UI In 2026 |
+| PAT-00002 | PAT-002 | Quick Capture | workflow | draft | seed | patterns/quick-capture.md | PRD-002 / RULE-00002 Low-Friction Capture Before Organization<br>UX-001 / RULE-00005 Thumb-Zone Primary Actions<br>UX-002 / RULE-00006 Progressively Disclose Power<br>A11Y-001 / RULE-00009 44x44 Touch Targets<br>A11Y-002 / RULE-00010 Textual Input Error Recovery<br>PERF-001 / RULE-00011 Reserve Layout Space For Asynchronous Content<br>A11Y-003 / RULE-00012 Visible Keyboard Focus | APPLE-REMINDERS / RESEARCH-00003 Apple Reminders<br>THINGS-3 / RESEARCH-00002 Things 3<br>TELEGRAM / RESEARCH-00001 Telegram<br>TEXTUAL-ERROR-RECOVERY / RESEARCH-00006 Textual Error Recovery<br>RESERVED-LOADING-SPACE / RESEARCH-00007 Reserved Loading Space<br>KEYBOARD-FOCUS-AND-MOTION / RESEARCH-00008 Keyboard Focus And Interaction Motion |
+| PAT-00003 | PAT-003 | Mobile Primary Action | mobile | draft | seed | patterns/mobile-primary-action.md | UX-001 / RULE-00005 Thumb-Zone Primary Actions<br>PRD-001 / RULE-00001 Daily Actions First<br>A11Y-001 / RULE-00009 44x44 Touch Targets | THINGS-3 / RESEARCH-00002 Things 3<br>TELEGRAM / RESEARCH-00001 Telegram<br>APPLE-REMINDERS / RESEARCH-00003 Apple Reminders |
+| PAT-00004 | PAT-004 | Progressive Detail | ux | draft | seed | patterns/progressive-detail.md | UX-002 / RULE-00006 Progressively Disclose Power<br>PRD-002 / RULE-00002 Low-Friction Capture Before Organization<br>VIS-001 / RULE-00008 Semantic Tokens Only<br>A11Y-001 / RULE-00009 44x44 Touch Targets | APPLE-REMINDERS / RESEARCH-00003 Apple Reminders<br>THINGS-3 / RESEARCH-00002 Things 3<br>TELEGRAM / RESEARCH-00001 Telegram<br>LINEAR / RESEARCH-00004 Linear |
+| PAT-00005 | PAT-005 | Context-Preserving Preview | ux | draft | seed | patterns/context-preserving-preview.md | UX-003 / RULE-00007 Preserve Context During Inspection<br>IA-002 / RULE-00004 Define The Object Model Before Screens<br>IA-001 / RULE-00003 One Stable Home Surface<br>A11Y-001 / RULE-00009 44x44 Touch Targets<br>A11Y-004 / RULE-00013 Reduce Non-Essential Interaction Motion<br>UX-004 / RULE-00015 Use Motion To Explain State Continuity | TELEGRAM / RESEARCH-00001 Telegram<br>THINGS-3 / RESEARCH-00002 Things 3<br>APPLE-REMINDERS / RESEARCH-00003 Apple Reminders<br>LINEAR / RESEARCH-00004 Linear<br>ARC / RESEARCH-00005 Arc<br>KEYBOARD-FOCUS-AND-MOTION / RESEARCH-00008 Keyboard Focus And Interaction Motion<br>MOTION-AS-STATE-CONTINUITY / RESEARCH-00010 Motion As State Continuity |
+| PAT-00006 | PAT-006 | Object Status List | ia | draft | seed | patterns/object-status-list.md | IA-002 / RULE-00004 Define The Object Model Before Screens<br>UX-003 / RULE-00007 Preserve Context During Inspection<br>VIS-001 / RULE-00008 Semantic Tokens Only<br>A11Y-001 / RULE-00009 44x44 Touch Targets | LINEAR / RESEARCH-00004 Linear<br>TELEGRAM / RESEARCH-00001 Telegram<br>ARC / RESEARCH-00005 Arc<br>THINGS-3 / RESEARCH-00002 Things 3<br>APPLE-REMINDERS / RESEARCH-00003 Apple Reminders |
+| PAT-00007 | PAT-007 | Consequential Action Confirmation | ux | active | validated | patterns/consequential-action-confirmation.md | UX-006 / RULE-00017 Confirm Consequential Actions With Preserved Context<br>UX-003 / RULE-00007 Preserve Context During Inspection<br>A11Y-002 / RULE-00010 Textual Input Error Recovery<br>UX-005 / RULE-00016 Expose Agent Work And Intervention | ARC / RESEARCH-00005 Arc<br>LINEAR / RESEARCH-00004 Linear<br>TELEGRAM / RESEARCH-00001 Telegram<br>TEXTUAL-ERROR-RECOVERY / RESEARCH-00006 Textual Error Recovery<br>CONTEXTUAL-AGENTIC-INTERFACE / RESEARCH-00011 Contextual And Observable Agentic Interfaces<br>HIGH-RISK-OPERATIONAL-FLOWS / RESEARCH-00012 High-Risk Operational Flows |

package/patterns/INDEX.md

@@ -0,0 +1,41 @@
+# Pattern Library
+
+Patterns are compositions of rules. They convert rule-level guidance into reusable product structures that agents can apply in prompts, reference projects, and reviews.
+
+Use this folder after `rules/` and before `prompts/`.
+
+```text
+observations -> research -> knowledge -> rules -> patterns -> prompts -> reference projects -> reviews
+```
+
+## Source Of Truth
+
+All pattern documents must follow `docs/PATTERN_SPEC.md`.
+
+New patterns should start from `templates/PATTERN_TEMPLATE.md`.
+
+Future pattern metadata should follow `docs/KNOWLEDGE_ENGINE.md`.
+
+Manual indexes are transitional. Future indexes should be generated from registry metadata.
+
+## Current Patterns
+
+- `daily-home-surface.md` - screen-level entry point for repeated daily work.
+- `quick-capture.md` - creation flow for recording intent before organization.
+- `progressive-detail.md` - staged access to metadata and advanced controls.
+- `context-preserving-preview.md` - inspection without losing source context.
+- `object-status-list.md` - scanable list of structured objects and states.
+- `mobile-primary-action.md` - touch-first placement and sizing of one primary action.
+
+## Ownership Boundaries
+
+- `daily-home-surface.md` owns the screen purpose and return point.
+- `quick-capture.md` owns the creation flow.
+- `mobile-primary-action.md` owns reachability, target size, and physical placement.
+- `progressive-detail.md` owns staged disclosure of optional detail.
+- `context-preserving-preview.md` owns inspection without navigation loss.
+- `object-status-list.md` owns structured object scanning.
+
+## Contribution Rule
+
+Do not add a pattern unless it references existing rules and related research. A pattern without rules or research is a one-off design idea.

package/patterns/README.md

@@ -0,0 +1,5 @@
+# Patterns
+
+Start with `patterns/INDEX.md`.
+
+Pattern documents follow `docs/PATTERN_SPEC.md` and should be created from `templates/PATTERN_TEMPLATE.md`.