ln-120-reference-docs-creator

Generate ADRs, guides, and manuals from TECH_STACK with justification rules.

534|73|Updated Oct 24, 2025

Search Tags:#documentation #guide #adr #reference #manual

Ready to run

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-120-reference-docs-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-120-reference-docs-creator
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-120-reference-docs-creator
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-120-reference-docs-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill creates the structure for docs/reference (ADRs, Guides, Manuals) based on TECH_STACK, generating smart documents only for nontrivial technology decisions.

Core Features & Use Cases

Establishes docs/reference structure (adrs/guides/manuals)
Produces ADRs, Guides, and Manuals when justified
Uses technology justification rules to avoid trivial documentation
Returns paths for linking in larger documentation pipelines

Quick Start

Run ln-120-reference-docs-creator to initialize reference docs and generate justified ADRs/guides/manuals.

Frequently Asked Questions about ln-120-reference-docs-creator

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

FAQPage Schema

How do I create reference documentation for my technology stack?▼

Reference documentation creation automates building ADRs, guides, and manuals based on your tech stack. This Skill generates the docs/reference structure and produces justified documents only for nontrivial technology decisions, returning paths for integration into larger documentation pipelines.

What's the difference between ADRs, guides, and manuals in reference docs?▼

Architecture Decision Records (ADRs) capture justified technology choices, guides provide implementation workflows, and manuals document comprehensive tool usage. This Skill generates each type only when the technology decision warrants documentation, avoiding trivial entries.

How do I avoid creating unnecessary documentation for every technology choice?▼

Technology justification rules filter which decisions merit documentation. This Skill applies those rules to generate ADRs, guides, and manuals only for nontrivial choices, keeping reference docs focused and maintainable.

Can I use this to initialize docs structure and generate content in one step?▼

Yes. The Skill establishes the complete docs/reference structure with adrs, guides, and manuals directories, then generates justified content from your TECH_STACK in a single run, returning paths for downstream documentation pipelines.

What input data do I need to generate reference documents?▼

You need your TECH_STACK definition and technology justification rules stored in context_store. The Skill reads this context, creates directories, substitutes placeholders in templates, and generates ADRs, guides, and manuals accordingly.

Does this work with existing documentation workflows?▼

Yes. The Skill returns paths for linking in larger documentation pipelines, making it compatible with existing doc systems. It functions as an initialization and generation step within multi-stage documentation processes.