ln-120-reference-docs-creator

Generate ADRs, guides, and manuals from a TECH_STACK.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-120-reference-docs-creator-dorrio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-120-reference-docs-creator
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-120-reference-docs-creator
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-120-reference-docs-creator-dorrio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of essential technical documentation, ensuring that only non-trivial technology choices are documented, thereby reducing unnecessary overhead.

Core Features & Use Cases

  • Automated Documentation Generation: Creates a structured documentation set including ADRs, Guides, and Manuals.
  • Context-Aware Generation: Bases documentation on the project's TECH_STACK and conversational context.
  • Use Case: When introducing a new, complex library into a project, this skill can automatically generate an Architecture Decision Record (ADR) explaining the choice and a user guide for its integration.

Quick Start

Use the ln-120-reference-docs-creator skill to generate documentation for the current tech stack.

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 generate an Architecture Decision Record for a new tech stack?▼

To generate an Architecture Decision Record (ADR), provide the Skill with your project's TECH_STACK and conversational context. It automatically creates justified ADRs, guides, and manuals, focusing only on non-trivial technology choices to ensure concise technical documentation.

What is the best way to document only non-trivial technology choices?▼

The best way to document non-trivial technology choices is to use an automated documentation generator that analyzes your TECH_STACK. This filters out standard choices and produces only relevant ADRs and user guides, reducing unnecessary overhead.

Can I use conversational context to create technical guides and manuals?▼

Yes, you can use conversational context alongside your TECH_STACK to create technical guides and manuals. The context-aware generation ensures the documentation accurately reflects the specific integration scenarios and technology choices discussed.

Does automated documentation generation work for complex library integrations?▼

Automated documentation generation works effectively for complex library integrations by creating structured ADRs explaining the choice and user guides for the integration. It uses your TECH_STACK to ensure the reference documentation is relevant and concise.

Why should I exclude standard technology choices from reference documentation?▼

Excluding standard technology choices from reference documentation reduces unnecessary overhead and keeps docs concise. By documenting only non-trivial tech stack choices, the generated ADRs and guides maintain higher relevance for software engineering teams.