ln-002-best-practices-researcher

Generate Guide, Manual, and ADR documents from MCP Ref/Context7 research.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill researches industry best practices and crafts documentation (guide/manual/ADR) from MCP Ref/Context7 findings, providing reusable outputs for Story notes.

Core Features & Use Cases

  • Identify patterns, standards, and best practices relevant to a Story.
  • Generate three output types: Guide (patterns), Manual (API references), and ADR (architecture decisions).
  • Return the path to generated documents for linking in Stories/Tasks.

Quick Start

Run a standards research pass to produce documentation artifacts (guide/manual/ADR) linked to the current Story context.

Frequently Asked Questions about ln-002-best-practices-researcher

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

FAQPage Schema
How do I document architectural decisions and best practices for my project?

This Skill researches industry standards and best practices, then produces three documentation artifacts: a Guide (pattern documentation), a Manual (API reference), and an ADR (architecture decision record). Each output is 300–500 words, cites sources from 2025 onward, and saves to your docs directories with proper naming for Story linking.

What's the best way to create ADRs and pattern guides from industry standards?

Run a standards research pass against MCP Ref/Context7 for your topic. The Skill identifies relevant patterns, libraries, and architectural decisions, then generates three linked documents—Guide, Manual, and ADR—ready to attach to your Story notes without manual compilation.

Can I generate API reference manuals and pattern documentation in one pass?

Yes. The Skill produces all three outputs—Guide, Manual, and ADR—in a single invocation, each meeting functional requirements: no code in guides, language preserved from your Story context, dated sources, and files saved with correct naming for retrieval.

Do I need to manually cite sources when documenting best practices?

No. The Skill automatically cites dated sources (2025+) in all documentation outputs. You receive research-backed Guides, Manuals, and ADRs with citations already embedded, ready for Story attachment.

What output formats and file structures does standards research produce?

The Skill generates three document types—Guide (patterns), Manual (API reference), and ADR (decisions)—each 300–500 words, saved to correct docs directories with proper naming. Paths are returned for direct Story linking without extra organization steps.

When should I use this for documentation instead of manual research and writing?

Use this Skill when you need repeatable, standards-backed documentation tied to a Story context. It handles research once per invocation, enforces consistent output formats, cites current sources, and delivers three linked artifacts faster than manual compilation, reducing research drift across documents.