Splits mixed Server/Client Next.js pages into clean boundaries — extracts client logic into `*Client.tsx`, rewrites `page.tsx` as a pure Server Component, flags repeated JSX for componentisation, and detects styling inconsistencies across the codebase. Trigger on: refactor requests, mixed Server/Client files, pages >200 LOC with hooks, duplicated JSX, or any style drift between components.
97
96%
Does it follow best practices?
Impact
98%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Server/Client split refactor structure
Client file naming
100%
100%
use client directive placement
100%
100%
Hooks in client file only
100%
100%
metadata in page.tsx
100%
100%
Metadata import type
100%
100%
page.tsx imports client component
100%
100%
Page default export structure
0%
50%
No placeholders
100%
100%
All hooks and handlers moved
100%
100%
No duplicate definitions
100%
100%
Repeated JSX extraction and naming
Work entry component extracted
100%
100%
Education entry component extracted
100%
100%
No generic numbered names
100%
100%
Inline duplication removed
100%
100%
Data-driven rendering
100%
100%
No placeholders in output
100%
100%
Component props typed
100%
100%
Functionality preserved
100%
100%
No duplicate definitions
100%
100%
Education entries also refactored
100%
100%
Styling consistency drift detection
Hex vs token flag (blue)
100%
100%
Inline style color flag
100%
100%
Mixed shadow flag
100%
100%
Button component bypassed flag
100%
100%
style override conflict flag
100%
100%
File locations specified
100%
100%
Proposed fixes included
100%
100%
Report format
100%
100%
No fixes applied
100%
100%
Color/text inconsistency on h1
100%
100%
58415cb
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.