repo-architecture

Route new brain pages to predefined subject directories using a decision-tree workflow.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/edwifiguy/era-agents-ops --skill repo-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-architecture
Source: https://github.com/edwifiguy/era-agents-ops/tree/main/skills/era-agents-op/gbrain/skills/repo-architecture
Command: npx skills add https://github.com/edwifiguy/era-agents-ops --skill repo-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Filing chaos in brain pages is reduced by enforcing a primary-subject routing protocol that standardizes where pages live and how they are discovered.

Core Features & Use Cases

  • Standardized routing: directs new pages to the correct top-level directories (people/, companies/, concepts/, originals/, meetings/, media/, sources/).
  • Decision-tree guidance: provides a deterministic workflow to resolve ambiguous subjects.
  • Cross-linking and governance: ensures related pages link back and that notability gates are respected.

Quick Start

Follow the primary-subject filing rules to route a new brain page to its correct directory.

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 content by primary subject to ensure consistent discoverability?▼

To organize brain content by primary subject, apply a standardized routing protocol that directs new pages to predefined top-level directories such as people, companies, concepts, and sources. This enforces consistent discoverability across all subjects.

What is the best way to resolve ambiguous subjects when filing brain pages?▼

The best way to resolve ambiguous subjects when filing brain pages is to follow a deterministic decision-tree workflow. This provides step-by-step guidance to route content to the correct predefined directory without guesswork.

How does the notability gate work for content management in brain pages?▼

The notability gate works as a governance rule to ensure only qualifying content is stored. It enforces cross-linking between related pages and validates that each new brain page meets specific criteria before it is filed in a directory.

Can I use a decision-tree workflow to route new pages to directories like media and meetings?▼

Yes, you can use a decision-tree workflow to route new pages to directories like media and meetings. The standardized routing protocol directs new brain content to predefined top-level directories based on the primary subject identified.

Why does filing chaos occur in brain pages and how can cross-linking prevent it?▼

Filing chaos occurs in brain pages due to inconsistent storage rules. Enforcing a primary-subject routing protocol with cross-linking prevents this by ensuring related pages link back to each other and respect notability gates for correct filing.

Do I need predefined directories to standardize brain content routing?▼

Yes, predefined directories are required to standardize brain content routing. The filing protocol directs new pages to specific top-level directories such as people, companies, concepts, originals, meetings, media, and sources to maintain organization.