bridge
/bridge
Zapisuje na bieżąco powiązania między projektami, na przykład wspólny wzorzec, most między ludźmi czy narrację zasilającą inny projekt, jako ustrukturyzowany YAML w thinking/bridges/.
- Autor
- digital-stoic-org ↗
- Repozytorium
- agent-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zapisuje na bieżąco powiązania między projektami, na przykład wspólny wzorzec, most między ludźmi czy narrację zasilającą inny projekt, jako ustrukturyzowany YAML w thinking/bridges/.
Wyzwalacze z opisu
Argumenty
/bridge <source> → <target>: <description>
Oryginalny opis (EN)
Capture cross-project connections on the fly. Use when you notice a link between two projects — a shared pattern, a people-bridge, a narrative that feeds another project. Persists to thinking/bridges/ as structured YAML. Use when user says "bridge", "this connects to", "this feeds into", "same pattern as", or explicitly names a cross-project link.
Jak działa
- Why
- Step 0: Load Config
- Archetypes
- Commands
- Storage
- Capture (/bridge <args>)
- List (/bridge list [project])
- Map (/bridge map)
- Stats (/bridge stats)
- Key Behaviors
Podgląd SKILL.md
---
name: bridge
description: >
Capture cross-project connections on the fly. Use when you notice a link between
two projects — a shared pattern, a people-bridge, a narrative that feeds another
project. Persists to thinking/bridges/ as structured YAML. Use when user says
"bridge", "this connects to", "this feeds into", "same pattern as", or explicitly
names a cross-project link.
allowed-tools: [Bash, Read, Write, Edit, Glob]
model: haiku
argument-hint: "<source> → <target>: <description>"
context: main
user-invocable: true
---
# Bridge — Cross-Project Connection Capture
Capture cross-project bridges in the moment, while you're in context. Bridges are knowledge — they live in `thinking/bridges/`, not in project artifacts.
## Why
Bridges are discovered during work, not during planning. When you're deep in a meeting and realize "this pattern connects to another project" — that's when `/bridge` captures it.
## Step 0: Load Config
Read `$PRAXIS_DIR/config/projects.yaml`. This file contains:
- Project aliases (keys), names, roles, tiers, goals, flywheel roles
- Stakeholders with `also_in` cross-references (for people-bridge detection)
- GTD and praxis paths
Use project YAML keys as aliases (case-insensitive matching). If a user types a project name instead of alias, fuzzy-match against `name` fields.
If config missing → `⚠️ No project config found at $PRAXIS_DIR/config/projects.yaml. Create it with your project definitions.`
## Archetypes
Every bridge has a type. The 10 archetypes:
| Code | Archetype | One-liner |
|---|---|---|
| `flywheel` | 🔄 Flywheel loop | Output of A feeds B feeds C → back to A |
| `knowledge` | 🧠 Knowledge cascade | Framework/learning from one domain reusable in another |
| `people` | 👤 People-bridge | Same person carries context across projects |
| `terrain` | 🌱 Terrain d'essai | One project is live lab for methods used in another |
| `narrative` | 📖 Narrative amplifier | One project generates stories that make another credible |
| `identity` | 🎭 Identity coherence | Projects collectively tell a story about who you are |
| `complexity` | 🔬 Complexity lab | Managing complexity in one domain trains patterns for another |
| `local` | 🤝 Local network overlay | Geographic proximity creates compound serendipity |
| `option` | ⚡ Option value | One project creates future optionality for another |
| `mirror` | 🪞 Mirror project | Introspective insights reshape how other projects are framed |
## Commands
| Command | Action |
|---|---|
| `/bridge <src> → <tgt>: <desc>` | Capture a bridge (auto-detect archetype) |
| `/bridge <src> → <tgt> [type]: <desc>` | Capture with explicit archetype |
| `/bridge list` | Show recent bridges (last 10) |
| `/bridge list <project>` | Show bridges involving a project |
| `/bridge map` | Generate mermaid bridge map from all captures |
| `/bridge stats` | Weekly summary — counts by project and archetype |
## Storage
**Directory:** `$PRAXIS_DIR/thinking/bridges/`
Each bridge is a YAML file: `{date}-{seq}-{source}-to-{target}.yaml`
Example: `2026-04-08-1-hp-to-brand.yaml`
**Sequence**: Within a day, increment seq (1, 2, 3...). Check existing files for the day to determine next seq.
### Schema
```yaml
source: HP
target: BR
archetype: narrative
emoji: 📖
description: "Philosopher council on construct AI → reframes human-centric positioning from marketing to philosophy"
direction: one-way # one-way | bidirectional
strength: potential # active | potential | theoretical
context: "During introspect session, realized philosopher encounters are unique differentiator"
date: 2026-04-08
```
**Fields:**
- `source`, `target`: Project alias (uppercase, from config keys)
- `archetype`: One of the 10 codes
- `emoji`: Archetype emoji
- `description`: The bridge itself — what flows from source to target
- `direction`: `one-way` (A→B only) or `bidirectional` (A↔B, create one file with note)
- `strength`: `active` (happening now), `potential` (could happen, not activated), `theoretical` (speculative)
- `context`: Optional — what triggered the discovery (session, meeting, realization)
- `date`: ISO date
## Capture (`/bridge <args>`)
### Parse Arguments
Input: `/bridge HP → BR: philosopher encounters reframe human-centric positioning`
1. Split on `→` to get source and rest
2. Split rest on `:` to get target (+ optional `[type]`) and description
3. Resolve aliases against config keys (case-insensitive). If no match, fuzzy-match against `name` fields.
4. If `[type]` present, use it; otherwise auto-detect archetype
### Auto-Detect Archetype
If no explicit type, use two signals:
**Signal 1 — Keywords in description:**
- "pattern", "framework", "method", "learned", "reusable" → `knowledge`
- Person name (check config stakeholders) or "carries context", "cross-pollinates" → `people`
- "story", "credibility", "proof", "case study" → `narrative`
- "test ground", "lab", "experiment", "tried in" → `terrain`
- "loop", "feeds back", "cycle" → `flywheel`
- "brand", "who I am", "positioning", "identity" → `identity`
- "admin", "bureaucracy", "same skill", "transfers" → `complexity`
- "local", "geographic" → `local`
- "future", "optionality", "if it works", "unlocks" → `option`
- "introspect", "philosopher", "reframe", "reshape" → `mirror`
**Signal 2 — Config context:**
- If source or target has `flywheel_role: terrain` → lean toward `terrain`
- If source or target has `flywheel_role: mirror` → lean toward `mirror`
- If a stakeholder name appears in description and has `also_in` → `people`
If ambiguous, default to `knowledge` and mention in response.
### Detect Direction & Strength
- Default: `one-way`, `potential`
- If description contains "↔" or "bidirectional" or "both ways" → `bidirectional`
- If description contains "already", "happening", "active", "doing this" → `active`
- If description contains "could", "should", "would", "not yet" → `potential`
- If description contains "maybe", "speculative", "in theory" → `theoretical`
### Write File
1. Guard: check `$PRAXIS_DIR` is set. If not: `⚠️ $PRAXIS_DIR not set. Set via: export PRAXIS_DIR="$HOME/dev/praxis"`
2. `mkdir -p $PRAXIS_DIR/thinking/bridges/`
3. Determine seq: count existing `{date}-*` files + 1
4. Write YAML file
5. Respond (one line): `🔗 Bridge #N: {emoji} {source} → {target} ({archetype}) — {short desc}`
6. **Weekly nudge** (optional): count bridges this week. If ≥3 involving same project pair: append `📊 {N} bridges this week involving {pair}. Consider updating Ponts Stratégiques during review.`
7. **Resume prior work immediately.**
## List (`/bridge list [project]`)
1. `Glob` for `$PRAXIS_DIR/thinking/bridges/*.yaml`
2. Read each file, parse YAML
3. If project filter: match against config aliases or names (case-insensitive)
4. Sort by date desc, show last 10
5. Display:
```
🔗 Bridges (last 10)
1. 2026-04-08 📖 HP → BR: philosopher encounters reframe positioning (potential)
2. 2026-04-08 🧠 BNP → HP: observability patterns = atelier content (active)
3. 2026-04-07 👤 HP ↔ SL: Matthieu carries context both ways (active)
```
If empty: `🔗 No bridges captured yet. Use /bridge <source> → <target>: <description>`
## Map (`/bridge map`)
1. Read config for project names (display labels)
2. Read all bridge files
3. Generate mermaid graph using config names as node labels:
```mermaid
graph LR
classDef active fill:#90EE90,stroke:#333,color:#000
classDef potential fill:#FFE4B5,stroke:#333,color:#000
classDef theoretical fill:#FFB6C1,stroke:#333,color:#000
HP["Homo Promptus"] -->|"📖 narrative"| BR["Personal Brand"]:::active
DS["Digital Stoic"] -->|"🧠 patterns"| HP:::potential
HP <-->|"👤 Matthieu"| SL["Slasheo"]:::active
```
4. Group by strength (active=green, potential=orange, theoretical=pink)
5. Output the mermaid block
## Stats (`/bridge stats`)
1. Read all bridge files
2. Read config for tier info
3. Count by: project (as source + target), archetype, strength, tier, this-week vs all-time
4. Display:
```
📊 Bridge Stats
This week: 5 bridges
All time: 23 bridges
By project (top 5):
HP: 12 (6→, 6←) [tier 1]
BR: 8 (2→, 6←) [tier 1]
DS: 7 (5→, 2←) [tier 1]
By archetype:
🧠 knowledge: 8
📖 narrative: 6
👤 people: 4
By strength:
🟢 active: 9
🟡 potential: 11
🔴 theoretical: 3
Tier 2 bridges: 3 (VN→HP, VN→BR, LW→HP)
```
## Key Behaviors
- **One-line capture response.** Never add commentary about bridge content.
- **Resume immediately.** After capture, pick up prior conversation exactly where it left off.
- **Store verbatim.** No reformulation of user's description.
- **Auto-detect but don't over-think.** If archetype is ambiguous, pick the closest and move on.
- **Weekly nudge, not nag.** Mention reconciliation opportunity only when pattern is clear (≥3 same pair).
- **No GTD writes.** This skill only writes to `thinking/bridges/`. GTD `## 🔗 Ponts Stratégiques` updates are manual during weekly review.
- **Config-driven.** All project aliases come from `$PRAXIS_DIR/config/projects.yaml`. If a project isn't in config, warn and suggest adding it.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · digital-stoic-org/agent-skills | 100 | MIT |
| muchiny/bridge-mcp | 100 | MIT |
| muchiny/bridge-mcp | 100 | MIT |
| Yuvasee/guild | 100 | MIT |
| pantheon-org/tekhne | 100 | MIT |
| msanchezdev/agent-bridge | 100 | MIT |
| ialameh/sift-coder | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 433f3a342f0d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100monitoring-cross-chain-bridges
Monitoruje bezpieczeństwo, płynność i status transakcji mostów między łańcuchami blockchain przy transferach aktywów między sieciami. - 100monitoring-cross-chain-bridges
Monitoruje TVL, wolumen, opłaty i status transakcji mostów międzyłańcuchowych, porównuje trasy i śledzi transakcje mostów. - 100unikit-bridge-route
Zapisuje reguły kierowania pracy przez mosty silnika: który most obsługuje dany rodzaj zadania i który ma być pomijany.