smithery/doancan

mags-init

Initialize MAGS for the current project

Installation

$ npx skills add smithery/doancan --skill mags-init

Also in this package

Other skills from smithery/doancan.

npx skills add smithery/doancan

Browse all from smithery/doancan

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
Allowed toolsmcp__mags_mags__mags_list_docs, mcp__mags_mags__mags_create_doc, mcp__mags_mags__mags_update_doc, mcp__mags_mags__mags_search_docs, mcp__mags_mags__mags_detect_stack, mcp__mags_mags__mags_generate_claude_md, mcp__mags_mags__mags_project_summary, mcp__mags_mags__mags_remember, Bash, Read, Glob, Write
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,470 B
  • docs SUMMARY.md 56 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

MAGS Init

Initialize the Memory And Guidance System for this project.

Steps

1. Check existing state

Check if a docs/ directory already exists in the project root. Also check for .mags/ directory and any existing CLAUDE.md.

Use Glob to scan for docs/**/*.md and check for .mags/config.yaml.

2A. If docs/ exists — Index existing documentation

Report what was found:

  • Number of documents in docs/
  • List the top-level structure

Call magslistdocs to see if MAGS already has indexed documents. If not, read each markdown file in docs/ and call magscreatedoc to index them into MAGS.

Tell the user: "Found existing docs/ directory with N documents. Indexed into MAGS."

2B. If docs/ does not exist — Gather project info

Ask the user these questions (all at once, not one by one):

  1. What is this project? (brief description)
  2. What is the tech stack?
  3. What is the current state? (new, in progress, mature)
  4. What is the architecture type? (monolith, microservices, library, cli, mobile, serverless)
  5. What language should documentation be in? (en, tr, or other locale)

Call magsdetectstack to auto-detect the project's tech stack. Use this information to enrich the docs.

Then create the docs/ directory structure using magscreatedoc with these templates. Pass the user's chosen locale (from question 5) as the locale parameter to each magscreatedoc call:

  • docs/architecture/overview.md — Project overview from user answers
  • docs/architecture/tech-stack.md — Tech stack details
  • docs/rules/coding-standards.md — Basic coding standards for the stack
  • docs/changelog/changes.md — Empty changelog

Stop here and wait for user answers before creating docs.

3. Create .mags/ directory

Create the following structure:

.mags/
  config.yaml    — MAGS configuration

config.yaml content:

version: 1
project_root: .
docs_path: docs/
locale: <user's chosen locale from question 5, e.g. "en" or "tr">
initialized_at: <current ISO date>

Use the locale code the user selected in question 5 (en, tr, etc.) as the locale value.

4. Offer CLAUDE.md generation

Ask the user: "Would you like me to generate a CLAUDE.md file based on your project docs?"

If yes, call magsgenerateclaude_md and write the result to the project root.

5. Save initial memory

Call mags_remember with:

  • key: project_initialized
  • value: Brief description of what was set up (e.g., "Project X initialized with N docs, tech stack: ...")
  • category: context
  • tags: ["init"]

This ensures the memory system has at least one entry from the start.

6. Summary

Print a summary:

MAGS initialized successfully.

  Project:    <name>
  Docs:       <N> documents indexed
  CLAUDE.md:  <generated / skipped>

Next steps:
  → /mags-help     — See all available commands
  → /mags-status   — View project dashboard
  → /mags-setup    — Get Claude Code configuration recommendations