navigation

Name: navigation
Author: pariyar07

18stars2forks

How to install navigation?

pariyar07/ariadne/navigation

$npx -y skills add pariyar07/ariadne --skill navigation

Installs into the current project.

Summary

Design or modify Markdown knowledge-vault navigation: folder hubs, agent navigation, routing matrices, workstream graphs, optional Bases/view layers, templates, health-check rules, and long-term traversability.

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Navigation
2
3	Use this skill when changing the durable structure of a Markdown knowledge vault.
4
5	## Core Principle
6
7	Optimize for reliable human and agent traversal, not for a beautiful graph view.
8
9	Markdown notes remain the source of truth. Bases, canvases, dashboards, and reports are view layers over the vault.
10
11	## Start
12
13	1. Read root instructions and every applicable ancestor scope instruction through the target.
14	2. Read relevant indexes, agent navigation, navigation standards, routing matrices, and knowledge-processing architecture.
15	3. In a multi-scope vault, require a current-turn named or confirmed target before writing.
16	4. State an explicit `allowed_write_set`. Name every parent hub, routing matrix, root Base formula, or cross-scope file separately; minimal wiring is not implicit authorization.
17
18	## Navigation Layers
19
20	Maintain these layers when useful:
21
22	1. Global entry: `00 Index.md` and agent instructions.
23	2. Agent entry: `Agent/00 Agent Navigation.md`.
24	3. Folder hubs: `00 ... Index.md` notes inside durable folders.
25	4. Thread hubs: synthesis or debate notes for recurring arguments.
26	5. View layer: `Bases/00 Bases Index.md`, `.base` files, canvases, dashboards.
27	6. Note-level links: meaningful links to sources, concepts, entities, relationships, questions, and decisions.
28
29	## Workstream Graph Protocol
30
31	Do not pre-create graph categories because they might be useful later.
32
33	Create or promote a workstream graph only when a recurring use case needs its own traversal path. Examples can include evidence trails, customer discovery, engineering decisions, GTM experiments, fundraising, life systems, or any other durable domain.
34
35	When promoting a workstream:
36
37	1. Choose or create the folder.
38	2. Create a `00 ... Index.md` hub.
39	3. Add a routing row to `Agent/Task Routing Matrix.md`.
40	4. Link from `Agent/00 Agent Navigation.md` if it becomes a primary route.
41	5. Add templates only if the structure repeats.
42	6. Add a Base only if metadata inspection helps.
43	7. Link the Base from `Bases/00 Bases Index.md`.
44	8. Update `00 Index.md` only if strategically important.
45	9. Add health-check coverage if the workstream creates recurring maintenance.
46
47	## Recursive Scope Protocol
48
49	A navigation scope can exist at any depth: the vault root, a top-level workstream, a child workflow, or a deep child project. Promote a child scope only when a recurring durable route needs local traversal; otherwise keep it as a normal folder under the parent scope.
50
51	Topology ownership is strict: `sync_scope_topology.js` owns descriptors, generated files, generated blocks, the scope map and `Bases/Scope Registry.base`, routing checkpoints, redirects, and parent/child topology. Use `ariadne:scope` for any lifecycle or topology change. Non-registry root Base formulas are report-only: they remain user-authored and may be updated outside generated blocks only through a separately confirmed explicit allowed_write_set.
52
53	Navigation may edit only user extension areas outside generated blocks: prose around marker-managed checkpoints, user-authored hub sections, semantic links, and other explicitly confirmed content. Never edit inside generated blocks or reproduce generated wiring elsewhere.
54
55	When improving a child scope's user-authored navigation:
56
57	1. Identify the parent scope and its hub.
58	2. Create or update the child hub, usually `00 ... Index.md`.
59	3. Preserve engine-owned parent/child links and routing checkpoints.
60	4. Add only semantic user-authored links outside generated regions.
61	5. Add a local `AGENTS.md` only for local deltas.
62	6. Add local templates or local Bases only when the repeated workflow justifies them.
63	7. Add health checks for hub links, scope queues, raw-source compilation, and Base coverage.
64
65	Warn when you see:
66
67	- child `AGENTS.md` files repeating parent or root policy instead of local deltas
68	- child local Bases without scope filters
69	- parent hub missing child link
70	- child hub missing parent link
71	- ambiguous cross-scope wikilinks that should point through the nearest useful hub, relationship note, or synthesis
72
73	## Bloat And Drift
74
75	When navigating or restructuring a vault, proactively call out:
76
77	- `00 Index.md` acting like a complete table of contents instead of a strategic map
78	- `Agent/00 Agent Navigation.md` carrying detailed note lists instead of routes
79	- folders with many durable notes but no `00 ... Index.md`
80	- hubs that are too long to scan and need sub-hubs or a Base
81	- recurring workstreams missing from the task-routing matrix
82	- Bases not linked from `Bases/00 Bases Index.md`
83	- raw/inbox/output/question buildup without a compilation route
84	- repeated need for user guidance because global instructions are too generic for a folder
85
86	If the current task is structural, fix the issue dire

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

