Four gaps in react-design.md's Fluent UI rules — a MUST with no runtime signal, a host the contract never names, a validation step that proves nothing about accessibility, and a missing motion rule — each with a runnable snippet. Pre-PR working notes, not a changelog.
AI-Assisted Development
The 16 Rules Your AI Should Follow Before Writing One Line of Fluent UI
Ask an AI coding agent for a Fluent UI card and it often hands back a hardcoded div with invented colors, because generic React training data has never heard of SharePoint's theme constraints. This post walks through react-design.md's 16-section "Copilot UI Contract," the SPFx Dev Skills rule set that stops that failure before an agent writes a single component.
Making the SPFx Upgrade Playbook Safer: A Roadmap for Rollbacks, Big Jumps, and CI
Post 4 covered upgrade.md as it exists today. This companion post proposes four concrete, testable extensions — an explicit rollback path when a report can't be fully applied, an incremental strategy for multi-major-version jumps, running the existing test suite as part of verification, and machine-readable JSON output for agent-driven diffing — each framed as a future contribution to SharePoint/spfx-dev-skills, not a criticism of it.
The Upgrade Playbook: How AI Agents Should (and Shouldn’t) Touch Your SPFx Version
Scaffolding fails safe — a bad attempt just gets deleted. An upgrade runs against a project that already works, so the cost of getting it wrong is much higher. This post walks the spfx-dev-skills upgrade.md reference end to end: the clean-git-state precondition, version detection via .yo-rc.json, the exact m365 spfx project upgrade commands, applying the report in order without overwriting customizations, and the build-clean bar for calling an upgrade done.
Four Ways We’d Extend SPFx Scaffolding (And the Exact Commands to Test)
Post 2 covered create.md as it exists today. This companion post proposes four concrete, testable extensions — scaffold commands for Library and Adaptive Card Extension, a workflow for adding components to an existing solution, the --sharepoint-version flag for on-premises targets, and a post-scaffold validation/commit step — each framed as a future contribution to SharePoint/spfx-dev-skills, not a criticism of it.
Stop Letting AI Hang on yo @microsoft/sharepoint: Non-Interactive SPFx Scaffolding
Interactive Yeoman prompts are invisible to AI coding agents — they hang, or worse, pick the wrong menu item. This post walks the official spfx-dev-skills create.md reference line by line: environment checks with m365 spfx doctor, the fully flag-based scaffold command for web parts and extensions, dependency install discipline, and toolchain-aware packaging for Heft vs. gulp.