Name: capture
Author: zircote-plugins

Prompt file imported from zircote-plugins/aesth (.claude/commands/capture.md). Fill in {{NAMESPACE}}, {{UUID}}, {{SLUG}}, {{DATE}}, {{TITLE}} before use. Copyright stays with the author.

aesth capture

Manually store design patterns, decisions, or tokens to Subcog.

Usage

Interactive mode - prompts for what to capture:

/aesth:capture

Direct capture with type:

/aesth:capture direction
/aesth:capture tokens
/aesth:capture pattern button
/aesth:capture decision

Capture Types

1. Design Direction

Capture the overall design personality and strategy.

Content Structure:

## Design Direction

Personality: [Precision & Density | Warmth & Approachability | Sophistication & Trust | Boldness & Clarity | Utility & Function | Data & Analysis]
Foundation: [Cool Slate | Warm Stone | Pure Neutral | Tinted]
Depth: [Borders-only | Subtle shadows | Layered shadows]

Rationale:
- [Why this personality fits the product]
- [Context about users and their needs]
- [Key considerations that drove the decision]

Established: [ISO 8601 date]

Subcog Parameters:

Namespace: patterns
Domain: project
Tags: ["aesth", "design-direction", "{personality-slug}", "{depth-slug}"]

2. Design Tokens

Capture spacing, colors, typography, and radius scales.

Content Structure:

## Design Tokens

### Spacing Scale
Base: 4px
Scale: 4, 8, 12, 16, 24, 32, 48, 64

### Colors
Foundation: Slate
- slate-50: #f8fafc
- slate-100: #f1f5f9
- slate-600: #475569
- slate-900: #0f172a

Accent: Blue
- blue-500: #3b82f6
- blue-600: #2563eb

Status:
- success: #10b981
- warning: #f59e0b
- error: #ef4444

### Typography
System: Inter (sans-serif)
Code: SF Mono (monospace)

Scale:
- xs: 12px / 1.4
- sm: 14px / 1.5
- base: 16px / 1.5
- lg: 18px / 1.6

### Border Radius
Scale: 4px, 6px, 8px

Updated: [ISO 8601 date]

Subcog Parameters:

Namespace: patterns
Domain: project
Tags: ["aesth", "design-tokens", "spacing", "colors", "typography", "radius"]

3. Component Pattern

Capture specific component measurements and styles.

Content Structure:

## Component: [Name]

### Variant: Primary
- Height: 36px
- Padding: 12px 16px
- Border Radius: 6px
- Background: blue-600
- Color: white
- Font: 14px medium
- Hover: blue-700

### Variant: Secondary
- Height: 36px
- Padding: 12px 16px
- Border: 1px solid slate-300
- Background: white
- Color: slate-700
- Hover: slate-50 bg

Rationale:
- [Why these measurements]
- [Usage guidelines]

Created: [ISO 8601 date]

Subcog Parameters:

Namespace: patterns
Domain: project
Tags: ["aesth", "component-pattern", "{component-name}"]

4. Design Decision

Capture a specific design choice with rationale.

Content Structure:

## Decision: [Topic]

### Choice
[What was decided]

### Context
[Why this decision was needed]

### Alternatives Considered
- [Option 1]: Rejected because...
- [Option 2]: Rejected because...

### Impact
[What this affects going forward]

Date: [ISO 8601 date]

Subcog Parameters:

Namespace: patterns
Domain: project
Tags: ["aesth", "design-decision", "{topic-slug}"]

Output

After successful capture:

Captured to Subcog: Design Direction
URN: subcog://project/patterns/aesth-direction-a1b2c3d4
Tags: aesth, design-direction, precision-density, borders-only

Content preview:
  ## Design Direction
  Personality: Precision & Density
  Foundation: Cool Slate
  ...

Interactive Mode

When invoked without arguments, prompt:

What would you like to capture?

