HR-ERP / rules
Cursor rule1 starsChanged 6 months agoApache-2.0View on GitHub
Always-on HR ERP repo boundaries — bounded contexts, contracts, phase scope
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-ai-governance.mdcCursor rule
- .cursor/rules/agent-architecture.mdcCursor rule
- .cursor/rules/agent-code-health.mdcCursor rule
- .cursor/rules/agent-db-migration-state.mdcCursor rule
- .cursor/rules/agent-developer-advocate.mdcCursor rule
- .cursor/rules/agent-devops-lifecycle.mdcCursor rule
- .cursor/rules/agent-finops.mdcCursor rule
- .cursor/rules/agent-integrations.mdcCursor rule
- .cursor/rules/agent-legal-hr-compliance.mdcCursor rule
- .cursor/rules/agent-mlops.mdcCursor rule
- .cursor/rules/agent-nextjs.mdcCursor rule
- .cursor/rules/agent-packaging-supply-chain.mdcCursor rule
- .cursor/rules/agent-qa.mdcCursor rule
- .cursor/rules/agent-security.mdcCursor rule
- .cursor/rules/orchestrator-hr-erp.mdcCursor rule
- .cursor/rules/site-contract.mdcCursor rule
- .cursor/rules/vercel-jwt-smoke.mdcCursor rule
- llms.txtllms.txt
- hr-contributor-handoffSkill
- hr-data-custodySkill
- hr-devops-lifecycleSkill
- hr-domain-boundariesSkill
- hr-foundation-governanceSkill
- hr-governance-learningSkill
- hr-human-collaborationSkill
- hr-orchestration-lanesSkill
- hr-product-gateSkill
- hr-product-mcp-governanceSkill
- hr-quality-labSkill
- hr-regulated-domainSkill
- hr-swarm-governanceSkill
- site-deliverySkill
- code-reviewSkill
- hr-data-custodySkill
The file
Files
--- description: Always-on HR ERP repo boundaries — bounded contexts, contracts, phase scope alwaysApply: true --- # Repo boundaries (always on) Canonical docs — **do not guess**; Read these paths when touching architecture: - [docs/architecture/bounded-contexts.md](../../docs/architecture/bounded-contexts.md) - [docs/architecture/README.md](../../docs/architecture/README.md) - [contracts/README.md](../../contracts/README.md) - Phase: [specs/alignment/decisions/0001-phase1-scope.md](../../specs/alignment/decisions/0001-phase1-scope.md) ## Non-negotiables - **Payroll never mutates Core HR DB** — events + read APIs only - **Single writer per aggregate** in owning bounded context - **No cross-database FKs** — stable business IDs as plain columns - **Forward-only migrations** on shared branches ## Skills (lazy, tier-gated) Dynamic loading: `~/.cursor/rules/core-dynamic-skills.mdc` → `@skill-router` + `@governance-tier-gate`. Global index: `~/.cursor/skills/README.md`. Domain depth: `@hr-domain-boundaries` (architecture), `@hr-regulated-domain` (T3 pay/AI).
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.

