oblt-aw / rules
Cursor rule2 starsChanged 30 days agoApache-2.0View on GitHub
Checklist when adding a new org key under config/<org-key>/
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/ci-precommit-before-push.mdcCursor rule
- .cursor/rules/fail-closed-e2e-gates.mdcCursor rule
- .cursor/rules/protected-oblt-aw-workflow.mdcCursor rule
- copilot-reviewSkill
- code-reviewSkill
The file
We split this new-org-key-checklist.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 14
When adding or scaffolding a new config/<org-key>/ (or <org-key>-aw-* workflows), follow AGENTS.md → Adding a new org key and …
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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.
Files
--- description: Checklist when adding a new org key under config/<org-key>/ globs: - config/*/workflow-registry.json - config/*/active-repositories.json - .github/remote-workflow-template/**/* - scripts/validate_aw_workflow_prelude.py - tests/unit/test_validate_aw_workflow_prelude.py alwaysApply: false --- # New org key — do not skip prelude route coverage When adding or scaffolding a new `config/<org-key>/` (or `<org-key>-aw-*` workflows), follow **`AGENTS.md` → Adding a new org key** and [docs/architecture/multi-org-agentic-workflows.md](../../docs/architecture/multi-org-agentic-workflows.md) §10. ## Non-negotiable for the prelude validator - `scripts/validate_aw_workflow_prelude.py` must **derive** route prefixes from `discover_org_keys_sorted(config)` — never reintroduce a hard-coded `(?:obs|docs|…)` org list. - `tests/unit/test_validate_aw_workflow_prelude.py` must keep **parametrized** `shared-proceed` cases over discovered org keys so a new org is covered automatically once its config dir exists. - Event orchestrators (`*-aw-event-*`) stay excluded from subject discovery; dashboard-audit-only scaffolds without prelude are OK until routes exist. ## Minimal validation ```bash python scripts/validate_aw_workflow_prelude.py pytest tests/unit/test_validate_aw_workflow_prelude.py pre-commit run --files <touched-paths> ```
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
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.