hr-domain-boundaries
Skill1 starsChanged 6 months agoApache-2.0View on GitHub
HR ERP bounded contexts: Postgres-per-context, Kafka outbox, Payroll never mutates Core HR DB, REST/gRPC contracts. Use for schemas, services, migrations, cross-context APIs, docker topology, or module proposals in this repo.
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/repo-boundaries.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-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
HR domain boundaries
Use this skill when
- Architecture Tasks touching
prisma/,services/,contracts/,proto/ - New modules or cross-context integration
- Innovation/R&D parity when infra or async boundaries change
Do not use this skill when
- Copy/CSS-only or single-table field rename with no boundary impact
- Regulated pay math (use
hr-regulated-domain)
Instructions
- Read references/boundary-checklist.md.
- Fill
specs/templates/architecture-spec.mdfor the feature. - Link module proposal per
docs/architecture/module-proposal-template.md. - Innovation parity: mark N/A with one line when no stack/extraction change.
Resources
- references/boundary-checklist.md
- docs/architecture/bounded-contexts.md
Limitations
- Phase 1 may use single app DB with logical contexts — follow phase ADR
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.

