From raiola
Activates Raiola frontend specialization, UI direction, and browser-backed visual verification. Use when workflow is active and the task has explicit frontend, UI, design-system, or browser-verdict needs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/raiola:raiola-frontend-laneThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill keeps frontend work design-system-aware, state-complete, and visually verified instead of treating UI changes as isolated markup edits.
This skill keeps frontend work design-system-aware, state-complete, and visually verified instead of treating UI changes as isolated markup edits. It must start by identifying the real product surface so Raiola does not mistake a mobile app for a landing page or a dashboard for a marketing site.
rai map-frontend and read the detected product surface before generating any frontend artifact.
Discuss mode is proposal_first, offer 2-3 narrow frontend options and get approval before opening the heavier artifact path.rai ui-directionrai ui-specrai state-atlas when state coverage is unclear or high-riskrai ui-plan when sequencing/reuse is non-trivialrai frontend-brief only when the user explicitly wants the full artifact packreferences/accessibility-checklist.md| Rationalization | Reality |
|---|---|
| "The logic changed more than the visuals, so browser proof is optional." | User-visible surfaces still need a visual verdict when UI behavior changes. |
| "I can improvise the look during implementation." | Raiola's frontend artifacts exist so taste and state coverage are explicit before the patch grows. |
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.
Implements UI components and frontend architecture. Breaks down designs into component trees, manages state, integrates with backend APIs, ensures accessibility and responsive behavior.
Builds React/Next.js web frontends: components, pages, design systems, state management, typed API clients. Uses structured phases and engagement modes.