supermind-init

Initialize Supermind projects by generating CLAUDE.md, living documentation, and local configs.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/steven-3/supermind --skill supermind-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supermind-init
Source: https://github.com/steven-3/supermind/tree/main/skills/supermind-init
Command: npx skills add https://github.com/steven-3/supermind --skill supermind-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a new repository with consistent Supermind configuration is hard, especially when CLAUDE.md, ARCHITECTURE.md, and DESIGN.md are missing or out of sync.

Core Features & Use Cases

  • Initializes CLAUDE.md with safe section-level merging while preserving project-specific content and refreshing Supermind infrastructure sections.
  • Auto-detects your tech stack and scaffolds local configs by generating .claude/settings.local.json and optionally .mcp.json based on detected indicators.
  • Generates AI-optimized living documentation by scanning the repo to create or migrate ARCHITECTURE.md and DESIGN.md (for UI projects), then verifies the results with spot checks and commits via Git.
  • Improves project health and tool discovery by checking setup signals (sessions, semantic navigation) and researching relevant additional tools without auto-installing.

Quick Start

Tell your AI agent: run the supermind-init skill to initialize this project’s CLAUDE.md, living documentation (ARCHITECTURE.md and optional DESIGN.md), and health/discovery scaffolding.

Frequently Asked Questions about supermind-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate and merge CLAUDE.md without losing existing project configurations?▼

To generate and merge CLAUDE.md without losing content, use template-based section-level merging. This preserves project-specific configurations while refreshing Supermind infrastructure sections during project initialization.

What is the best way to auto-detect a tech stack and scaffold local MCP configs?▼

Auto-detecting a tech stack and scaffolding local MCP configs is done by generating .claude/settings.local.json and .mcp.json based on detected repository indicators, avoiding any auto-installation of packages.

Can I migrate existing ARCHITECTURE.md and DESIGN.md files into AI-optimized living documentation?▼

You can migrate or create ARCHITECTURE.md and DESIGN.md into AI-optimized living documentation by scanning the repository, generating token-efficient table outputs, and verifying results with spot checks.

Does the project initialization process auto-install discovered health and setup tools?▼

The project initialization process does not auto-install discovered tools. It checks setup signals and researches relevant health tools, leaving the actual installation as a manual step for the user.

Why do my Supermind docs keep falling out of sync across new repositories?▼

Supermind docs fall out of sync when repositories are missing or outdated. Running a setup flow triggered by /supermind-init scans the repo and updates documentation to maintain consistency.