Software Engineering · Sitecore · AI
Thoughts on software engineering, product development, and building with AI.
A few days ago I published one agent skill for moving Sitecore content. It has grown into a small library. Here are three new residents - multi-environment authoring, a publish-and-verify diagnostic, and an XM Cloud config review - and the idea that ties them together: a skill encodes experience, not just a workflow.
The official Azure DevOps MCP server only runs inside VS Code, so I built a local reviewer that polls pull requests, verifies its own findings against the source before posting, and handles developer replies without nagging. The team says it is right about 80% of the time - here is how, and why that number is enough to make it useful.
A large data import brought our SitecoreAI environment to a crawl and every full CLI pull died with a 524. The fix was three layers deep: a CLI upgrade, a new serialization flag, and one full restart.
One shared Next.js codebase, multiple brands as separate Vercel projects, each needing its own bulk redirects list - and the one non-obvious rule about where vercel.ts actually runs.
The Package Designer is gone and its replacement is a pair of REST APIs with an eight-step chunk relay. The community shipped the docs and the UI within a day of each other - here is the third interface: an agent skill, so you ask for a content move instead of performing one.
Wire a Sitecore Experience Edge webhook to a Next.js revalidation endpoint on Vercel so a publish refreshes exactly the affected pages in seconds - no full rebuilds, no short timers.
Why publishing a shared datasource on its own never refreshes the pages that use it, why fully automating the fix is harder than it looks, and the SPE 'Revalidate Page / Tree' buttons that bridge the gap.
Four reasonable ways to feed a per-environment secret to a Sitecore PowerShell script - three of which die on XM Cloud - plus the sharp edges (IAR shadowing, a BOM trap, the prod WAF) that each cost real time.
How to securely fetch the logged-in user's identity in a Sitecore Marketplace app to personalize the experience without building a custom authentication layer.
A deep dive into why I migrated my personal blog from WordPress to a Git-backed Next.js 16 architecture hosted on Google Cloud Run.