1. Direction - Overall design personality and depth strategy
2. Tokens - Spacing, colors, typography scales
3. Pattern - Component-specific measurements
4. Decision - Design choice with rationale

Select (1-4):

Then gather relevant information through conversation.

Mnemonic Integration: Cross-Session Learning

After capturing design patterns to Subcog, also capture significant decisions to mnemonic for cross-project learning.

When to Capture to Mnemonic

Capture to mnemonic when the design decision represents:

A reusable design pattern applicable across projects
A lesson learned from design iteration
A craft principle discovered through practice

Capture Process

After successful Subcog capture, if the content qualifies:

# Search for related existing memories first
rg -i "design|pattern|aesth" ~/.claude/mnemonic/ --glob "*.memory.md" -l | head -5

# If this is a novel insight, capture it
UUID=$(uuidgen | tr '[:upper:]' '[:lower:]')
DATE=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
NAMESPACE="patterns"
TITLE="Design Pattern: {pattern-name}"
SLUG=$(echo "$TITLE" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | head -c 50)

cat > ~/.claude/mnemonic/default/{{NAMESPACE}}/user/{{UUID}}-{{SLUG}}.memory.md << 'MEMORY'
---
id: {{UUID}}
type: procedural
namespace: patterns/user
created: {{DATE}}
modified: {{DATE}}
title: "{{TITLE}}"
tags:
  - aesth
  - design-pattern
  - {specific-tags}
temporal:
  valid_from: {{DATE}}
  recorded_at: {{DATE}}
provenance:
  source_type: design-capture
  agent: claude-opus-4
  confidence: 0.85
---

# {Pattern Title}

## Level 1: Quick Answer
{One-line summary of the pattern}

## Level 2: Context
{When and why to use this pattern}

## Level 3: Full Detail
{Complete pattern specification with rationale}
MEMORY

Do Not Capture to Mnemonic

Project-specific tokens (colors, spacing) - these stay in Subcog only
Routine component patterns without novel insight
Decisions that only apply to current project context

