proactive-memory

Proactive Memory — Remember as You Work

Keywords

remember this, save convention, note this pattern, don't forget, save this decision, remember for next time, keep this in mind, convention, architecture decision, gotcha, correction

Overview

During normal coding work, capture valuable project knowledge into Tages so it persists across sessions. This skill guides when and what to remember — the goal is that the next session starts with full context instead of amnesia.

Use this skill when: You discover something worth remembering during coding, or the user explicitly asks you to remember something.

---

What to Remember

Conventions

Naming patterns, code style, file organization, import conventions, test patterns.

Examples:

• "Components in this project use PascalCase with a .component.tsx suffix"
• "All API routes validate input with Zod schemas before processing"
• "Tests use factories from tests/factories/ instead of inline fixtures"

Architecture Decisions

Why something is built a certain way, trade-offs that were made, structural choices.

Examples:

• "Auth uses Supabase PKCE flow with a /auth/cli-token workaround for CLI OAuth"
• "SQLite is the primary store for sub-10ms reads; Supabase syncs in background"
• "Dashboard deploys manually via vercel --prod, not auto-deploy from GitHub"

Gotchas

Non-obvious behavior, common mistakes, workarounds, things that look wrong but are intentional.

Examples:

• "Supabase .from().insert() returns PromiseLike not Promise — wrap with Promise.resolve() for .catch()"
• "The ESM/CJS boundary between CLI and server requires createRequire + directory walk"
• "Migration params need explicit ::uuid cast for uuid columns"

Corrections

When the user corrects your approach — remember it so you don't repeat the mistake.

Examples:

• User: "No, we don't mock the database in these tests" → Remember: integration tests use real DB
• User: "Use the existing Button component, don't create a new one" → Remember: reuse shared components from src/components/ui/