By doancan
Memory And Guidance System — Project documentation memory, session persistence, and development guidance for Claude Code
Validates code-documentation consistency. Use this agent when a feature is completed, before creating a PR, or when /mags-docs validate is called. Checks that code changes are reflected in documentation and identifies stale or missing doc sections. Examples: <example>Context: User completed a feature. user: "I finished the payment module, check if docs are up to date" assistant: "I'll validate documentation consistency with the codebase."</example> <example>Context: Before PR creation. user: "Validate docs before I create the PR" assistant: "Let me run the doc-sync-validator to check for stale or missing documentation."</example> <example>Context: Routine check. user: "Are my docs in sync with the code?" assistant: "I'll check documentation-code consistency."</example>
Analyzes a project and recommends optimal Claude Code setup including plugins, skills, hooks, and CLAUDE.md configuration. Use when setting up a new project with Claude Code, when running /mags-setup, or when the user asks about optimizing their development workflow. Examples: <example>Context: User wants to set up Claude Code for their project. user: "How should I configure Claude Code for this project?" assistant: "Let me analyze your project and recommend the optimal setup."</example> <example>Context: User is starting a new project. user: "Set up MAGS for this repo" assistant: "I'll use the setup-recommender agent to analyze your project."</example> <example>Context: User wants to optimize workflow. user: "What plugins and hooks should I use?" assistant: "Let me recommend the best configuration for your stack."</example>
Provides API design and lifecycle management guidance including versioning, deprecation, rate limiting, and documentation standards. Triggers on api design, rest api, graphql, api versioning, deprecation, breaking changes, rate limiting, api lifecycle, api documentation, openapi.
Provides guidance on creating and maintaining CLAUDE.md project configuration files for Claude Code. Use when setting up a new project, configuring Claude Code behavior, or updating project rules and conventions. Triggers on creating CLAUDE.md, project setup, Claude Code configuration, project rules, project conventions, module map, tech stack definition.
Provides document management guidance for creating, updating, and maintaining project documentation. Use when writing or editing docs, structuring markdown files, managing document lifecycle, or applying formatting standards. Triggers on creating docs, updating docs, writing documentation, markdown formatting, frontmatter, document status, cross-references, naming conventions.
Provides infrastructure and DevOps guidance including deployment, CI/CD, monitoring, containerization, and cloud architecture. Triggers on infrastructure, devops, deployment, docker, kubernetes, ci/cd, monitoring, observability, cloud, scaling, load balancing.
Generate changelog from git history and project docs
Admin access level
Server config contains admin-level keywords
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin that keeps your project context alive across sessions.
MAGS indexes your documentation and remembers decisions — so every new conversation picks up exactly where the last one left off.
Claude Code sessions are stateless. Every time you start a new conversation, you lose context: what was decided, what was built, what's next. MAGS solves this by giving Claude a persistent memory layer tied to your project.
/mags-legacy command for existing codebases: generates architecture docs, migration plans, and tech debt trackingpack.yaml manifests# Add the marketplace source
claude plugin marketplace add https://github.com/doancan/mags
# Install the plugin
claude plugin install mags@mags-marketplace
Restart Claude Code, then inside any project:
/mags-init
That's it. MAGS will scan your docs/ directory (or help you create one from templates) and start tracking your project.
| Command | What it does |
|---|---|
/mags-init | Set up MAGS for your project — scan docs or scaffold from templates |
/mags-status | Dashboard — doc health score, next steps |
/mags-docs | List all project documents |
/mags-docs-create <template> | Create a new document from template |
/mags-docs-validate | Run document validation checks |
/mags-docs-search <query> | Search across all documents |
/mags-changelog | Generate a changelog from git history |
/mags-setup | Analyze your project and recommend Claude Code configuration |
/mags-legacy | Initialize MAGS for a legacy/brownfield project with stack detection and tech debt tracking |
/mags-help | Quick reference of all commands, skills, agents, and hooks |
These run silently in the background — no action needed from you:
| Event | What happens |
|---|---|
| SessionStart | Loads project summary and conventions |
Claude automatically uses these when relevant:
| Skill | Activates when |
|---|---|
doc-management | Creating or editing project documentation |
memory-guidance | Storing decisions, conventions, or session context |
claude-md-management | Working with CLAUDE.md project configuration |
testing-strategy | Planning tests, test pyramid, coverage targets, mocking strategies |
security-review | Security audits, OWASP Top 10, threat modeling, secure coding |
infrastructure | DevOps, CI/CD pipelines, containerization, monitoring, deployment |
api-lifecycle | API design, versioning, deprecation, rate limiting, OpenAPI/GraphQL |
| Agent | Purpose |
|---|---|
doc-sync-validator | Checks if documentation matches the actual code |
setup-recommender | Recommends plugins, skills, and hooks for your stack |
Session starts
→ Hook loads: project summary + conventions
You work normally
→ Claude uses MAGS tools as needed (memory, docs)
→ Decisions and context are stored via mags_remember
Next session starts
→ Project summary is restored automatically
→ Stored memories carry over across sessions
Store decisions, conventions, and notes as key-value pairs. MAGS searches them using TF-IDF scoring (offline) or OpenAI embeddings (optional).
"We're using JWT with refresh tokens for auth, remember this"
→ mags_remember is called automatically
Categories: decisions, conventions, notes, context, bugs
MAGS indexes your docs/ directory — parses YAML frontmatter, extracts section headings, and builds a fuzzy search index. Supports .md, .mdx, .rst, and .adoc.
npx claudepluginhub doancan/mags --plugin magsAutomatically maintains CLAUDE.md files as codebases evolve using hooks, agents, and skills
Lightweight documentation memory for AI coding agents: scaffold a docs tree, validate it, and auto-load recent context each session.
CLAUDE.md lifecycle toolkit: initialise, enhance, sync, and modularise CLAUDE.md files with a 150-line cap, automatic chaining, and Karpathy behavioural guardrails.
Commands for generating documentation and managing changelogs
Claude Copilot — a framework of specialized agents, skills, commands, and hooks that give Claude persistent memory, expert methodology, and task tracking. Agents cover architecture (ta), engineering (me), QA (qa), service design (sd), DevOps (do), documentation (doc), and knowledge onboarding (kc).
AI Development Environment - Multi-agent orchestration for Claude Code