Project Bindings

Use when authoring or changing a repository's project-specific bindings such as module ownership, workspace roots, database locations, gate keys, namespaces, palettes, registry contracts, or release values; keep facts in one authoritative declaration.

9 stars 3 forksDatabases

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sandbaseai/workbuddy-skill --skill project-bindings
Manual install
git clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/project-bindings ~/.claude/skills/project-bindings

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Project Bindings

Use this skill when a repository needs to declare project-specific values that generic Skills and standards consume. A binding is a value that two repositories could change while both still follow the same rule: a package owner, workspace root, database/test directory, closed namespace, palette asset, release set, or registry identifier. Keep one authoritative bindings document at the repository root or the location named by governance.

## Separate values from rules

Bindings declare values; they do not create obligations. Put “the approved compute module is X” in bindings, but keep “only the approved compute module may do Y” in the standard that owns that rule. Do not put architecture decisions, workflow behavior, explanatory doctrine, or current runtime behavior into bindings. Code is the authority for current behavior; architecture documents own boundaries and contracts.

Never store secrets, tokens, passwords, private endpoints, environment credentials, or ephemeral deployment values as bindings. Use safe references or environment-owned configuration and document only the interface needed by consumers.

## Discover consumers before editing
Read the full skill on GitHub

Details

Skill name
project-bindings
Path
skills/project-bindings/SKILL.md
License
MIT
Repo updated
8 September 2026

FAQ

What does the Project Bindings skill do?

Use when authoring or changing a repository's project-specific bindings such as module ownership, workspace roots, database locations, gate keys, namespaces, palettes, registry contracts, or release values; keep facts in one authoritative declaration.

How do I install the Project Bindings skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill project-bindings. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Project Bindings popular?

It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all databases skills, or write your own with the skills generator.