CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-architecture-review

Reviews Next/React boundaries, state ownership, duplicated client state, rendering contracts, and component boundaries. Use during frontend architecture refactoring.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/frontend-architecture-review/SKILL.md
SKILL.md
Quality
Evals
Security

Frontend Architecture Review Skill

Use this skill when reviewing Next.js App Router structures, component boundaries, state management, and React performance.

Repository Review Protocol

Follow AGENTS.md review throttling and docs/codex-review-protocol.md before starting. Do not review opportunistically or mutate files during pure review. After a completed PR review, post one Review record comment on the PR (see Records); never edit the frozen docs/branch-review-ledger.md table.

Review Checklist

1. Next.js App Router Boundaries

  • RSC vs. Client Components: Ensure components are Server Components by default. Keep client-side logic (use state, use effect, browser APIs) isolated to leaf components marked with "use client".
  • Data Fetching: Fetch data in Server Components or Server Actions where possible. Avoid calling internal /api/... endpoints directly from RSCs.

2. State & Rendering

  • State Duplication: Avoid replicating URL/router state in local React state. Prefer URLSearchParams and next/navigation controls for search/filters.
  • Rendering Waste: Check for unnecessary context re-renders, un-memoized expensive calculations, or excessive component mount/unmount cycles.
Repository

BigSimmo/PsychSift

Path

.cursor/skills/frontend-architecture-review/SKILL.md

Last updated
First committed

Is this your skill?

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.