From raiola
Frontend-control skill for keeping UI work evidence-backed, state-aware, and reuse-oriented.
How this skill is triggered — by the user, by Claude, or both
Slash command
/raiola:raiola-frontend-control-roomThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the job is **to move a frontend safely without losing browser proof, state coverage, or primitive discipline**.
Use this skill when the job is to move a frontend safely without losing browser proof, state coverage, or primitive discipline.
rai frontend-control --json.rai state-atlas, rai ui-review, rai component-map, or rai responsive-matrix based on the top signal.rai codex operator --goal "..." --json when the next frontend wave should run in the native Codex layer.npx claudepluginhub aydoganberk/raiola --plugin raiolaImplements and reviews frontend UI including routing, state management, API integration, responsive layout, accessibility, and browser behavior within existing design systems.
Maps frontend component tree, routing, state management, build config; assesses bundle size, deps, freshness, tests, TypeScript strictness. Use for 'understand this frontend' or 'UI built with'.
Frontend reconnaissance — map the component tree, routing, state management, build config, and assess quality. Use when asked to "understand this frontend", "frontend assessment", or "what's the UI built with".