init

Initialize or update CLAUDE.md with architecture context and plugin references.

30|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/joestump/claude-plugin-design --skill init-joestump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/joestump/claude-plugin-design/tree/main/skills/init
Command: npx skills add https://github.com/joestump/claude-plugin-design --skill init-joestump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures a repository has a standardized CLAUDE.md architecture context so Claude sessions can discover ADRs and OpenSpec specs without manual, error-prone setup.

Core Features & Use Cases

  • Automatic Detection and Creation: Checks for an existing CLAUDE.md, reads and updates it, or creates one when missing.
  • Idempotent Configuration: Adds references to docs/adrs/ and docs/openspec/specs/ only when absent and avoids duplicate sections.
  • Safe Path Handling and User Consent: Detects differing architecture path conventions and prompts the user before changing existing content, preserving other file contents.
  • Use Case: Run when installing the design plugin to prepare a repository so ADR and spec generation workflows integrate seamlessly with session context.

Quick Start

Ask the assistant to initialize design for this repository so it creates or updates CLAUDE.md with the plugin's architecture context.

Frequently Asked Questions about init

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

FAQPage Schema
How do I add architecture context to CLAUDE.md for ADRs and OpenSpec specs?

To add architecture context to CLAUDE.md, initialize the design plugin which automatically detects existing files, checks for docs/adrs/ and docs/openspec/specs/ paths, and updates the configuration idempotently while preserving existing content.

What is the best way to set up a CLAUDE.md file so Claude sessions can discover repository architecture?

Setting up a standardized CLAUDE.md file ensures Claude sessions discover repository architecture by reading or creating the file with references to docs/adrs/ and docs/openspec/specs/, avoiding manual and error-prone configuration steps.

Can I update an existing CLAUDE.md file without losing my current content?

You can update an existing CLAUDE.md file without losing content because the initialization process requires idempotent behavior, preserves existing sections, and adds architecture context references only when they are absent.

Does initializing design context in CLAUDE.md prompt before changing existing architecture paths?

Initializing design context in CLAUDE.md does prompt before changing existing architecture paths by using AskUserQuestion interaction to detect mismatches and request user consent, ensuring safe path handling during updates.

Why does my CLAUDE.md initialization not duplicate architecture context sections on repeated runs?

Your CLAUDE.md initialization avoids duplicating architecture context sections on repeated runs because it enforces idempotent behavior, checking for the presence of docs/adrs/ and docs/openspec/specs/ references before adding them.

Do I need a CLAUDE.md file to use ADR generation workflows with Claude?

You need a CLAUDE.md file for ADR generation workflows with Claude so sessions can automatically discover architecture context, and the initialization process creates one when missing or updates it with the required plugin references.