Menu
Verify any UI change end-to-end before declaring it done.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Choose the simplest loop primitive (turn-based, /goal, /loop, /schedule) and make success criteria explicit and verifiable.
Plan and roll out Claude Code via a self-hosted apps gateway, using centralized SSO login, managed settings enforcement, and per-user usage attribution when running on Amazon Bedrock or Google Cloud.
Decide whether to run Claude via Microsoft Foundry hosted on Azure or hosted on Anthropic, based on Azure-native requirements vs. needing full API feature/model availability.
A practical playbook for designing and operating effective human–agent teams: working in public, defining roles and tools, setting a north star, and building trust through verification and gradual autonomy.
Configure and roll out workspace-owned “agent identities” for team-wide AI agents with least privilege, strong boundaries, and reliable auditing.
Roll out Claude Desktop across an organization with cloud-hosted inference and enterprise controls, based on a provider-backed deployment (AWS, Google Cloud, or Microsoft Foundry).
| name | verify-frontend-change |
| description | Verify any UI change end-to-end before declaring it done. |
Never report a UI change as complete based on a successful edit alone. Verify it the way a human reviewer would:
Start the dev server and open the edited page in the browser.
Interact with the change directly. For a new control (button, input, toggle): click it, confirm the expected state change, and screenshot before/after.
Check the browser console: zero new errors or warnings.
Use the Chrome Devtools MCP, run a performance trace and audit Core Web Vitals.
If any step fails, fix the issue and rerun from step 1 — do not hand back partially verified work.
