How does this differ from a standard project README?

While root READMEs focus on installation and usage, this skill is specifically designed for internal directory documentation to explain folder-specific logic and context.

Is this skill specific to certain programming languages?

No, the principles of explaining organizational logic and mental models apply to any software project regardless of the language used.

Can this skill help with project onboarding?

Yes, by providing high-level context and explaining relationships between folders, it makes it much easier for new developers to navigate complex codebases.

Does it automatically list the files in the directory?

No, it explicitly avoids listing files that are already visible via 'ls', focusing instead on the underlying purpose and mental model of the folder.

Folder README Architect

Name: Folder README Architect
Author: EpicenterHQ

byEpicenterHQ

•

3,817

Learning & Documentation

Crafts purposeful internal directory documentation that explains organizational logic and architectural context.

About

The Folder README Architect skill provides a specialized framework for documenting internal project directories, moving beyond redundant file listings to focus on the 'why' behind directory structures. It guides Claude to explain mental models, organizational reasoning, and non-obvious context, helping developers understand how different parts of a codebase relate to one another. By emphasizing purpose over simple file enumeration, this skill ensures that internal documentation serves as a valuable map for current contributors and future maintainers.

Key Features

3,817 GitHub stars
Promotes scannable and concise documentation styles
Provides guidance on where to place new code
Clarifies relationships between different project folders
Focuses on organizational logic and mental models
Eliminates redundant file listings and obvious context

Use Cases

Improving codebase discoverability for new team members during onboarding
Explaining the purpose of utility and converter directories during a refactor
Standardizing documentation across a large-scale monorepo

About

Key Features

3,817 GitHub stars
Promotes scannable and concise documentation styles
Provides guidance on where to place new code
Clarifies relationships between different project folders
Focuses on organizational logic and mental models
Eliminates redundant file listings and obvious context

Use Cases

Improving codebase discoverability for new team members during onboarding
Explaining the purpose of utility and converter directories during a refactor
Standardizing documentation across a large-scale monorepo