We’re thrilled to share SPA template support in the Power Pages plugin for GitHub Copilot CLI and Claude Code. The /create-site skill can now create your site from a ready-made single-page application (SPA) template, instead of generating every page and component from scratch.
We’re thrilled to share SPA template support in the Power Pages plugin for GitHub Copilot CLI and Claude Code. The /create-site skill can now create your site from a ready-made single-page application (SPA) template, instead of generating every page and component from scratch.
In context
- Topic: Desarrollo con IA — Copilotos y agentes en el ciclo de desarrollo de software.
- Source: Microsoft Power Platform
- Published: 13/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
AI applied to development moved the bottleneck. Writing code stopped being the slow part; now the slow part is reviewing, understanding and maintaining what was written. Any team adopting these tools without adjusting review gets faster in week one and slower by month three.
I distinguish between accelerating an experienced developer and accelerating someone just starting. In the first case the tool multiplies judgement; in the second it multiplies the lack of it. Adoption policy has to acknowledge that difference or the codebase fills with plausible, wrong code.
What usually goes wrong
Where I see most stumbles is in the conversation with people. The tool gets announced as a productivity improvement without saying what is expected of each person, and everyone fills the silence with their own fear. Adoption does not stall on the technology, it stalls on what was left unsaid.
What to watch
- What happens to code review: if the assistant produces more, somebody has to read more.
- What happens to tests — generating code without generating tests only moves the problem forward.
- Where the source code travels when the assistant is used, and what the contract says about it.
How I read this entry
What I would ask to measure is not lines or accepted suggestions, but defects reaching production and review time per change. If those two go down, the tool works. If they go up while speed goes up, debt is being accumulated and it gets paid in incidents.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
