bridge-explorer
Skill13 starsChanged 13 days agoMITView on GitHub
Bridge visualizations: ecosystem map (repos, workspaces, skills, infra), repo layout (CORE/USER split), and constellation (information flow). Trigger: "/bridge-explorer", "explorer", "show ecosystem", "repo layout", "where do files live", "constellation".
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/board-pilot/references/agents.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- a2aSkill
- archiveSkill
- board-pilotSkill
- bridge-auditSkill
- bridge-contributeSkill
- bridge-curatorSkill
- bridge-greetingSkill
- bridge-leak-checkSkill
- bridge-learnSkill
- bridge-onboardSkill
- bridge-overlaySkill
- bridge-promoteSkill
- bridge-statusSkill
- bridge-syncSkill
- briefingSkill
- calendarSkill
- capability-brokerSkill
- channelSkill
- cmuxSkill
- cockpitSkill
- dashboardSkill
- debriefSkill
- doc-systemSkill
- github-projects-managerSkill
- html-canvasSkill
- html-slidesSkill
- knowledge-repo-initSkill
- mail-draftSkill
- mandantsSkill
- meeting-transcriptionSkill
- object-storeSkill
- onboard-simSkill
- remoteSkill
- scheduleSkill
- secretsSkill
- spec-kickoffSkill
- task-close-postmortemSkill
- tmuxSkill
- tracker-syncSkill
- workloadSkill
- workspaceSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the referenced file ONLY when triggered.
- Very specific: line 33
All variants render the same CORE/USER + cluster-wrapper split, sourced from docs/repo-layout/regions.yaml (single source of truth — edit …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bridge Explorer
Visualize Bridge state as interactive HTML dashboards. Read the referenced file ONLY when triggered.
Decision Tree
User wants to...
├── Ecosystem visualization → Read references/workflow.md
├── CORE/USER repo split visual → Read references/repo-layout.md
│ (triggers: "repo layout", "core/user", "where do files live",
│ "repo structure"; pick variant v1–v4 or c-prime, see below)
├── Information flow / network → Render + open the network variant
│ (triggers: "network diagram", "constellation", "how is everything linked",
│ "how does the bridge distribute information", "layers")
└── Questions about ecosystem → Read ecosystem.yaml directlyRepo-layout variants
All variants render the same CORE/USER + cluster-wrapper split, sourced from
docs/repo-layout/regions.yaml (single source of truth — edit there, all
variants pick up on regenerate).
Constellation (network) is generated, not hand-edited. Its nodes/edges/flows
live in regions.yaml under constellation: (schema v3). After editing them run:
python3 docs/repo-layout/build-constellation.pyThis injects the JS data block into network.html between the CONSTELLATION-DATA
markers and bumps the version badge. Precondition: network.html must have been
rendered first — the script refreshes the data block of an existing rendered file;
on a fresh clone there is no network.html yet, so render it via this skill first.
Wire it into your deploy pipeline so the served HTML never drifts from
regions.yaml by hand.
| Variant | Lens |
| c-prime | Editorial cluster/top-level map (primary, dense) |
| network | Constellation — 5-ring information network (hub → brain → synapses → memory → state → world), 4 sectors (Meta · Operations · CustomerA · Identity), bundled edges, named flows |
| v1 | Hemispheric brain (CORE left, USER right) — static SVG |
| v2 | Brain with anatomical region labels + side panel |
| v3 | Interactive brain — click region for drill-down |
| v4 | Minimal two-column schematic — dense, print-friendly |
User-facing MOC: docs/repo-layout.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.