navigation

18stars2forks

View on GitHub

How to install navigation?

pariyar07/ariadne/navigation

$npx -y skills add pariyar07/ariadne --skill navigation

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Navigation
2
3	Use this skill when changing the durable structure of a Markdown knowledge vault.
4
5	## Core Principle
6
7	Optimize for reliable human and agent traversal, not for a beautiful graph view.
8
9	Markdown notes remain the source of truth. Bases, canvases, dashboards, and reports are view layers over the vault.
10
11	## Start
12
13	1. Read root instructions and every applicable ancestor scope instruction through the target.
14	2. Read relevant indexes, agent navigation, navigation standards, routing matrices, and knowledge-processing architecture.
15	3. In a multi-scope vault, require a current-turn named or confirmed target before writing.
16	4. State an explicit `allowed_write_set`. Name every parent hub, routing matrix, root Base formula, or cross-scope file separately; minimal wiring is not implicit authorization.
17
18	## Navigation Layers
19
20	Maintain these layers when useful:
21
22	1. Global entry: `00 Index.md` and agent instructions.
23	2. Agent entry: `Agent/00 Agent Navigation.md`.
24	3. Folder hubs: `00 ... Index.md` notes inside durable folders.
25	4. Thread hubs: synthesis or debate notes for recurring arguments.
26	5. View layer: `Bases/00 Bases Index.md`, `.base` files, canvases, dashboards.
27	6. Note-level links: meaningful links to sources, concepts, entities, relationships, questions, and decisions.
28
29	## Workstream Graph Protocol
30
31	Do not pre-create graph categories because they might be useful later.
32
33	Create or promote a workstream graph only when a recurring use case needs its own traversal path. Examples can include evidence trails, customer discovery, engineering decisions, GTM experiments, fundraising, life systems, or any other durable domain.
34
35	When promoting a workstream:
36
37	1. Choose or create the folder.
38	2. Create a `00 ... Index.md` hub.
39	3. Add a routing row to `Agent/Task Routing Matrix.md`.
40	4. Link from `Agent/00 Agent Navigation.md` if it becomes a primary route.
41	5. Add templates only if the structure repeats.
42	6. Add a Base only if metadata inspection helps.
43	7. Link the Base from `Bases/00 Bases Index.md`.
44	8. Update `00 Index.md` only if strategically important.
45	9. Add health-check coverage if the workstream creates recurring maintenance.
46
47	## Recursive Scope Protocol
48
49	A navigation scope can exist at any depth: the vault root, a top-level workstream, a child workflow, or a deep child project. Promote a child scope only when a recurring durable route needs local traversal; otherwise keep it as a normal folder under the parent scope.
50
51	Topology ownership is strict: `sync_scope_topology.js` owns descriptors, generated files, generated blocks, the scope map and `Bases/Scope Registry.base`, routing checkpoints, redirects, and parent/child topology. Use `ariadne:scope` for any lifecycle or topology change. Non-registry root Base formulas are report-only: they remain user-authored and may be updated outside generated blocks only through a separately confirmed explicit allowed_write_set.
52
53	Navigation may edit only user extension areas outside generated blocks: prose around marker-managed checkpoints, user-authored hub sections, semantic links, and other explicitly confirmed content. Never edit inside generated blocks or reproduce generated wiring elsewhere.
54
55	When improving a child scope's user-authored navigation:
56
57	1. Identify the parent scope and its hub.
58	2. Create or update the child hub, usually `00 ... Index.md`.
59	3. Preserve engine-owned parent/child links and routing checkpoints.
60	4. Add only semantic user-authored links outside generated regions.
61	5. Add a local `AGENTS.md` only for local deltas.
62	6. Add local templates or local Bases only when the repeated workflow justifies them.
63	7. Add health checks for hub links, scope queues, raw-source compilation, and Base coverage.
64
65	Warn when you see:
66
67	- child `AGENTS.md` files repeating parent or root policy instead of local deltas
68	- child local Bases without scope filters
69	- parent hub missing child link
70	- child hub missing parent link
71	- ambiguous cross-scope wikilinks that should point through the nearest useful hub, relationship note, or synthesis
72
73	## Bloat And Drift
74
75	When navigating or restructuring a vault, proactively call out:
76
77	- `00 Index.md` acting like a complete table of contents instead of a strategic map
78	- `Agent/00 Agent Navigation.md` carrying detailed note lists instead of routes
79	- folders with many durable notes but no `00 ... Index.md`
80	- hubs that are too long to scan and need sub-hubs or a Base
81	- recurring workstreams missing from the task-routing matrix
82	- Bases not linked from `Bases/00 Bases Index.md`
83	- raw/inbox/output/question buildup without a compilation route
84	- repeated need for user guidance because global instructions are too generic for a folder
85
86	If the current task is structural, fix the issue dire

People who liked this also viewed

6 picks

Type