Install capture and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# aesth capture Manually store design patterns, decisions, or tokens to Subcog. ## Usage Interactive mode - prompts for what to capture: ``` /aesth:capture ``` Direct capture with type: ``` /aesth:capture direction /aesth:capture tokens /aesth:capture pattern button /aesth:capture decision ``` ## Capture Types ### 1. Design Direction Capture the overall design personality and strategy. **Content Structure:** ```markdown ## Design Direction Personality: [Precision & Density | Warmth & Approachability | Sophistication & Trust | Boldness & Clarity | Utility & Function | Data & Analysis] Foundation: [Cool Slate | Warm Stone | Pure Neutral | Tinted] Depth: [Borders-only | Subtle shadows | Layered shadows] Rationale: - [Why this personality fits the product] - [Context about users and their needs] - [Key considerations that drove the decision] Established: [ISO 8601 date] ``` **Subcog Parameters:** - Namespace: `patterns` - Domain: `project` - Tags: `["aesth", "design-direction", "{personality-slug}", "{depth-slug}"]` --- ### 2. Design Tokens Capture spacing, colors, typography, and radius scales. **Content Structure:** ```markdown ## Design Tokens ### Spacing Scale Base: 4px Scale: 4, 8, 12, 16, 24, 32, 48, 64 ### Colors Foundation: Slate - slate-50: #f8fafc - slate-100: #f1f5f9 - slate-600: #475569 - slate-900: #0f172a Accent: Blue - blue-500: #3b82f6 - blue-600: #2563eb Status: - success: #10b981 - warning: #f59e0b - error: #ef4444 ### Typography System: Inter (sans-serif) Code: SF Mono (monospace) Scale: - xs: 12px / 1.4 - sm: 14px / 1.5 - base: 16px / 1.5 - lg: 18px / 1.6 ### Border Radius Scale: 4px, 6px, 8px Updated: [ISO 8601 date] ``` **Subcog Parameters:** - Namespace: `patterns` - Domain: `project` - Tags: `["aesth", "design-tokens", "spacing", "colors", "typography", "radius"]` --- ### 3. Component Pattern Capture specific component measurements and styles. **Content Structure:** ```markdown ## Component: [Name] ### Variant: Primary - Height: 36px - Padding: 12px 16px - Border Radius: 6px - Background: blue-600 - Color: white - Font: 14px medium - Hover: blue-700 ### Variant: Secondary - Height: 36px - Padding: 12px 16px - Border: 1px solid slate-300 - Background: white - Color: slate-700 - Hover: slate-50 bg Rationale: - [Why these measurements] - [Usage guidelines] Created: [ISO 8601 date] ``` **Subcog Parameters:** - Namespace: `patterns` - Domain: `project` - Tags: `["aesth", "component-pattern", "{component-name}"]` --- ### 4. Design Decision Capture a specific design choice with rationale. **Content Structure:** ```markdown ## Decision: [Topic] ### Choice [What was decided] ### Context [Why this decision was needed] ### Alternatives Considered - [Option 1]: Rejected because... - [Option 2]: Rejected because... ### Impact [What this affects going forward] Date: [ISO 8601 date] ``` **Subcog Parameters:** - Namespace: `patterns` - Domain: `project` - Tags: `["aesth", "design-decision", "{topic-slug}"]` --- ## Output After successful capture: ```text Captured to Subcog: Design Direction URN: subcog://project/patterns/aesth-direction-a1b2c3d4 Tags: aesth, design-direction, precision-density, borders-only Content preview: ## Design Direction Personality: Precision & Density Foundation: Cool Slate ... ``` ## Interactive Mode When invoked without arguments, prompt: ```text What would you like to capture? 1. Direction - Overall design personality and depth strategy 2. Tokens - Spacing, colors, typography scales 3. Pattern - Component-specific measurements 4. Decision - Design choice with rationale Select (1-4): ``` Then gather relevant information through conversation. --- ## Mnemonic Integration: Cross-Session Learning After capturing design patterns to Subcog, also capture significant decisions to mnemonic for cross-project learning. ### When to Capture to Mnemonic Capture to mnemonic when the design decision represents: - A reusable design pattern applicable across projects - A lesson learned from design iteration - A craft principle discovered through practice ### Capture Process After successful Subcog capture, if the content qualifies: ```bash # Search for related existing memories first rg -i "design|pattern|aesth" ~/.claude/mnemonic/ --glob "*.memory.md" -l | head -5 # If this is a novel insight, capture it UUID=$(uuidgen | tr '[:upper:]' '[:lower:]') DATE=$(date -u +"%Y-%m-%dT%H:%M:%SZ") NAMESPACE="patterns" TITLE="Design Pattern: {pattern-name}" SLUG=$(echo "$TITLE" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | head -c 50) cat > ~/.claude/mnemonic/default/{{NAMESPACE}}/user/{{UUID}}-{{SLUG}}.memory.md << 'MEMORY' --- id: {{UUID}} type: procedural namespace: patterns/user created: {{DATE}} modified: {{DATE}} title: "{{TITLE}}" tags: - aesth - design-pattern - {specific-tags} temporal: valid_from: {{DATE}} recorded_at: {{DATE}} provenance: source_type: design-capture agent: claude-opus-4 confidence: 0.85 --- # {Pattern Title} ## Level 1: Quick Answer {One-line summary of the pattern} ## Level 2: Context {When and why to use this pattern} ## Level 3: Full Detail {Complete pattern specification with rationale} MEMORY ``` ### Do Not Capture to Mnemonic - Project-specific tokens (colors, spacing) - these stay in Subcog only - Routine component patterns without novel insight - Decisions that only apply to current project context

{ "prompt": "# aesth capture\n\nManually store design patterns, decisions, or tokens to Subcog.\n\n## Usage\n\nInteractive mode - prompts for what to capture:\n```\n/aesth:capture\n```\n\nDirect capture with type:\n```\n/aesth:capture direction\n/aesth:capture tokens\n/aesth:capture pattern button\n/aesth:capture decision\n```\n\n## Capture Types\n\n### 1. Design Direction\n\nCapture the overall design personality and strategy.\n\n**Content Structure:**\n```markdown\n## Design Direction\n\nPersonality: [Precision & Density | Warmth & Approachability | Sophistication & Trust | Boldness & Clarity | Utility & Function | Data & Analysis]\nFoundation: [Cool Slate | Warm Stone | Pure Neutral | Tinted]\nDepth: [Borders-only | Subtle shadows | Layered shadows]\n\nRationale:\n- [Why this personality fits the product]\n- [Context about users and their needs]\n- [Key considerations that drove the decision]\n\nEstablished: [ISO 8601 date]\n```\n\n**Subcog Parameters:**\n- Namespace: `patterns`\n- Domain: `project`\n- Tags: `[\"aesth\", \"design-direction\", \"{personality-slug}\", \"{depth-slug}\"]`\n\n---\n\n### 2. Design Tokens\n\nCapture spacing, colors, typography, and radius scales.\n\n**Content Structure:**\n```markdown\n## Design Tokens\n\n### Spacing Scale\nBase: 4px\nScale: 4, 8, 12, 16, 24, 32, 48, 64\n\n### Colors\nFoundation: Slate\n- slate-50: #f8fafc\n- slate-100: #f1f5f9\n- slate-600: #475569\n- slate-900: #0f172a\n\nAccent: Blue\n- blue-500: #3b82f6\n- blue-600: #2563eb\n\nStatus:\n- success: #10b981\n- warning: #f59e0b\n- error: #ef4444\n\n### Typography\nSystem: Inter (sans-serif)\nCode: SF Mono (monospace)\n\nScale:\n- xs: 12px / 1.4\n- sm: 14px / 1.5\n- base: 16px / 1.5\n- lg: 18px / 1.6\n\n### Border Radius\nScale: 4px, 6px, 8px\n\nUpdated: [ISO 8601 date]\n```\n\n**Subcog Parameters:**\n- Namespace: `patterns`\n- Domain: `project`\n- Tags: `[\"aesth\", \"design-tokens\", \"spacing\", \"colors\", \"typography\", \"radius\"]`\n\n---\n\n### 3. Component Pattern\n\nCapture specific component measurements and styles.\n\n**Content Structure:**\n```markdown\n## Component: [Name]\n\n### Variant: Primary\n- Height: 36px\n- Padding: 12px 16px\n- Border Radius: 6px\n- Background: blue-600\n- Color: white\n- Font: 14px medium\n- Hover: blue-700\n\n### Variant: Secondary\n- Height: 36px\n- Padding: 12px 16px\n- Border: 1px solid slate-300\n- Background: white\n- Color: slate-700\n- Hover: slate-50 bg\n\nRationale:\n- [Why these measurements]\n- [Usage guidelines]\n\nCreated: [ISO 8601 date]\n```\n\n**Subcog Parameters:**\n- Namespace: `patterns`\n- Domain: `project`\n- Tags: `[\"aesth\", \"component-pattern\", \"{component-name}\"]`\n\n---\n\n### 4. Design Decision\n\nCapture a specific design choice with rationale.\n\n**Content Structure:**\n```markdown\n## Decision: [Topic]\n\n### Choice\n[What was decided]\n\n### Context\n[Why this decision was needed]\n\n### Alternatives Considered\n- [Option 1]: Rejected because...\n- [Option 2]: Rejected because...\n\n### Impact\n[What this affects going forward]\n\nDate: [ISO 8601 date]\n```\n\n**Subcog Parameters:**\n- Namespace: `patterns`\n- Domain: `project`\n- Tags: `[\"aesth\", \"design-decision\", \"{topic-slug}\"]`\n\n---\n\n## Output\n\nAfter successful capture:\n```text\nCaptured to Subcog: Design Direction\nURN: subcog://project/patterns/aesth-direction-a1b2c3d4\nTags: aesth, design-direction, precision-density, borders-only\n\nContent preview:\n ## Design Direction\n Personality: Precision & Density\n Foundation: Cool Slate\n ...\n```\n\n## Interactive Mode\n\nWhen invoked without arguments, prompt:\n\n```text\nWhat would you like to capture?\n\n1. Direction - Overall design personality and depth strategy\n2. Tokens - Spacing, colors, typography scales\n3. Pattern - Component-specific measurements\n4. Decision - Design choice with rationale\n\nSelect (1-4):\n```\n\nThen gather relevant information through conversation.\n\n---\n\n## Mnemonic Integration: Cross-Session Learning\n\nAfter capturing design patterns to Subcog, also capture significant decisions to mnemonic for cross-project learning.\n\n### When to Capture to Mnemonic\n\nCapture to mnemonic when the design decision represents:\n- A reusable design pattern applicable across projects\n- A lesson learned from design iteration\n- A craft principle discovered through practice\n\n### Capture Process\n\nAfter successful Subcog capture, if the content qualifies:\n\n```bash\n# Search for related existing memories first\nrg -i \"design|pattern|aesth\" ~/.claude/mnemonic/ --glob \"*.memory.md\" -l | head -5\n\n# If this is a novel insight, capture it\nUUID=$(uuidgen | tr '[:upper:]' '[:lower:]')\nDATE=$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")\nNAMESPACE=\"patterns\"\nTITLE=\"Design Pattern: {pattern-name}\"\nSLUG=$(echo \"$TITLE\" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | head -c 50)\n\ncat > ~/.claude/mnemonic/default/{{NAMESPACE}}/user/{{UUID}}-{{SLUG}}.memory.md << 'MEMORY'\n---\nid: {{UUID}}\ntype: procedural\nnamespace: patterns/user\ncreated: {{DATE}}\nmodified: {{DATE}}\ntitle: \"{{TITLE}}\"\ntags:\n - aesth\n - design-pattern\n - {specific-tags}\ntemporal:\n valid_from: {{DATE}}\n recorded_at: {{DATE}}\nprovenance:\n source_type: design-capture\n agent: claude-opus-4\n confidence: 0.85\n---\n\n# {Pattern Title}\n\n## Level 1: Quick Answer\n{One-line summary of the pattern}\n\n## Level 2: Context\n{When and why to use this pattern}\n\n## Level 3: Full Detail\n{Complete pattern specification with rationale}\nMEMORY\n```\n\n### Do Not Capture to Mnemonic\n\n- Project-specific tokens (colors, spacing) - these stay in Subcog only\n- Routine component patterns without novel insight\n- Decisions that only apply to current project context", "variables": [ "NAMESPACE", "UUID", "SLUG", "DATE", "TITLE" ], "notes": "Capture design patterns, tokens, or decisions to Subcog memory. Tools: mcp__plugin_subcog_subcog__subcog_capture, mcp__plugin_subcog_subcog__subcog_recall, Bash, Glob, Grep, Read, Write.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/zircote-plugins/aesth", "path": ".claude/commands/capture.md", "ref": "476b3c3720b0a54eb0f8fe05a1a48e41bed022cd", "url": "https://github.com/zircote-plugins/aesth/blob/476b3c3720b0a54eb0f8fe05a1a48e41bed022cd/.claude/commands/capture.md", "key": "zircote-plugins/aesth/.claude/commands/capture.md" } } }

capture

About

aesth capture

Usage

Capture Types

1. Design Direction

2. Design Tokens

3. Component Pattern

4. Design Decision

Output

Interactive Mode

Mnemonic Integration: Cross-Session Learning

When to Capture to Mnemonic

Capture Process

Do Not Capture to Mnemonic

Install capture and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews