by markmdev
Zero-config Claude Code setup with enforced task scaffolding, structured memory, persistent context after compaction, plug-in code standards, optional TDD mode, and zero behavior changes for developers.
# Add to your Claude Code skills
git clone https://github.com/markmdev/meridianBehavioral guardrails for Claude Code — enforced workflows, persistent context, and quality gates for complex tasks.
Current version: 0.0.81 (2026-01-30) | Changelog
If Meridian helps your work, please star the repo and share it. Follow updates: X (@markmdev) • LinkedIn
Claude Code is powerful, but on complex tasks it struggles with:
| Problem | What happens |
|---------|--------------|
| Context loss | After compaction, Claude forgets decisions, requirements, and what it was working on |
| No built-in memory | Claude can't remember lessons learned — it repeats the same mistakes because it doesn't know it already made them |
| Forgets prompt details | With large context, Claude starts ignoring parts of your CLAUDE.md instructions |
| Shallow planning | Plans lack depth, miss integration steps, and break during implementation |
| No task continuity | When you return to a task next session, Claude doesn't know what was done, decided, or tried |
You can write instructions in CLAUDE.md, but with large context Claude starts forgetting details from the prompt.
Meridian uses Claude Code's hooks system to enforce behaviors automatically:
| Capability | How it works | |------------|--------------| | Context survives compaction | Hooks re-inject memory, task state, guidelines, and your docs after every compaction | | | Lessons learned, architectural decisions, and mistakes are saved to — Claude reads them every session | | | Rolling tracks decisions, discoveries, and context across sessions — Claude picks up where it left off | | | Monitors token usage and prompts Claude to save context before compaction happens | | | Planning skill guides Claude through thorough discovery, design, and integration planning | | | Plan-reviewer and code-reviewer agents validate work before proceeding | | | Context7 and DeepWiki provide up-to-date library docs and repository knowledge for planning and review | | | Add your architecture docs, API references, etc. to — they're injected every session |
memory.jsonlsession-context.mdrequired-context-files.yamlYour behavior doesn't change. You talk to Claude the same way. Meridian works behind the scenes.
Meridian is designed for large, complex, long-running tasks where:
For simple tasks (quick edits, one-off questions), Meridian won't help much — but it won't hurt either. It stays out of the way.