Frontend Solution Evaluator

Problem Statement

Frontend technical comparisons and feasibility assessments often rely on subjective experience, lacking quantifiable baselines. This skill structures the evaluation process, providing objective scoring and risk identification across complexity, performance, and device compatibility, helping engineers align on technical constraints before writing or refactoring code.

Core Capabilities & Workflow

• Dual-Mode Auto-Detection: Automatically switches between Mode A (Implementation Evaluation) and Mode B (Ideation Feasibility) based on user input, reducing interaction friction.
• Multi-Dimensional Quantitative Evaluation (Mode A):
• Complexity: Scores component structure, state management, dependency risks, development cost, and maintainability on a 1-5 scale.
• Performance Bottlenecks: Analyzes LCP, runtime rendering, animation frame rates, and network strategies, flagging low/medium/high risks.
• Device Compatibility: Evaluates specific configurations (e.g., low-end Android, integrated GPU PCs, 4K displays) to identify memory overflow and animation degradation.
• HTML Report Generation: Replaces template placeholders to output a self-contained HTML file featuring radar charts, bar charts, device heatmaps, and Top 3 Optimization Suggestions.
• Ideation Feasibility Breakdown (Mode B): Extracts core features from natural language or demo code, maps them to underlying technical paradigms (e.g., real-time sync, Canvas rendering), and assesses inherent complexity and paradigm coupling amplification.

Boundaries & Caveats

• Evaluation accuracy depends on the completeness of input code or descriptions; ambiguous inputs may trigger a Medium confidence confirmation step.
• Performance and device compatibility analyses are based on empirical criteria and reference configurations, not a replacement for real-device Profiling.
• Single-solution evaluations switch to a "Technical Health Dashboard" and do not provide cross-solution rankings.
• Improvement suggestions (feature degradation & roadmaps) in Mode B are optional and not generated by default.