1"use strict";(self.webpackChunkhomol_works=self.webpackChunkhomol_works||[]).push([[1690],{43055(e,t,n){n.r(t),n.d(t,{default:()=>l,metadata:()=>r});var r=n(76174),s=n(74848),i=n(28453);const a={authorsImageUrls:[void 0]};function o(e){const t={code:"code",h2:"h2",li:"li",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(t.p,{children:["Starting a new enterprise engagement is more than scaffolding code \u2014 agents and humans need shared delivery rules from commit one. This week I wired a new delivery repo with ",(0,s.jsx)(t.strong,{children:"ThreeWill Engineering Standards"})," as a git submodule and product-specific agent context before the first feature branch landed."]}),"\n",(0,s.jsx)(t.h2,{id:"what-happened",children:"What happened"}),"\n",(0,s.jsxs)(t.ul,{children:["\n",(0,s.jsxs)(t.li,{children:["Added ",(0,s.jsx)(t.code,{children:"threewill-engineering-standards"})," as a git submodule at ",(0,s.jsx)(t.code,{children:".cursor/rules/"})," so team non-negotiables, MCP docs, and SPFx patterns travel with the repo"]}),"\n",(0,s.jsx)(t.li,{children:"The standards package is the result of a long partnership and rounds of planning with Cursor \u2014 so every developer, whether working locally or in the cloud, can trust that agents follow the same rules"}),"\n",(0,s.jsx)(t.li,{children:"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"}),"\n",(0,s.jsxs)(t.li,{children:["Wrote product-specific ",(0,s.jsx)(t.code,{children:"AGENTS.md"})," with submodule hygiene: detect missing standards, init/sync commands, and a light cadence for bumping the pinned SHA via PR"]}),"\n",(0,s.jsxs)(t.li,{children:["Documented delivery conventions in ",(0,s.jsx)(t.code,{children:"docs/delivery.md"}),": branch + PR discipline, Azure DevOps Boards \u2194 GitHub PR linkage (",(0,s.jsx)(t.code,{children:"AB#<id>"}),"), GitHub Actions CI/CD posture, and Azure DevOps MCP setup for Cursor \u2014 without publishing client org or cutover details"]}),"\n",(0,s.jsx)(t.li,{children:"Added Cursor Cloud-specific instructions so cloud agents follow the same submodule and delivery rules as local sessions"}),"\n",(0,s.jsx)(t.li,{children:"Adoption across the practice keeps improving \u2014 especially on SPFx web parts, where the standards enforce fewer rules but bring a consistent look-and-feel and reusable React components"}),"\n",(0,s.jsxs)(t.li,{children:["Recent advancements clarify sophistication levels: ",(0,s.jsx)(t.strong,{children:"Enterprise"})," solutions carry a fuller requirements set than smaller/atomic solutions, so agents and humans get the right bar for the work"]}),"\n",(0,s.jsx)(t.li,{children:"The same submodule pattern shows up across multiple active delivery repos (enterprise engagements and internal SPFx products), not only this kickoff"}),"\n"]})]})}function l(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(o,{...e})}):o(e)}n.d(t,["assets",0,a,"contentTitle",0,void 0,"frontMatter",0,{id:"2026-07-27-engineering-standards-submodule-bootstrap",title:"Bootstrapping an Enterprise Repo with Engineering Standards",author:"Mike Homol",author_title:"Principal Consultant @ ThreeWill",author_url:"https://github.com/mhomol",author_image_url:"https://avatars2.githubusercontent.com/u/680566?s=460&v=4",tags:["ai","cursor","threewill","enterprise"]},"toc",0,[{value:"What happened",id:"what-happened",level:2}]])},28453(e,t,n){n.d(t,{R:()=>a,x:()=>o});var r=n(96540);const s={},i=r.createContext(s);function a(e){const t=r.useContext(i);return r.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:a(e.components),r.createElement(i.Provider,{value:t},e.children)}},76174(e){e.exports=JSON.parse('{"permalink":"/blog/2026/07/27/engineering-standards-submodule-bootstrap","source":"@site/blog/2026-07-27-engineering-standards-submodule-bootstrap.md","title":"Bootstrapping an Enterprise Repo with Engineering Standards","description":"Starting a new enterprise engagement is more than scaffolding code \u2014 agents and humans need shared delivery rules from commit one. This week I wired a
1new delivery repo with ThreeWill Engineering Standards as a git submodule and product-specific agent context before the first feature branch landed.","date":"2026-07-27T00:00:00.000Z","tags":[{"inline":true,"label":"ai","permalink":"/blog/tags/ai"},{"inline":true,"label":"cursor","permalink":"/blog/tags/cursor"},{"inline":true,"label":"threewill","permalink":"/blog/tags/threewill"},{"inline":true,"label":"enterprise","permalink":"/blog/tags/enterprise"}],"readingTime":1.48,"hasTruncateMarker":false,"authors":[{"name":"Mike Homol","title":"Principal Consultant @ ThreeWill","url":"https://github.com/mhomol","imageURL":"https://avatars2.githubusercontent.com/u/680566?s=460&v=4","key":null,"page":null}],"frontMatter":{"id":"2026-07-27-engineering-standards-submodule-bootstrap","title":"Bootstrapping an Enterprise Repo with Engineering Standards","author":"Mike Homol","author_title":"Principal Consultant @ ThreeWill","author_url":"https://github.com/mhomol","author_image_url":"https://avatars2.githubusercontent.com/u/680566?s=460&v=4","tags":["ai","cursor","threewill","enterprise"]},"unlisted":false,"prevItem":{"title":"Weekly AI Builds - August 3, 2026","permalink":"/blog/2026/08/03/weekly-ai-builds"},"nextItem":{"title":"Weekly AI Builds - July 27, 2026","permalink":"/blog/2026/07/27/weekly-ai-builds"}}')}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.