bryan/dotfiles
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity

Build a Claude skill for opting repos into the vault pattern #18

New issue
Open
opened 2026-05-28 05:41:08 +00:00 by bryan · 0 comments
bryan commented 2026-05-28 05:41:08 +00:00
Owner
Copy link

Build a Claude skill (working name: wire-vault) that automates wiring a
repo (or a multi-repo project domain) into the personal notes vault pattern
documented in docs/superpowers/specs/2026-05-27-vault-pattern-design.md.

Steps the skill should automate:

  1. Accept a repo path (default: current working directory). For multi-repo
    project domains, accept multiple paths.
  2. Derive a vault name (default: basename of the umbrella or repo).
  3. Create ~/code/notes/<name>/ if it doesn't exist, with a seed INDEX.md
    following the template in the design doc (D5).
  4. Symlink <path>/vault → ~/code/notes/<name>/ at each provided path.
  5. Add the "Notes vault" pointer block (D4) to each location's AGENTS.md.
    Create AGENTS.md with a CLAUDE.md → AGENTS.md symlink alongside if missing.
    Respect each repo's local gitignore tracking stance (commit only if
    !AGENTS.md is negated in the local .gitignore).
  6. Commit + push the new vault to the notes repo with message <name>: init vault.

Idempotency requirements:

  • Re-running on an already-wired repo must be a no-op (or skip with a clear "already wired" message).
  • Detect cases where the symlink target exists but the source doesn't, or vice versa, and report rather than silently fix.

Design reference: docs/superpowers/specs/2026-05-27-vault-pattern-design.md.
Related skill: vault-pkm — this skill complements that one; vault-pkm
governs how to use a wired-up vault, wire-vault creates one.

Build a Claude skill (working name: `wire-vault`) that automates wiring a repo (or a multi-repo project domain) into the personal notes vault pattern documented in `docs/superpowers/specs/2026-05-27-vault-pattern-design.md`. Steps the skill should automate: 1. Accept a repo path (default: current working directory). For multi-repo project domains, accept multiple paths. 2. Derive a vault name (default: basename of the umbrella or repo). 3. Create `~/code/notes/<name>/` if it doesn't exist, with a seed `INDEX.md` following the template in the design doc (D5). 4. Symlink `<path>/vault → ~/code/notes/<name>/` at each provided path. 5. Add the "Notes vault" pointer block (D4) to each location's `AGENTS.md`. Create `AGENTS.md` with a `CLAUDE.md → AGENTS.md` symlink alongside if missing. Respect each repo's local gitignore tracking stance (commit only if `!AGENTS.md` is negated in the local .gitignore). 6. Commit + push the new vault to the notes repo with message `<name>: init vault`. Idempotency requirements: - Re-running on an already-wired repo must be a no-op (or skip with a clear "already wired" message). - Detect cases where the symlink target exists but the source doesn't, or vice versa, and report rather than silently fix. Design reference: `docs/superpowers/specs/2026-05-27-vault-pattern-design.md`. Related skill: `vault-pkm` — this skill complements that one; `vault-pkm` governs *how to use* a wired-up vault, `wire-vault` *creates* one.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
agents/move-opencode-skills-to-dot-agents
add-sgg-staging-fuzz-script
code-fn-auto-discover-org-containers-retry
tmux-claude-status-warnings
tmux-osc8-hyperlink-passthrough
code-fn-auto-discover-org-containers
tmux-claude-and-openrouter-widgets
claude/tender-jepsen-a86af3
feat/opencode-ollama-config
feat/syncthing-notes-sync
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bryan/dotfiles#18
No description provided.