giuseppe-trisciuoglio/developer-kit / plugins/developer-kit-core/skills/memory-md-management
memory-md-management
VerifiedProvides comprehensive memory file management capabilities including auditing, quality assessment, and targeted improvements for files such as CLAUDE.md. Use when user asks to check, audit, update, improve, fix, maintain, or validate project memory files. Also triggers for "project memory optimization", "CLAUDE.md quality check", "documentation review", or when a project memory file needs to be created from scratch. This skill scans memory files, evaluates quality against standardized criteria, outputs detailed quality reports with scores and recommendations, then makes targeted updates with user approval.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.3 KB |
| references/quality-criteria.md | markdown | 2.6 KB |
| references/templates.md | markdown | 3.1 KB |
| references/update-guidelines.md | markdown | 3.2 KB |
references/templates.md
View on GitHub# Memory File Templates
## Key Principles
- **Concise**: Dense, human-readable content; one line per concept when possible
- **Actionable**: Commands should be copy-paste ready
- **Project-specific**: Document patterns unique to this project, not generic advice
- **Current**: All info should reflect actual codebase state
---
## Recommended Sections
Use only the sections relevant to the project. Not all sections are needed.
### Commands
Document the essential commands for working with the project.
~~~markdown
## Commands
| Command | Description |
|---------|-------------|
| `<cmd>` | Install dependencies |
| `<cmd>` | Start development server |
| `<cmd>` | Production build |
| `<cmd>` | Run tests |
| `<cmd>` | Lint/format code |
~~~
### Architecture
Describe the project structure so Claude understands where things live.
~~~markdown
## Architecture
~~~
<tree-structure>
```
# <directory-name>
# <directory-name>
```
```
### Key Files
List important files that Claude should know about.
```markdown
## Key Files
- `<path>` - <purpose>
- `<path>` - <purpose>
```
### Code Style
Document project-specific coding conventions.
```markdown
## Code Style
- <convention 1>
- <convention 2>
```
### Environment
Document required environment variables and setup.
```markdown
## Environment
Required:
- `<VAR>` - <purpose>
Setup:
- <setup steps>
```
### Testing
Document testing approach and commands.
```markdown
## Testing
- <approach 1>
- <approach 2>
```
### Gotchas
Document non-obvious patterns, quirks, and warnings.
```markdown
## Gotchas
- <gotcha 1>
- <gotcha 2>
```
### Workflow
Document development workflow patterns.
```markdown
## Workflow
- <workflow pattern>
```
---
## Template: Project Root (Minimal)
```markdown
# <Project Name>
## Commands
| Command | Description |
|---------|-------------|
| `<cmd>` | <description> |
## Architecture
```
<tree>
```
## Gotchas
- <gotcha>
```
---
## Template: Project Root (Comprehensive)
```markdown
# <Project Name>
## Commands
| Command | Description |
|---------|-------------|
| `<cmd>` | <description> |
## Architecture
```
<tree>
```
## Key Files
- `<path>` - <purpose>
## Code Style
- <convention>
## Environment
- `<VAR>` - <purpose>
## Testing
- <approach>
## Gotchas
- <gotcha>
```
---
## Template: Package/Module
For packages within a monorepo or distinct modules.
```markdown
# <Package/Module Name>
## Usage
```<language>
<example>
```
## Key Exports
- `<export>` - <purpose>
## Dependencies
- <dependency>
## Notes
- <note>
```
---
## Template: Monorepo Root
```markdown
# <Monorepo Name>
## Packages
| Package | Description | Path |
|---------|-------------|------|
| `<name>` | <description> | `<path>` |
## Commands
| Command | Description |
|---------|-------------|
| `<cmd>` | <description> |
## Cross-Package Patterns
- <pattern>
```
---
## Update Principles
When updating any CLAUDE.md:
1. **Be specific**: Use actual file paths, real commands from this project
2. **Be current**: Verify info against the actual codebase
3. **Be brief**: One line per concept when possible
4. **Be useful**: Would this help a new Claude session understand the project?
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |