frontend-engineer

Codify React/TypeScript frontend engineering best practices for consistent patterns.

21|2|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/siviter-xyz/dot-agent --skill frontend-engineer-siviter-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-engineer
Source: https://github.com/siviter-xyz/dot-agent/tree/main/skills/frontend-engineer
Command: npx skills add https://github.com/siviter-xyz/dot-agent --skill frontend-engineer-siviter-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Frontend teams often ship inconsistent UI code, duplicative patterns, and partially adopted techniques. This Skill consolidates modern React/TypeScript guidelines into a single reference to improve maintainability, performance, and developer velocity.

Core Features & Use Cases

  • Conventions for component structure: guidelines for file organization, props, hooks, and naming.
  • Data fetching & rendering patterns: recommended Suspense-based data fetching, error handling, and caching.
  • Performance & styling: guidance on code-splitting, lazy loading, MUI v7 styling, and responsive design.
  • Use Case: A new project starts with the recommended features/ directory layout and TanStack Router-based routing for a cohesive developer experience.

Quick Start

Apply the frontend-engineer guidelines to your React/TypeScript project by aligning components, routes, and styles with the referenced patterns and files.

Frequently Asked Questions about frontend-engineer

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

FAQPage Schema
What are the best practices for organizing React and TypeScript project components?

Best practices for React and TypeScript project components involve using a feature-based organization structure, such as a features/ directory layout. This approach improves maintainability, performance, and developer velocity by ensuring consistent file organization, props, hooks, and naming conventions across teams.

How do I implement Suspense-based data fetching in a React application?

Implementing Suspense-based data fetching in a React application requires aligning your data fetching patterns with recommended guidelines for error handling and caching. This modern approach ensures consistent UI rendering and improves overall application performance by standardizing how asynchronous data is loaded and managed.

Does this guide support TanStack Router for React routing?

Yes, this guide explicitly supports TanStack Router for React routing. It recommends starting new projects with TanStack Router-based routing alongside a feature-based directory layout to provide a cohesive developer experience and enforce consistent routing patterns across your application.

What is the recommended way to style React components with MUI v7?

The recommended way to style React components with MUI v7 involves following specific guidelines for code-splitting, lazy loading, and responsive design. These styling practices are codified to ensure consistent UI code, prevent duplicative patterns, and maintain high performance across modern React projects.

How do I enforce consistent TypeScript standards across a frontend team?

To enforce consistent TypeScript standards across a frontend team, apply consolidated engineering guidelines to your component creation, data fetching, and architecture. This approach codifies TypeScript standards directly into code and architecture, eliminating partially adopted techniques and ensuring maintainable outputs.

When should I use feature-based organization in my React project?

You should use feature-based organization in your React project when starting a new project or aiming to improve maintainability across teams. This directory layout structure ensures a cohesive developer experience by standardizing component creation, routing, and project organization from the beginning.