ruleslisted

Per-repo credo special rules (project-local grants) that live in the target repo's `.credo/RULES.md` and travel with the repo. Load and honor these at the start of every session and inside every subagent, so a project can widen credo's autonomy for itself - for example "in this debug-only repo, restarting local services is always allowed without asking". Use whenever a session starts (read the rules), whenever the user asks to set, change, add, or remove a per-repo credo rule ("can we set a credo rule here that ...", "for this repo, always ...", "make it a project rule that ..."), and whenever you delegate to a subagent (pass the rules along). This is credo's per-repo policy layer, independent of dogma. It can only WIDEN latitude, never lower the safety floor.
Marcel-Bich/marcel-bich-claude-marketplace · ★ 13 · AI & Automation · score 80

Install: claude install-skill Marcel-Bich/marcel-bich-claude-marketplace

# rules - per-repo credo special rules A project can carry its own credo **special rules** in `<target>/.credo/RULES.md`: a free-form Markdown file of project-local grants that widen credo's autonomy for that one repo. Example: a debug-only repo declaring that restarting local services is always fine without asking. These rules are credo-native and independent of dogma; they travel with the repo (the file is versioned by default). ## Resolve the file via the project layer (never cwd) RULES.md lives in the RESOLVED target `.credo/`, not necessarily the cwd. Resolve it with the shared project-layer resolver so it also works when you start from a launch hub: ``` "${CLAUDE_PLUGIN_ROOT}/scripts/credo-config.sh" rules ``` - Prints `<target>/.credo/RULES.md` plus `(present)` / `(missing)`. - Exit 4 = no target resolved (cwd is a hub or has no credo project). Then the rules cannot be located here - the user pins the target with `/credo:project <path>` (or sets `CREDO_DIR`), and you retry. Do NOT fall back to reading a cwd-relative file. When it prints a `(present)` path, Read that file. Resolution precedence is the same as for config and items: `CREDO_DIR` env > session pin (`/credo:project`) > repo-root `.credo/`. ## Config values live in the cascade, not the repo folder All config and personal values (ntfy topic/server, sleep, identities, viewports) live in the credo config cascade (builtin < global < profile < project). Resolve them ONLY via `credo-config.sh get <dotte