frontend-dev-guidelines

Standardize React component creation, data fetching, and routing in TypeScript applications.

41|5|Updated Sep 30, 2025
One-click install
npx skills add https://github.com/efekrbas/discord-hypesquad-manager --skill frontend-dev-guidelines-efekrbas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-dev-guidelines
Source: https://github.com/efekrbas/discord-hypesquad-manager/tree/main/.agents/skills/frontend-dev-guidelines
Command: npx skills add https://github.com/efekrbas/discord-hypesquad-manager --skill frontend-dev-guidelines-efekrbas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes frontend React work so teams can build predictable, maintainable interfaces with strong typing, clear boundaries, and safer performance defaults.

Core Features & Use Cases

  • Suspense-first data flow: Use it when creating components, pages, and feature screens that fetch or mutate data.
  • Feature-based architecture: Apply it to organize code into reusable components, isolated features, hooks, helpers, and types.
  • Production UI standards: Follow it for routing, lazy loading, MUI styling, error handling, and performance tuning in long-lived React codebases.
  • Use case: A developer adding a new dashboard page can use this Skill to decide component structure, data fetching patterns, loading behavior, and file placement.

Quick Start

Apply the frontend-dev-guidelines skill to design, review, or refactor a React feature with Suspense-first fetching, strict TypeScript, and feature-based organization.

Frequently Asked Questions about frontend-dev-guidelines

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

FAQPage Schema
How do I structure a React project with feature-based organization in TypeScript?

Feature-based organization structures React projects into isolated features, reusable components, hooks, helpers, and types. This approach enforces strict typing and clear boundaries, ensuring maintainable interfaces that scale safely as the codebase grows.

What is Suspense-first data fetching in React and when should I use it?

Suspense-first data fetching standardizes loading behavior for React components and pages that fetch or mutate data. Use this pattern when creating feature screens to establish predictable, safer performance defaults for asynchronous rendering across your application.

What's the best way to implement lazy loading and routing for production React applications?

Production React routing and lazy loading should follow performance-safe patterns with strict TypeScript. Standardizing these UI standards ensures clear boundaries and predictable behavior in long-lived codebases, preventing performance degradation as pages scale.

Can I use MUI styling patterns with strict TypeScript and Suspense boundaries?

MUI styling integrates with strict TypeScript and Suspense-first loading through performance-safe patterns. Applying standardized MUI implementation ensures clear component boundaries and safer performance defaults while maintaining strict typing across your feature architecture.

Why does my React component structure break down when refactoring large TypeScript applications?

Component structure breaks down without feature-based organization and strict typing. Standardizing frontend React implementation with isolated features, clear boundaries, and Suspense-first data flow prevents architectural decay during refactoring in long-lived codebases.