Agent skill · software engineering · aiskillstore
frontend-fundamentals
Auto-invoke when reviewing React, Vue, or frontend component code. Enforces component architecture, state management patterns, and UI best practices.
Why this skill is useful
Provides specific architectural patterns and best practices for frontend component design that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Frontend Fundamentals Review "A component should do ONE thing well. If you're describing it with 'and', split it." When to Apply Activate this skill when reviewing: React/Vue/Svelte components UI rendering logic State management code CSS/styling decisions Client-side routing --- Review Checklist Component Architecture [ ] Single Responsibility: Does each component do ONE job? [ ] Size Check: Is the component under 200 lines? [ ] Props Count: Are there fewer than 7 props? [ ] Naming: Can you describe the component without saying "and"? State Management [ ] Colocation: Is state as close as possible to where it's used? [ ] Lifting: Is state shared properly between siblings via parent? [ ] Context vs Props: Is prop drilling avoided (max 3 levels)? [ ] Server State: Is server data managed separately (React Query/SWR)? Performance [ ] Memoization: Are expensive computations wrapped in useMemo? [ ] Callbacks: Are event handlers wrapped in useCallback where needed? [ ] Re-renders: Will this cause unnecessary re-renders? [ ] Lazy Loading: Are heavy components code-split? Accessibility [ ] Semantic HTML: Are proper elements used (button vs div)? [ ] ARIA: Are interactive elements accessible? [ ] Keyboard: Can users navigate without a mouse? --- Common Mistakes (Anti-Patterns) 1. God Components 2. Logic in Render 3. Prop Drilling 4. Boolean Prop Soup --- Socratic Questions Ask the junior these questions instead of giving answers: 1. Architecture: "What is the ONE job of this component?" 2. Splitting: "If I asked you to use just the header part elsewhere, could you?" 3. State: "Who needs this data? Should it live here or higher up?" 4. Performance: "What happens when the parent re-renders?" 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/frontend-fundamentals