memory_bank
π―Skillfrom cityfish91159/maihouses
Maintains a persistent memory file to track project context, architecture, issues, and operational rules across AI agent sessions.
Installation
npx skills add https://github.com/cityfish91159/maihouses --skill memory_bankSkill Details
Establishes a persistent "Long-Term Memory" file to prevent context amnesia across sessions.
Overview
# Memory Bank Protocol
1. The Core Rule
"Read First, Write Last."
- Start of Task: You MUST read
MEMORY.md(at project root) to understand the project's current state, constraints, and architecture. - End of Task: You MUST update
MEMORY.mdif you have:
- Added a new feature.
- Changed the architecture.
- Discovered a new bug or constraint.
2. File Structure Constraint
Your MEMORY.md updates must roughly follow this template to maintain readability:
```markdown
1. Active Context
- Goal: [Current Objective]
- Status: [Progress]
2. Architecture & Tech Stack
- [Key tech decisions]
3. Known Issues & Technical Debt
- [List of things that are broken or hacky]
4. Operational Rules
- [Do's and Don'ts specific to this project]
```
3. Maintenance Triggers
- New Pattern: If you implement a new pattern (e.g., "All lists must be virtualized"), add it to
Operational Rules. - Bug Hunt: If you spend >10 mins debugging something, write the "Cause & Fix" in
Known Issuesso the next agent doesn't suffer. - Schema Change: If
api/changes, updateArchitecture.
4. Verification Checklist
- [ ] Did I read
MEMORY.mdat the start? - [ ] Did I verify if my plan conflicts with "Known Issues"?
- [ ] Did I update "Active Context" to reflect my completed work?
More from this repository10
Enforces comprehensive testing by mandating tests for every code change, bug fix, and new feature implementation.
read-before-edit skill from cityfish91159/maihouses
Enforces architectural best practices by guiding developers to think systematically about data flow, component boundaries, and scalability before writing code.
Enforces strict Row Level Security (RLS) policies in Supabase, mandating default-deny access and comprehensive security checks.
Validates and sanitizes backend API inputs, preventing injection attacks and ensuring robust data integrity across server-side endpoints
Validates TypeScript/React code quality for maihouses projects, ensuring adherence to CLAUDE.md standards through comprehensive automated checks.
Checks and fixes TypeScript type errors by identifying, analyzing, and resolving type mismatches across project files.
Enforces strict React performance guidelines by policing re-renders, optimizing bundle size, and preventing performance bottlenecks.
Logs and tracks critical actions with comprehensive user, action, and resource metadata for enhanced traceability and security.
pre-commit-validator skill from cityfish91159/maihouses