~ / rigs / nevenincs / vaultspec-core

nevenincs/vaultspec-core

Decision-driven harness for coding agents, and humans.

↗ GitHub ★ 2 MIT updated 1mo ago project Claude Code
field: unknown workflow: Planning & specsTesting & TDDDocsPR / code reviewResearch runs claude in CI
share on X
ARCHETYPE
Skill Collector
Ten-plus skills loaded on demand. A procedural-knowledge library.
CONTEXT TAX · EVERY TURN
~595 tokens
Featherweight · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

$ git clone --depth 1 https://github.com/nevenincs/vaultspec-core

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-adr .claude/skills/vaultspec-adr
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-code-research .claude/skills/vaultspec-code-research
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-code-review .claude/skills/vaultspec-code-review
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-curate .claude/skills/vaultspec-curate
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-documentation .claude/skills/vaultspec-documentation
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-execute .claude/skills/vaultspec-execute
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-projectmanager .claude/skills/vaultspec-projectmanager
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-rag-discovery .claude/skills/vaultspec-rag-discovery
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-research .claude/skills/vaultspec-research
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-team .claude/skills/vaultspec-team
$ npx degit nevenincs/vaultspec-core/.vaultspec/skills/vaultspec-write .claude/skills/vaultspec-write

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (11)

Similar rigs

copied ✓