Verified:GitHub

literate-programming

Analyze codebases and generate narrative-driven Literate Architecture Records.

18|Updated Feb 8, 2026

Search Tags:#architecture #software engineering #code analysis #documentation #literate programming #progressive disclosure

Ready to run

npx skills add https://github.com/goldengrape/skills --skill literate-programming-goldengrape

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: literate-programming
Source: https://github.com/goldengrape/skills/tree/main/literate-programming
Command: npx skills add https://github.com/goldengrape/skills --skill literate-programming-goldengrape

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the challenge of understanding and documenting complex codebases by applying the principles of Literate Programming, transforming code into a narrative.

Core Features & Use Cases

Narrative Code Analysis: Deeply analyze codebases by "weaving" code snippets into a coherent, story-like explanation.
Literate Architecture Records (LAR): Generate structured, human-readable documentation that explains the 'why' behind the code.
Use Case: When onboarding a new developer to a legacy system, use this Skill to generate a LAR that explains the architecture as if telling a story, making it easier to grasp the system's design and intent.

Quick Start

Use the literate programming skill to analyze the architecture of the current project and generate a Literate Architecture Record.

Frequently Asked Questions about literate-programming

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

FAQPage Schema

How do I document a legacy codebase for new developer onboarding?▼

Narrative code analysis treats code as prose by weaving code snippets into a coherent, story-like explanation. It helps developers understand complex software architecture by focusing on the narrative flow rather than isolated logic blocks.

What is the best way to explain the 'why' behind complex software architecture?▼

Literate Architecture Records (LARs) are structured, human-readable documentation that explain the 'why' behind code. They use progressive disclosure to present architectural decisions sequentially, helping readers deeply understand system design.

How do I generate a Literate Architecture Record for my current project?▼

To generate a Literate Architecture Record, trigger a narrative-driven code analysis on your current project. The system will apply progressive disclosure to weave code snippets into a structured story explaining your architecture.

Does literate programming work for analyzing any codebase scale?▼

Literate programming applies to any codebase scale by treating documentation as sequential instructions. It facilitates deep understanding of code by transforming complex architectural structures into a coherent, human-readable narrative.

When should I use narrative-driven code analysis instead of standard documentation?▼

Use narrative-driven code analysis when standard documentation fails to convey architectural intent. It is ideal for explaining complex system design and onboarding developers by treating code as prose and generating story-like Literate Architecture Records.