repo-architecture

Route new brain pages to directories by primary subject.

174|144|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/inbrainfun/inbrain --skill repo-architecture-inbrainfun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-architecture
Source: https://github.com/inbrainfun/inbrain/tree/main/skills/repo-architecture
Command: npx skills add https://github.com/inbrainfun/inbrain --skill repo-architecture-inbrainfun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents and enforces a filing protocol to route brain-related content to the correct pages, improving consistency and discoverability.

Core Features & Use Cases

  • Standardized Filing Protocol: Always file by primary subject to avoid format- or source-based misfiling.
  • Decision Tree Guidance: Navigate to the appropriate directory (people, companies, concepts, originals, meetings, media, sources) based on subject.
  • Cross-linking and Notability: Ensure related pages are linked and pass notability checks.

Quick Start

Review a new brain page request and file it according to the primary subject using the decision tree rules.

Frequently Asked Questions about repo-architecture

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

FAQPage Schema
How do I organize brain pages by primary subject instead of format or source?

To organize brain pages by primary subject, route each new page to the correct directory—people, companies, concepts, originals, meetings, media, or sources—using a decision-tree workflow that enforces consistent filing and cross-linking.

What is the best way to standardize a taxonomy and filing protocol for notes?

Standardizing a taxonomy and filing protocol requires applying deterministic rules that route pages to directories by primary subject, enforcing notability checks, cross-linking related pages, and avoiding format-based misfiling.

How does the decision-tree workflow handle ambiguous brain page filing?

The decision-tree workflow handles ambiguous brain page filing by applying deterministic routing rules based on primary subject, ensuring common ambiguities between people, companies, concepts, and media are resolved consistently.

When should I avoid format-based or source-based filing for my notes?

You should avoid format-based or source-based filing whenever a brain page has a clear primary subject, as the protocol enforces subject-level routing to prevent misfiling and ensure discoverability across people, concepts, and meetings.

Can I use this filing protocol for cross-linking meetings, media, and data sources?

Yes, you can use this filing protocol for cross-linking meetings, media, and data sources, as it explicitly applies across these categories to ensure related pages are linked and pass notability checks.