ln-112-project-core-creator

Generate requirements, architecture, tech stack, and patterns documentation files.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-112-project-core-creator-cbbkrd-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-112-project-core-creator
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-112-project-core-creator
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-112-project-core-creator-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill automates the creation of essential project documentation, ensuring consistency and saving developers significant time on boilerplate writing.

Core Features & Use Cases

  • Automated Document Generation: Creates requirements.md, architecture.md, and tech_stack.md based on project context.
  • Legacy Content Integration: Merges existing legacy documentation data for a smoother transition.
  • Use Case: When starting a new project, this Skill can be invoked to immediately generate the foundational documentation files, populated with discovered project details and legacy information if available.

Quick Start

Use the ln-112-project-core-creator skill to generate the core project documentation files.

Frequently Asked Questions about ln-112-project-core-creator

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

FAQPage Schema
How do I generate core project documentation like requirements and architecture files?

To generate core project documentation, this Skill automatically creates requirements.md, architecture.md, tech_stack.md, and patterns catalog files by auto-discovering project details and merging legacy content. It ensures arc42 compliance and generates C4 diagrams for visual architecture representation.

What is arc42 compliance and how does it apply to project documentation generation?

Arc42 compliance is a standard structure for architecture documentation that this Skill enforces when generating architecture.md and patterns catalog files. It ensures consistent documentation by integrating with a context store and auto-discovering project details to populate the required arc42 sections.

Can I integrate existing legacy documentation when generating new project architecture files?

Yes, legacy content integration merges existing legacy documentation data into the newly generated requirements.md, architecture.md, and tech_stack.md files. This ensures smoother transitions by preserving and incorporating prior documentation into the arc42-compliant output.

Does this documentation generation approach work with a context store for auto-discovering project details?

Yes, project documentation generation integrates with a context store and utilizes auto-discovery to identify project details automatically. This allows the Skill to populate requirements, architecture, tech stack, and patterns catalog files without manual input of technical specifications.

What is the best way to ensure consistent boilerplate documentation across new software projects?

The best way to ensure consistent boilerplate documentation is to automate the creation of foundational files using project detail auto-discovery. This Skill generates arc42-compliant requirements, architecture, tech stack, and patterns files with C4 diagrams, eliminating manual boilerplate writing.

What are the limitations of auto-discovery when generating tech stack and patterns catalog files?

Auto-discovery is limited to detecting project details available in the integrated context store and any provided legacy content. It cannot infer undocumented architectural decisions or external tech stack dependencies not present in the source environment during the documentation generation process.