learn

Detect a project's technology stack and document architectural patterns in markdown.

13|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/fredericvilcot/clean-claude --skill learn-fredericvilcot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/fredericvilcot/clean-claude/tree/main/.claude/skills/learn
Command: npx skills add https://github.com/fredericvilcot/clean-claude --skill learn-fredericvilcot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the detection of your project's technology stack and architectural patterns, ensuring consistency and adherence to best practices.

Core Features & Use Cases

  • Stack Detection: Identifies all libraries used in your project beyond the mandatory stack (TypeScript, React, TanStack Query).
  • Architecture Learning: Analyzes code structure, naming conventions, and layer boundaries to document your project's architecture.
  • CRAFT Compliance Validation: Ensures your code adheres to Software Craft principles, refusing to learn from code smells.
  • Use Case: After setting up a new React project, run /learn to automatically generate documentation for all installed libraries and capture the project's architectural patterns, creating a living reference.

Quick Start

Run the learn skill to analyze your project's stack and architecture.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I automate technology stack detection for a React project?

Automate technology stack detection by running the analysis command to identify all installed libraries beyond mandatory frameworks like TypeScript and React, generating markdown documentation for your project's architectural patterns.

What is CRAFT compliance validation for code architecture?

CRAFT compliance validation ensures your code adheres to Software Craft principles by analyzing structure and naming conventions, refusing to document architectural patterns if it detects code smells.

Can I analyze external repositories or monorepo contexts for architecture documentation?

Yes, you can analyze external repositories and monorepo contexts to detect architectural patterns, validate layer boundaries, and generate markdown reference files for your entire codebase structure.

How do I generate documentation for installed libraries in my stack?

Generate library documentation by running the stack detection process, which automatically identifies all used libraries and creates corresponding skills and markdown files capturing their usage in your architecture.

Why does architecture learning refuse to document certain code structures?

Architecture learning refuses to document code structures that violate CRAFT principles, acting as a quality gate by rejecting code smells and ensuring only best-practice architectural patterns are captured.