Browse code by meaning
6 comments · 55% upvoted · source · other discussions
comments
chickenbomb52
Backyard13
one of the most meaningful views according to Mitchel Hashimoto
Pozzuh
Interesting idea, but the current implementation seems quite noisy. I ran this on my OSS project Fragno, to give readers an idea:
▼ /Users/me/dev/fragno (1568)
├── ▼ Fragment Platform (106)
│ ├── ▶ Fragment Authoring (7)
│ ├── ▶ *.md: Developer Guidelines (9)
│ ├── ▶ Upload Fragment (10)
│ ├── ▶ Stripe Integration (9)
│ ├── ▶ Service Middleware (6)
│ ├── ▶ Server Integration (12)
│ ├── ▶ Corpus Tools (9)
│ ├── ▶ Project Overview (11)
│ ├── ▶ apps/docs/content/docs/*meta.json: Docs Metadata (14)
│ ├── ▶ packages/auth/src/*.ts: Auth Services (12)
│ └── ▶ packages/auth/src/*.ts: Auth Types (7)
├── ▶ Schema Runtime (205)
├── ▶ Release Workflow (66)
├── ▼ Workflow Runner (100)
│ ├── ▶ *.md: Workflows Implementation (6)
│ ├── ▶ Dispatcher Implementation (5)
│ ├── ▶ Workflows Documentation (6)
│ ├── ▶ Test Prompts (6)
│ ├── ▼ Durable Hooks (4)
│ │ ├── apps/docs/content/docs/fragno/for-library-authors/database-integration/durable-hooks.mdx: Durable hooks usage and guidance
│ │ ├── packages/fragno-db/src/hooks/durable-hooks-processor.ts: Create durable hooks processor utility
│ │ ├── packages/fragno-db/src/hooks/hooks.ts: Hook lifecycle and scheduling implementation
│ │ └── packages/fragno-test/src/durable-hooks.ts: Test helper to drain hooks
│ ├── ▶ *.ts: Workflow Servers (5)
│ ├── ▶ *.ts: Database Schemas (4)
│ ├── ▶ *.test.ts: Workflow Tests (5)
│ ├── ▶ Runner Internals (5)
│ ├── ▶ packages/fragment-workflows/src/*.ts: Fragment Core (7)
│ ├── ▶ packages/frag*.ts: Bindings Adapter (4)
│ ├── ▶ packages/fragment-workflows/src/runner*.ts: Runner Orchestrator (4)
│ ├── ▶ packages/fragment-workflows/src/*s.ts: Runner Utilities (4)
│ ├── ▼ packages/fragment-workflows/workflows-smoke-artifacts/*.js: Concurrency Tests
(and it goes on for a while, but Reddit doesn't allow me to post it all)
elperroborrachotoo
Looks like your code is not AI tooling compatible, please fix! :)
Srsly, I applaud OPs approach to use AI for the boring parts, too
Interesting! In a programming projects ideally I'd hope this is roughly how the folders are grouped in general (by what the code does). Maybe this has a future as an folder structure refactoring tool (for code or other files)?
Tekmo [OP] 1 points · Feb 2026
Yeah, my partner suggested something similar when test-driving this: that one possible application of this is to identify places where the project organization should be fixed