#Remember

Capture learnings and persist them to improve future sessions.

#Workflow

#1. Capture the Learning

Extract structured information:

LEARNING:
- What: [Concise description of the pattern/solution/pitfall]
- Why: [Why this matters or what problem it solves]
- Context: [When this applies - conditions, file types, scenarios]
- Example: [Concrete code/command example if applicable]

#2. Categorize and Route

Determine where the learning belongs:

| Category | Route To | Criteria | |----------|----------|----------| | Project guideline | CLAUDE.md | General coding standards, conventions, style rules | | Existing skill domain | Update skill's SKILL.md | Learning relates to a skill's specific purpose | | New capability | Create new skill | Significant workflow that warrants its own skill | | Architecture pattern | CLAUDE.md or create-domain-model skill | DDD, clean architecture decisions | | Tooling/commands | CLAUDE.md Commands section | New CLI commands, scripts, workflows |

#3. Propose the Update

Present the proposed change to the user:

## Proposed Learning

**Category**: [Category from above]
**Target**: [File path to update]
**Action**: [Add/Update/Create]

### Change Preview
[Show the exact text to add or modify]

### Rationale
[Brief explanation of why this location was chosen]

#4. Apply with Approval

Only apply changes after user confirms. Use:

• Edit tool for updating existing files
• Write tool for creating new skills (via skill-creator)

#Routing Rules

#→ CLAUDE.md

Add to CLAUDE.md when:

• It's a general TypeScript/React pattern for this project
• It's a naming convention or code style rule
• It's a new command that should be documented
• It affects multiple features or is cross-cutting

Format for CLAUDE.md additions:

## [Section Name]

### [Subsection if needed]

- [Concise rule or pattern]
- [Example if helpful]

#→ Existing Skill

Update an existing skill when:

• Learning directly relates to that skill's domain
• It's a refinement of the skill's workflow
• It adds a new variant or edge case handling

Read the skill's SKILL.md first to find the right insertion point.

#→ New Skill

Create a new skill when:

• The learning represents a significant, reusable workflow
• It would be triggered by specific user requests
• It has clear inputs, outputs, and steps

Use /skill-creator to create properly structured skills.

#Examples

#Example 1: Code Pattern

User: "Remember that we should always use ?? instead of || for nullish coalescing"

LEARNING:
- What: Use ?? instead of || for nullish coalescing
- Why: Preserves falsy values like 0 and empty string
- Context: All TypeScript code in this project
- Example: const value = input ?? defaultValue

Route: CLAUDE.md → TypeScript Usage section (already exists, skip if duplicate)

#Example 2: Skill Enhancement

User: "Remember that the create-use-case skill should also generate the test file"

LEARNING:
- What: Generate test file alongside create-use-case
- Why: TDD workflow requires tests before implementation
- Context: When creating new use-cases
- Example: CreateAssetUseCase.ts → CreateAssetUseCase.test.ts

Route: Update create-use-case skill's SKILL.md

#Example 3: New Workflow

User: "Remember how we debug API issues - check network tab, verify auth token, test with curl"

LEARNING:
- What: API debugging workflow
- Why: Systematic approach to diagnose API failures
- Context: When API calls fail or return unexpected results
- Example: 1. Check network tab 2. Verify token 3. curl test

Route: New skill if complex, or CLAUDE.md troubleshooting section if simple

#Anti-patterns

• Don't duplicate: Check if learning already exists before adding
• Don't over-specify: Keep learnings concise and generalizable
• Don't add obvious things: Only capture non-obvious knowledge
• Don't skip approval: Always show proposed changes before applying