
Repo Architecture
- 172 installs
- 27.8k repo stars
- Updated August 5, 2026
- garrytan/gbrain
Map and explain gbrain repository layout, module boundaries, data flows, and extension points so agents navigate code safely and propose changes aligned with existing structure.
About
The repo-architecture skill builds a durable mental model of the garrytan/gbrain codebase for agents, documenting layers, dependencies, and conventions so subsequent coding and skill work stays consistent with project structure.
- Documents module and folder boundaries
- Explains key data and control flows
- Identifies extension and plugin points
- Links code areas to responsibilities
- Reduces blind edits in unfamiliar repos
Repo Architecture by the numbers
- 172 all-time installs (skills.sh)
- Ranked #544 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/garrytan/gbrain --skill repo-architectureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 172 |
|---|---|
| repo stars | ★ 27.8k |
| Last updated | August 5, 2026 |
| Repository | garrytan/gbrain ↗ |
What it does
Map and explain gbrain repository layout, module boundaries, data flows, and extension points so agents navigate code safely and propose changes aligned with existing structure.
Files
Repo Architecture — Filing Rules
Full filing rules: See skills/_brain-filing-rules.mdContract
This skill guarantees:
- Every new page is filed by primary subject (not format, not source)
- The decision protocol is followed for ambiguous cases
- Common misfiling patterns are caught
Phases
1. Identify the primary subject. What would you search for to find this page? 2. Walk the decision tree:
- About a person →
people/{name-slug}.md - About a company →
companies/{name-slug}.md - A reusable concept/framework →
concepts/{slug}.md - An original idea →
originals/{slug}.md - A meeting →
meetings/{slug}.md - Media content →
media/{type}/{slug}.md - Raw data import →
sources/{slug}.md
3. Cross-link. Link from related directories. 4. Check notability. See skills/conventions/quality.md notability gate.
Output Format
Advisory: "File this at {type}/{slug}.md because the primary subject is {reason}."
Anti-Patterns
- Filing by format ("it's a PDF so it goes in sources/")
- Filing by source ("it came from email so it goes in sources/")
- Creating pages without checking if one already exists
- Using
sources/for anything except raw data dumps