chain-enforcement

name

chain-enforcement

description

Mandatory agent pipeline enforcement for frontend development. Activates when the user asks to create, build, or implement any React/MUI UI component, form, page, table, dashboard, or interface. Triggers on: (EN) 'create a component', 'build a form', 'create a page', 'add a table', 'implement', 'build', 'fix React', '/chain'; (IT) 'crea un componente', 'crea una pagina', 'aggiungi una tabella', 'implementa', 'costruisci'; (Technical) 'MUI', 'Material UI', 'React', 'DataGrid', 'header', 'form', 'dialog', 'dashboard', 'wizard', 'stepper', 'carousel', 'sidebar', 'layout'. Also activates when the user provides a multi-component implementation plan or requests any frontend feature development. Use when this capability is needed.

Mandatory Agent Chain Enforcement

Absolute Rule

When this skill is active, it is FORBIDDEN to implement React code directly in the main conversation. EVERY frontend implementation task MUST go through the specialized agent chain using the Task tool.

Input Evaluation

This skill accepts the user's implementation request (via $ARGUMENTS if invoked as /chain-enforcement, or from the conversation context when auto-triggered).

Workflow:

1. Receive the user's request and analyze it
2. Identify discrete components/tasks to implement
3. For each component, execute the full mandatory chain (see below)
4. Report results between phases

If the user provides a multi-component plan (e.g., "Implementa UserTable, UserForm e UserDetail"), decompose it into individual components and process each through the complete chain before moving to the next.

Mandatory Chain Sequence

For every component/task, execute this sequence:

1. frontend-architect   -> Creates the component (design + implementation)
2. frontend-reviewer    -> Code review with numeric score (MANDATORY)
3. frontend-debugger    -> IF score < 80 OR CRITICAL/HIGH issues -> automatic fix
4. frontend-refactorer  -> IF LOC > 150 OR maintainability < 15/25 -> decomposition
5. frontend-reviewer    -> Re-validation after debugger/refactorer (max 2 cycles)