Bootstrapping an Enterprise Repo with Engineering Standards

Starting a new enterprise engagement is more than scaffolding code — agents and humans need shared delivery rules from commit one. This week I wired a new delivery repo with ThreeWill Engineering Standards as a git submodule and product-specific agent context before the first feature branch landed.

What happened

• Added threewill-engineering-standards as a git submodule at .cursor/rules/ so team non-negotiables, MCP docs, and SPFx patterns travel with the repo
• The standards package is the result of a long partnership and rounds of planning with Cursor — so every developer, whether working locally or in the cloud, can trust that agents follow the same rules
• The approach predates Cursor Cloud agents, but it remains a strong way to distribute consistent agentic behavior; it is still a work in progress, and the team is happy with how far it has come
• Wrote product-specific AGENTS.md with submodule hygiene: detect missing standards, init/sync commands, and a light cadence for bumping the pinned SHA via PR
• Documented delivery conventions in docs/delivery.md: branch + PR discipline, Azure DevOps Boards ↔ GitHub PR linkage (AB#<id>), GitHub Actions CI/CD posture, and Azure DevOps MCP setup for Cursor — without publishing client org or cutover details
• Added Cursor Cloud-specific instructions so cloud agents follow the same submodule and delivery rules as local sessions
• Adoption across the practice keeps improving — especially on SPFx web parts, where the standards enforce fewer rules but bring a consistent look-and-feel and reusable React components
• Recent advancements clarify sophistication levels: Enterprise solutions carry a fuller requirements set than smaller/atomic solutions, so agents and humans get the right bar for the work
• The same submodule pattern shows up across multiple active delivery repos (enterprise engagements and internal SPFx products), not only this kickoff