codebase
Record code patterns and architectural decisions, then retrieve relevant context to maintain consistent design and avoid repeated decisions.
Instructions
Unified codebase tool. Actions: 'remember_pattern' (store code pattern), 'remember_decision' (store architectural decision), 'get_context' (retrieve patterns and decisions).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name/title for the pattern (required for remember_pattern) | |
| files | No | Files where this pattern is used or affected by this decision | |
| limit | No | Maximum items per category (default: 10, for get_context) | |
| action | Yes | Action to perform: 'remember_pattern' stores a code pattern, 'remember_decision' stores an architectural decision, 'get_context' retrieves patterns and decisions for a codebase | |
| codebase | No | Codebase/project identifier (e.g., 'vestige-tauri') | |
| decision | No | The architectural or design decision made (required for remember_decision) | |
| rationale | No | Why this decision was made (required for remember_decision) | |
| description | No | Detailed description of the pattern (required for remember_pattern) | |
| alternatives | No | Alternatives that were considered (optional for remember_decision) |