workspace-instructions

Name: workspace-instructions
Author: pariyar07

18stars2forks

How to install workspace-instructions?

pariyar07/ariadne/workspace-instructions

$npx -y skills add pariyar07/ariadne --skill workspace-instructions

Installs into the current project.

Summary

Create or update workspace-level instruction files for code repositories or ordinary project folders, including AGENTS.md, CLAUDE.md, GEMINI.md, local override files, and Ariadne vault-link blocks. Use when a user wants to initialize, repair, or refresh workspace instructions, co

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Workspace Instructions
2
3	Use this skill to make a workspace agent-readable and connect it to Ariadne vault context when useful.
4
5	This skill owns workspace-level instruction files. `ariadne:global-discovery` owns machine-level registry files and global adapter blocks.
6
7	## Core Model
8
9	Workspace instruction files are a bridge:
10
11	```text
12	global agent files -> registered vault discovery -> vault or scope context
13	workspace instruction files -> local workspace rules -> optional vault/scope link
14	```
15
16	Keep the bridge small. Do not copy vault navigation, private absolute paths, or long scope notes into public workspace files.
17
18	## Bounded Discovery
19
20	Inspect only the smallest useful workspace context:
21
22	1. Current directory and parents up to the nearest workspace root.
23	2. Existing `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `WORKSPACE.md`, and local override files in that root.
24	3. `.gitignore`.
25	4. High-signal workspace files such as `README.md`, package or build manifests, test config, and existing docs indexes.
26	5. Git state when relevant: whether the folder is inside a worktree, the repository root, tracked instruction files, ignored local files, and whether remotes suggest the workspace is shared.
27	6. Registered vault metadata only when the user asks to connect the workspace to Ariadne context, repair stale global discovery, or the prompt is ambiguous about which known workspace/vault it refers to.
28
29	Do not scan the whole computer. Do not scan an entire vault or repository to infer intent. Use filenames, manifests, and existing entry files first.
30
31	## Mechanical Signal Check
32
33	When the workspace shape is uncertain, or when repairing existing instruction files, you may run the deterministic checker:
34
35	```bash
36	node scripts/check_workspace.js "/path/to/workspace" --json
37	node scripts/check_workspace.js "/path/to/workspace" --json --vault "/confirmed/path/to/vault"
38	```
39
40	Resolve `scripts/check_workspace.js` relative to this `SKILL.md`. In an Ariadne repository checkout, the same script lives at `skills/workspace-instructions/scripts/check_workspace.js`.
41
42	Use the checker for mechanical signals only: Git/worktree state, tracked or ignored instruction files, local-file `.gitignore` coverage, private-path signals, instruction line counts, high line-count files, duplicated vault navigation, adapter duplication, copied global-discovery blocks, malformed, duplicate, legacy, or foreign marker blocks, stable scope identity and canonical-path checks inside workspace-vault-link markers, `WORKSPACE.md` references, fixed-depth child directories, child Git repos, exact child-name mentions by file, root Git plus child Git repo topology, Codex `AGENTS.override.md` bodies that have drifted out of sync with `AGENTS.md` (`codexOverrideOutOfSyncFiles`), Hermes `.hermes.md` / `HERMES.md` override signals, shared instruction files that exceed the ~150-line open-standard length (`oversizedForStandardFiles`), and a canonical `AGENTS.md` that carries no command guidance (`agentsMissingCommandGuidance`).
43
44	Pass `--vault` only after the user has confirmed the intended vault. The checker uses the shared scope-topology inventory and proves a unique valid mapping before making a canonical claim. Duplicate ID declarations, invalid or model-excluded descriptors, ambiguous roots/topology, case-fold or canonical-path collisions, escaping realpaths, and multiply linked descriptor files produce `ambiguousScopeIdFiles`, never current or stale. Without `--vault`, a complete identity is reported in `unverifiedScopeIdentityFiles`; it is never called current, stale, or unknown. Programmatic callers use `checkWorkspace(workspace, { vaultRoot })` under the same confirmation boundary.
45
46	Do not let checker output replace judgment. This skill decides whether to ask a question, preserve workspace-specific rules, split shared/local content, or perform conservative cleanup.
47
48	## Questions
49
50	Ask adaptively when missing information changes the files to write.
51
52	Useful questions:
53
54	- Which workspace root should receive these files?
55	- Is this workspace shared through Git, local-only on this machine, or should it have both shared and local/private instruction files?
56	- Which runtimes should be supported: Codex, Claude Code, Gemini CLI, or another adapter?
57	- Should the vault connection be public-safe in tracked files, private in local ignored files, or both?
58	- Which registered vault or scope should this workspace link to?
59	- Should existing instruction files be updated

People who liked this also viewed

6 picks

Type

workspace-instructions

18stars2forks

View on GitHub

How to install workspace-instructions?

pariyar07/ariadne/workspace-instructions

$npx -y skills add pariyar07/ariadne --skill workspace-instructions

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Ariadne Workspace Instructions
2
3	Use this skill to make a workspace agent-readable and connect it to Ariadne vault context when useful.
4
5	This skill owns workspace-level instruction files. `ariadne:global-discovery` owns machine-level registry files and global adapter blocks.
6
7	## Core Model
8
9	Workspace instruction files are a bridge:
10
11	```text
12	global agent files -> registered vault discovery -> vault or scope context
13	workspace instruction files -> local workspace rules -> optional vault/scope link
14	```
15
16	Keep the bridge small. Do not copy vault navigation, private absolute paths, or long scope notes into public workspace files.
17
18	## Bounded Discovery
19
20	Inspect only the smallest useful workspace context:
21
22	1. Current directory and parents up to the nearest workspace root.
23	2. Existing `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `WORKSPACE.md`, and local override files in that root.
24	3. `.gitignore`.
25	4. High-signal workspace files such as `README.md`, package or build manifests, test config, and existing docs indexes.
26	5. Git state when relevant: whether the folder is inside a worktree, the repository root, tracked instruction files, ignored local files, and whether remotes suggest the workspace is shared.
27	6. Registered vault metadata only when the user asks to connect the workspace to Ariadne context, repair stale global discovery, or the prompt is ambiguous about which known workspace/vault it refers to.
28
29	Do not scan the whole computer. Do not scan an entire vault or repository to infer intent. Use filenames, manifests, and existing entry files first.
30
31	## Mechanical Signal Check
32
33	When the workspace shape is uncertain, or when repairing existing instruction files, you may run the deterministic checker:
34
35	```bash
36	node scripts/check_workspace.js "/path/to/workspace" --json
37	node scripts/check_workspace.js "/path/to/workspace" --json --vault "/confirmed/path/to/vault"
38	```
39
40	Resolve `scripts/check_workspace.js` relative to this `SKILL.md`. In an Ariadne repository checkout, the same script lives at `skills/workspace-instructions/scripts/check_workspace.js`.
41
42	Use the checker for mechanical signals only: Git/worktree state, tracked or ignored instruction files, local-file `.gitignore` coverage, private-path signals, instruction line counts, high line-count files, duplicated vault navigation, adapter duplication, copied global-discovery blocks, malformed, duplicate, legacy, or foreign marker blocks, stable scope identity and canonical-path checks inside workspace-vault-link markers, `WORKSPACE.md` references, fixed-depth child directories, child Git repos, exact child-name mentions by file, root Git plus child Git repo topology, Codex `AGENTS.override.md` bodies that have drifted out of sync with `AGENTS.md` (`codexOverrideOutOfSyncFiles`), Hermes `.hermes.md` / `HERMES.md` override signals, shared instruction files that exceed the ~150-line open-standard length (`oversizedForStandardFiles`), and a canonical `AGENTS.md` that carries no command guidance (`agentsMissingCommandGuidance`).
43
44	Pass `--vault` only after the user has confirmed the intended vault. The checker uses the shared scope-topology inventory and proves a unique valid mapping before making a canonical claim. Duplicate ID declarations, invalid or model-excluded descriptors, ambiguous roots/topology, case-fold or canonical-path collisions, escaping realpaths, and multiply linked descriptor files produce `ambiguousScopeIdFiles`, never current or stale. Without `--vault`, a complete identity is reported in `unverifiedScopeIdentityFiles`; it is never called current, stale, or unknown. Programmatic callers use `checkWorkspace(workspace, { vaultRoot })` under the same confirmation boundary.
45
46	Do not let checker output replace judgment. This skill decides whether to ask a question, preserve workspace-specific rules, split shared/local content, or perform conservative cleanup.
47
48	## Questions
49
50	Ask adaptively when missing information changes the files to write.
51
52	Useful questions:
53
54	- Which workspace root should receive these files?
55	- Is this workspace shared through Git, local-only on this machine, or should it have both shared and local/private instruction files?
56	- Which runtimes should be supported: Codex, Claude Code, Gemini CLI, or another adapter?
57	- Should the vault connection be public-safe in tracked files, private in local ignored files, or both?
58	- Which registered vault or scope should this workspace link to?
59	- Should existing instruction files be updated

People who liked this also viewed

6 picks

Type