ln-120-reference-docs-creator

Generate reference documentation hubs and smart documents from a TECH_STACK.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-120-reference-docs-creator-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-120-reference-docs-creator
Source: https://github.com/0xtaoist/taogate/tree/main/ln-120-reference-docs-creator
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-120-reference-docs-creator-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a scalable reference documentation hub (ADRs, Guides, Manuals) and smart documents based on the project's TECH_STACK, ensuring only justified, nontrivial choices are documented.

Core Features & Use Cases

  • Auto-generates docs/reference/ structure (adrs/, guides/, manuals/, research/) and a README hub.
  • Performs Phase 2 smart-document creation (ADRs, Guides, Manuals) only for nontrivial technology choices, with justification and alternatives.
  • Validates and maintains the hub structure across Phase 3 and Phase 4, including auto-discovery of existing files.
  • Integrates with the context store to reflect current tech decisions and research.

Quick Start

Invoke ln-120-reference-docs-creator when your TECH_STACK context is available to generate the reference docs hub and smart documents.

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 automate reference documentation generation for my tech stack?

Automate reference documentation by analyzing your tech stack to generate a complete docs hub, including ADRs, guides, and manuals. The process auto-discovers existing files and writes templates to ensure only justified, nontrivial technology choices are documented.

When do I need to create Architecture Decision Records for my project?

Create Architecture Decision Records when your project involves nontrivial technology choices that require justification. The automation validates your tech stack, generates ADR templates with alternatives, and updates the registry to reflect current decisions.

What is the best way to structure a scalable reference documentation hub?

Structure a scalable reference documentation hub by auto-generating a directory with ADRs, guides, manuals, and research folders alongside a README hub. This structure validates and maintains itself through auto-discovery of existing files across project phases.

Can I auto-discover existing documentation files when generating a new docs hub?

Auto-discover existing documentation files during the hub generation process. The automation validates the existing structure, identifies current ADRs, guides, and manuals, and updates the registry to accurately reflect all documented files.

How to justify nontrivial technology choices in project documentation?

Justify nontrivial technology choices by generating smart documents that analyze your tech stack and outline specific reasoning with alternatives. This ensures your reference documentation captures only meaningful architectural decisions rather than trivial configurations.

Does reference docs automation work without predefined dependencies?

Reference docs automation works without predefined dependencies, relying solely on your available TECH_STACK context. It analyzes the provided tech stack to generate the documentation hub, write templates, and integrate decisions into the context store.