Skip to content

Add section on folder organization as system map - #1

Open
benvinegar wants to merge 3 commits into
mainfrom
claude/skill-file-flat-repos-928mif
Open

Add section on folder organization as system map#1
benvinegar wants to merge 3 commits into
mainfrom
claude/skill-file-flat-repos-928mif

Conversation

@benvinegar

Copy link
Copy Markdown
Member

This PR expands the code discoverability guide with a new section on folder organization principles.

Summary

Added a new section (2) on using folders as a navigational map of the codebase, with supporting clarifications to existing sections. This emphasizes that while folders should group related files logically, the actual context and meaning should still live in symbol names rather than folder paths.

Key changes

  • New section 2: "Folders are the map" — Explains that directory listings should serve as a high-level overview of the system, grouping related files by feature, domain, or layer. Clarifies that folders provide organization but symbols should remain self-documenting.
  • Updated section 1 clarification — Added explicit note that folders group related files but don't carry the name's context, reinforcing the separation of concerns between folder structure and symbol naming.
  • Renumbered subsequent sections — Sections "Types are the documentation agents can't skip" and "Say it where the search lands" are now sections 3 and 4 respectively.
  • Updated checklist — Added item 7 to the review checklist to verify that new files are placed in appropriate folders and that the overall folder structure still reads as a coherent system map.

Implementation details

The changes maintain consistency with the existing guide's philosophy: discoverability through clear naming and organization. The new section reinforces that folder structure and symbol naming serve complementary but distinct purposes in making code navigable.

https://claude.ai/code/session_014C4qvBvsHQScHF5idhxk6g

claude added 3 commits August 19, 2026 15:13
…mes disambiguate

The skill's 'put the context in the symbol, not the folder' rule plus
'one searchable concept per file' was being read as 'folders are
useless', producing source roots with dozens of flat files (e.g.
modem-dev/cli needed a follow-up PR to organize 67 flat files in src/).

- Clarify the module-path bullet: it's about what a name must carry,
  not an argument against folders.
- Add a section on directory structure: group files into domain-named
  subfolders, split by feature/layer not syntax kind, folders group but
  still don't disambiguate.
- Point the file-splitting bullet at the subsystem folder instead of
  the source root, and add a checklist item for folder hygiene.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014C4qvBvsHQScHF5idhxk6g
Drop the prescriptive rules (specific layouts, entry-count thresholds,
banned folder names) in favor of the general point: group related files
into folders so a directory listing reads as a map, with whatever
organizing principle fits the codebase.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014C4qvBvsHQScHF5idhxk6g
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants