frontend-fundamentals

Review React and Vue components for architecture, state management, and accessibility.

274|18|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/DanielPodolsky/ownyourcode --skill frontend-fundamentals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-fundamentals
Source: https://github.com/DanielPodolsky/ownyourcode/tree/main/.claude/skills/fundamentals/frontend
Command: npx skills add https://github.com/DanielPodolsky/ownyourcode --skill frontend-fundamentals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend fundamentals review helps ensure junior developers write components with proper architecture, state management, and accessible markup, preventing common pitfalls.

Core Features & Use Cases

  • Component Architecture: ensure Single Responsibility, readability, and clear naming.
  • State Management Guidance: advise colocated state, lifting, and minimizing prop drilling.
  • Accessibility & Performance: check semantic HTML, keyboard navigation, and performance considerations.
  • Use Case: When a junior builds a UI component, run this skill to validate structure and state decisions before merging.

Quick Start

Use the frontend-fundamentals skill to review a new React/Vue component for architecture, state usage, and accessibility before integration.

Frequently Asked Questions about frontend-fundamentals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to review React component architecture before merging?

The best way to review React component architecture is applying a checklist to verify single responsibility, readability, and clear naming. This approach validates structure and state decisions to improve frontend quality before integration.

How do I check Vue component state management for prop drilling issues?

Check Vue component state management by evaluating colocated state, lifting strategies, and minimizing prop drilling. This ensures junior developers use proper state allocation and prevent common architectural pitfalls during component creation.

Does this frontend review process cover accessibility and keyboard navigation?

Yes, the frontend review process covers accessibility and keyboard navigation. It checks semantic HTML markup and keyboard interactions alongside performance considerations to ensure interactive widgets and modals are fully accessible.

Can I use this checklist approach for interactive widgets and modals?

Yes, you can use this checklist approach for interactive widgets and modals. It applies during the creation and review of framework components to validate architecture, state usage, and accessibility comprehensively.

When do I need a checklist-based frontend component review?

You need a checklist-based frontend component review when a junior developer builds UI components. Run it to validate structure, verify state management decisions, and enforce accessibility standards before merging new code.