Record structured decisions once, search them from all your AI coding tools — a shared structured semantic memory store across Claude Code, Cursor, Windsurf, Antigravity, and every MCP client.
**Call this IMMEDIATELY** when user says phrases like: "Let's use...", "From now on...", "Always do...", "Never do...", "I prefer...", "The standard is...", "We should always...", or confirms ANY technical approach. Also call when: (1) A design pattern is established, (2) An architectural choice is made, (3) Coding standards are discussed, (4) UI/UX conventions are agreed, (5) Technology stack decisions happen. Capture decisions DURING the conversation, not after. Focus on WHY, not just WHAT.
Permanently delete a decision and its embedding. Supports global: prefix. Consider deprecating instead if the user might want it back.
Get full details of a specific decision by ID. Use this after search_decisions returns relevant results to get complete context including rationale and constraints.
View the activity log of recent decision changes — adds, edits, deletes, and syncs.
Get a project overview: total decisions, active count, and last activity.
List all recorded decisions for the project. Use this when you need a complete overview of project conventions, or when starting work on a new feature area to understand existing patterns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 17 | 2026-07-28+ | v2 |
List all projects with decisions, plus global decision count. Use this first in monorepos to find the right project name.
**MANDATORY: Call this FIRST before ANY code changes.** When user asks you to: add a feature, modify code, fix a bug, implement something, refactor, style UI, or make ANY technical choice — you MUST call this tool FIRST to check for existing conventions. Skipping this causes inconsistency and wasted rework. Query with what you're about to work on: "button styling", "error handling", "API design", "authentication", "database schema", "component structure". If no decisions exist, proceed freely; if decisions exist, FOLLOW them.
Update an existing decision when requirements change or the approach evolves. Use this instead of creating duplicate decisions.