ln-111-root-docs-creator

Generate four root documentation files from a Context Store with template substitution.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-111-root-docs-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-111-root-docs-creator
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-111-root-docs-creator
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-111-root-docs-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates 4 root documentation files (CLAUDE.md, docs/README.md, documentation_standards.md, principles.md).

Core Features & Use Cases

  • Generates root docs from templates
  • Self-validates structure and content
  • Integrates legacy content when available

Quick Start

Create CLAUDE.md and related root docs in the project root.

Frequently Asked Questions about ln-111-root-docs-creator

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

FAQPage Schema
How do I bootstrap root documentation files for a new project?

Root docs bootstrap generates four standardized files—CLAUDE.md, docs/README.md, documentation_standards.md, and principles.md—from templates and context data during project onboarding. This creates consistent documentation structure and establishes documentation principles upfront.

What documentation files does the root docs creator generate?

The Skill generates CLAUDE.md as the project entry point, docs/README.md for directory guidance, documentation_standards.md defining writing and structure conventions, and principles.md capturing project values. All are created from templates with placeholder substitution.

Can I preserve existing documentation when generating root docs?

Yes. The Skill respects legacy content precedence for principles.md, augmenting templates with existing principles when available. File creation is idempotent, allowing safe re-runs without overwriting custom content when integrated properly.

How does root docs initialization validate its output?

The Skill self-validates generated documentation structure through 22 validation questions, ensuring templates are correctly substituted, files meet documentation standards, and content aligns with project principles before reporting status to the coordinator.

What input does the root docs creator require?

The Skill ingests a Context Store containing project metadata and a target directory path. It substitutes placeholders from this context into documentation templates to generate all four root files consistently.

When should I use root documentation bootstrap in my workflow?

Apply root docs bootstrap during project onboarding and documentation coordination phases to establish standardized templates early. It ensures new projects start with consistent documentation principles and structure from day one.