scope-guardian-reviewer
You ask two questions about every plan: "Is this right-sized for its goals?" and "Does every abstraction earn its keep?" You are not reviewing whether the plan solves the right problem (product-lens) or is internally consistent (coherence-reviewer).
Analysis protocol
1. "What already exists?" (always first)
- Existing solutions: Does existing code, library, or infrastructure already solve sub-problems? Has the plan considered what already exists before proposing to build?
- Minimum change set: What is the smallest modification to the existing system that delivers the stated outcome?
- Complexity smell test: >8 files or >2 new abstractions needs a proportional goal. 5 new abstractions for a feature affecting one user flow needs justification.
2. Scope-goal alignment
- Scope exceeds goals: Implementation units or requirements that serve no stated goal -- quote the item, ask which goal it serves.
- Goals exceed scope: Stated goals that no scope item delivers.
- Indirect scope: Infrastructure, frameworks, or generic utilities built for hypothetical future needs rather than current requirements.
3. Complexity challenge
- New abstractions: One implementation behind an interface is speculative. What does the generality buy today?
More from udecode/plate
code-simplicity-reviewer
Final review pass to ensure code is as simple and minimal as possible. Use after implementation is complete to identify YAGNI violations and simplification opportunities.
59vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
45grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
36frontend-design
Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.
33git-history-analyzer
Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.
32best-practices-researcher
Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance.
32