Review frontend project structure

When To Use

• Before UI edits
• When finding duplicated component patterns
• When choosing a verification strategy

When Not To Use

• When design assets are missing and decisions need product approval
• When the user expects a full redesign
• When production deployment is requested

Inputs Required

• Project tree
• Package scripts
• Relevant UI framework context

Expected Outputs

• Structure map
• Risk list
• Improvement plan

Skill Bundle

MCP Discovery Workflow

Use this as read-only discovery and planning. The live endpoint does not execute the workflow or install packages.

1. search_solutions - Find scenario solutions by workflow problem.
2. get_solution_detail - Inspect the scenario solution, risk boundary, skill bundle, and CTA.
3. search_skills - Search the current public GetSkillary skill catalog.
4. get_skill_detail - Inspect the primary or supporting skill detail.
5. get_download_url - Get a manual download URL for the selected skill.
6. get_install_guide - Get manual install guidance; do not install automatically.

search_solutions("Review frontend project structure")
search_skills("Frontend Structure Analyzer")
search_skills("Codebase Analysis Probe")
search_skills("Create Distinctive, Production-grade Frontend Interfaces")

Safety Boundary

Execution mode

local_agent_guided_no_hosted_execution

Human review required

Yes

Modifies local files

No

Requires API key

No

Requires external account

No

Local scenario-solution architecture only. This does not publish Batch 3, deploy production pages, add hosted execution, or claim AI citation, recommendation, ranking, click, lead, or conversion improvement.

Success Criteria

• Routes and components are identified
• Styling system is described
• Verification steps are concrete

Failure Modes

• Inventing a framework
• Ignoring responsive states
• Making design claims without screenshots

Example Prompt

How should an AI agent review a frontend project structure before changing UI?

Example Input

A React or Next.js workspace with route and component folders.

Example Output Summary

A component and route map with safe UI change guidance.

Next Action

Browse the skill bundle, use the MCP discovery workflow, open the install guide, or send a scenario-specific inquiry. Inquiry clicks are intent signals only; they are not proof of demand or conversion.