Five-layer memory architecture: where each fact lives, how layers interact, when to promote learnings
/plugin marketplace add sefaertunc/Worclaude
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/worclaude-mpt6qis2?utm_source=badge&utm_medium=readme&utm_campaign=badge)
Resources to assist in writing various internal communications, adhering to company-preferred formats. Claude should utilize this skill for status reports, leadership updates, newsletters, FAQs, and other internal documents.
Monitors a pull request or review cycle until it is ready to merge. This skill is used to track PR comments, reviews, and CI status until all actionable issues are resolved.
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
Token-optimized structural code search using tree-sitter AST parsing. Use this instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.
Category alert
One short email with only the new DevOps e Infra skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Worclaude projects use five distinct memory layers. Each has a different scope, owner, and lifecycle. Routing a fact to the correct layer is a load-bearing decision — the wrong layer means the fact is invisible when needed, or noisy when not.
| Layer | Scope | Owner | Lifecycle |
|---|---|---|---|
| `CL |
[Description truncada. Veja o README completo no GitHub.]
Sign in to comment. Sign in
