webdev-agent-kit
A frontend kit of skills and agents that helps Claude Code and other AI coding agents plan, debug, and review React and Next.js work, including reading Figma designs and screenshots into implementation specs.

A frontend kit of skills and agents that helps Claude Code and other AI coding agents plan, debug, and review React and Next.js work, including reading Figma designs and screenshots into implementation specs.
Maintain WebDev Agent Kit source rules, skills, metadata, and validators. Excludes upgrading installed copies.
Project memory: remember this mistake, save for learning, запиши себе в базу, сохрани для обучения, запомни эту ошибку. Requested…
Inspect Figma links through MCP or browser computer use, or analyze screenshots and selected-layer properties. Produce frontend…
Create, resume, analyze, or converge standard and deep frontend execution plans with traceable slices, evidence, and stop/resume…
Plan architecture and ownership for standard or deep React/Next.js work across routing, state, data, styling, forms, builds,…
Diagnose and fix frontend defects from evidence, including unclear UI/runtime errors, broken routes, styling regressions, and…
Set subject-grounded visual direction for standard or deep UI work, redesign, polish, critique, anti-template review, or design…
Review inspected designs or briefs for product-flow gaps and ask evidence-based user questions. Ground UI direction in audience,…
Implement approved React/Next.js design specs using existing CSS Modules, Redux, TanStack, and Axios conventions. Route…
Run scoped frontend lint verification, repair related lint failures, or plan explicitly requested lint setup. Prefer existing…
Build disposable experiments for unresolved UI or state decisions. Use when code and documentation cannot settle the question;…
Review frontend quality from evidence across code, UI, architecture, TypeScript, security, performance, verification,…
Consequential architecture or migration tradeoffs. Read-only; not routine file-location questions.
Exceptionally coupled architecture decisions with an explicit deeper-analysis budget. Read-only; not automatic escalation.
Ambiguous multi-file debugging or integration within a defined scope. Not unbounded redesign.
Bounded read-only repository lookup and fact extraction. Not implementation or external browsing.
Independent correctness review across changed boundaries. Read-only; not implementation.
Independent review of consequential security, architecture or data-loss risks. Read-only; not routine review.
An explicitly requested narrow independent review. Read-only; not self-approval or fixing.
An approved implementation slice within existing project conventions. Not product decisions or independent review.
Fully specified small mechanical edits with no new behavioral decisions. Not architecture or ambiguous fixes.
Is this you? Claim your profilePut a plugin at the top of Plugins, from $9