What problem does it solve? React and TypeScript UI codebases often accumulate deeply nested conditionals, wall-style if/else chains, overloaded function signatures, and JSX templates stuffed with business logic, making code hard to read and review. This Skill provides concrete, judgment-based style rules for writing and reviewing web UI code so teams stay consistent beyond what a formatter can enforce. ## Core Features & Use Cases - Control flow rules: Early returns for errors and edge cases, removal of redundant else branches, and named booleans for conditions with three or more operands. - Function and component design: Options objects when parameters exceed roughly four, components limited to presentation concerns, and a defined declaration order within files. - JSX and review support: Guidance on lifting complex derived values out of templates, readonly props, why-focused comments, plus a parallel audit mode using up to five subagents for large codebases. - Use Case: While reviewing a pull request, ask the assistant to check a diff for deep nesting, long parameter lists, and business logic embedded in JSX, and receive concrete refactoring suggestions aligned with the project style. ## Quick Start Review this React component for deep nesting, long parameter lists, and logic that should be lifted out of the JSX template.
