repo-architecture

Determines the correct directory for new brain pages by primary subject.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill repo-architecture-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-architecture
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/plugin/skills/repo-architecture
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill repo-architecture-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When writing new pages into a knowledge base, it is easy to file content by format or source instead of subject, which fragments the repository and makes pages hard to find. This Skill provides a decision protocol that routes every new page to the correct directory based on its primary subject. ## Core Features & Use Cases - Subject-Based Filing Decision Tree: Routes pages to people/, companies/, concepts/, originals/, meetings/, media/, or sources/ directories based on what the page is about. - Anti-Pattern Detection: Catches common misfiling mistakes such as filing by format (PDF goes to sources/) or by source (email goes to sources/). - Advisory Output: Returns a concrete recommendation like "File this at companies/acme.md because the primary subject is Acme Corp." - Use Case: After a meeting with a startup founder, you have notes covering the person, their company, and an investment idea. Use this Skill to decide whether the content becomes one page or several, and exactly where each page belongs. ## Quick Start Ask where a new page about a person, company, meeting, or idea should be filed and follow the decision tree recommendation.

Frequently Asked Questions about repo-architecture

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

FAQPage Schema
How do I decide where to file a new knowledge base page?

Identify the primary subject of the page by asking what you would search for to find it. Then follow the decision tree: people go to people/, companies to companies/, concepts to concepts/, meetings to meetings/, and raw data imports to sources/.

How should I organize notes by subject instead of format?

File every page by what it is about, not its file type or origin. A PDF about a person belongs in people/, not sources/; sources/ is reserved only for raw data dumps with no primary subject.

What are common mistakes when filing knowledge base pages?

The main anti-patterns are filing by format, filing by source such as email, creating duplicate pages without checking for existing ones, and misusing the sources/ directory for anything other than raw data imports.

When should content be split into multiple pages?

Split content when it covers multiple distinct primary subjects, such as a meeting note that also introduces a new company. File each subject in its own directory and cross-link between the related pages.

Does this filing protocol modify existing pages?

No, the Skill is non-mutating and advisory only. It outputs a recommendation stating where a page should be filed and why, leaving the actual file creation to the user or other writing skills.