agentleFS
renanflustosarenanflustosa/octo-cluster/.cursor/rules/00-consumer-boundary.mdc

octo-cluster / rules

Cursor rule3 starsChanged 23 days agoMITView on GitHub

Master rule — consumer identifiers are secrets; every git change in octo-cluster must pass this gate

The file

We split this 00-consumer-boundary.mdc into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before staging, committing, pushing, or opening a PR in this repository:

    line 16
  2. Distinctive:

    Stop: if the audit fails — fix violations before proceeding.

    line 21
  3. Distinctive:

    Add real client, product, repo, vault, or workspace names to tracked source.

    line 29
  4. Very specific:

    Commit until boundary-audit passes on staged changes.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 6,873 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
00-consumer-boundary.mdc
---
description: Master rule — consumer identifiers are secrets; every git change in octo-cluster must pass this gate
alwaysApply: true
---

# Master rule — consumer boundary (public framework)

Consumer identifiers are treated as secrets.

Any consumer-specific name, repository name, workspace name, project name, product name, company name, acronym, codename, or internal reference must be handled with the same severity as a credential leak.

Public repositories must never store them.

## Applies to every git change in octo-cluster

Before staging, committing, pushing, or opening a PR in this repository:

1. **Generalize** consumer-specific names in tracked paths and file contents — or remove them.
2. **Relocate** consumer context to a gitignored local overlay or a separate consumer workspace — never the public tree.
3. **Run** `.\scripts\boundary-audit.ps1 -Staged` before commit; full `.\scripts\boundary-audit.ps1` before push. Configure patterns in `boundary-patterns.local.yaml` (see `boundary-patterns.example.yaml`).
4. **Stop** if the audit fails — fix violations before proceeding. Do not bypass hooks, CI, or this rule.

## In scope

Filenames, folder names, markdown, yaml, json, prompts, scripts, commit messages, PR titles and bodies, and comments in tracked files.

## Do not

- Add real client, product, repo, vault, or workspace names to tracked source.
- Copy private overlay paths or consumer vocabulary into public docs, examples, or tests.
- Commit until `boundary-audit` passes on staged changes.

## Reference

`scripts/boundary-audit.ps1` · `.githooks/pre-commit` · `.githooks/pre-push`

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.