// Capture important architectural decisions, bug patterns, feature designs, or other critical findings into the project knowledge base. Use proactively when significant technical decisions are made, non-obvious bugs are resolved, new subsystems are designed, or important product features are discussed.
Fix a production exception from Rollbar in an interactive Claude Code session. Fetches the occurrence data, analyzes the error, and either implements a fix or adds the error to the ignore list. Use when given a Rollbar occurrence ID.
Guidelines for writing React Native code in Liftosaur. Use when migrating web components to RN primitives, fixing RN performance issues, or building new RN screens.
Write, debug, and integrate Lezer grammars for the Liftosaur project. Use when creating or modifying .grammar files, evaluators, syntax highlighting, or CodeMirror integration.
Write idiomatic Liftoscript code for weightlifting programs. Use when creating or editing program files in programs/builtin/.
Writing style guide for prose content - program descriptions, technique pages, blog posts, and any user-facing text. Use when writing or editing descriptive content.
Add a new server-rendered page to the Liftosaur website. Use when creating new public-facing pages with routing, SSR, and client hydration.
| name | kb |
| description | Capture important architectural decisions, bug patterns, feature designs, or other critical findings into the project knowledge base. Use proactively when significant technical decisions are made, non-obvious bugs are resolved, new subsystems are designed, or important product features are discussed. |
| disable-model-invocation | false |
| argument-hint | ["what to capture"] |
Capture this into the knowledge base: $ARGUMENTS
All files live in lambda/scripts/memory/. The index is at lambda/scripts/memory/INDEX.md.
Read lambda/scripts/memory/INDEX.md to understand what's already captured and avoid duplicates.
| Category | Directory | When to use |
|---|---|---|
| Architecture | architecture/ | System design, infrastructure, sync protocols, data formats, tech stack choices |
| Decisions | decisions/ | "We chose X over Y because Z" — explicit tradeoff analysis |
| Features | features/ | Product feature descriptions, UX designs, user-facing behavior |
| Bugs | bugs/ | Non-obvious bug root causes, debugging patterns worth remembering |
| Future Plans | futureplans/ | Planned work not yet started — roadmap items, RFCs for future features |
| SEO | seo/ | SEO research, keyword analysis, backlink data, Core Web Vitals |
If none fit, create a new category directory and add a section to INDEX.md.
Filename: lowercase-kebab-case, descriptive. Example: watch-echo-loop-bug.md
Entry format:
---
date: YYYY-MM-DD
tags: [relevant, tags]
---
# Title
Concise description of the finding/decision/pattern.
Keep it 5-20 lines. Link to relevant source files where useful.
Focus on the WHY and the non-obvious parts — assume the reader is a developer familiar with the codebase.
Add a one-liner entry under the appropriate category heading:
- [filename.md](category/filename.md) — concise one-liner (max 80 chars)
Keep entries sorted by relevance within each category (most important first), not by date.
Capture knowledge when ANY of these happen during a conversation:
Do NOT capture: