platform-frontend

Standardize frontend architecture patterns for scalable web apps.

16|15|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ravnhq/ai-toolkit --skill platform-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-frontend
Source: https://github.com/ravnhq/ai-toolkit/tree/main/skills/platform-frontend
Command: npx skills add https://github.com/ravnhq/ai-toolkit --skill platform-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes frontend architecture patterns across teams, reducing duplication and enabling scalable UI codebases.

Core Features & Use Cases

  • Framework-agnostic guidelines for organizing code by feature, avoiding barrel files, and preferring explicit imports.
  • State-management guidance for when to lift state, where to colocate data, and how to choose between local vs server state.
  • Real-world use case: When starting a new web app, apply the patterns to structure folders, naming, and components to improve maintainability and onboarding.

Quick Start

Start by adopting a feature-based folder structure in a new project and align the initial components and hooks with the guidelines.

Frequently Asked Questions about platform-frontend

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

FAQPage Schema
How do I structure a scalable frontend architecture for a growing web app?

To structure a scalable frontend architecture, adopt a feature-based folder organization that avoids barrel files and uses explicit imports. This standardizes component organization and reduces code duplication across teams.

What is the best way to manage state and colocate data in frontend components?

Effective state management requires deciding when to lift state and choosing between local and server state. Colocating data with its consuming components ensures maintainable frontend UI patterns.

Does this frontend architecture framework work with any UI library or web framework?

Yes, the guidelines are framework-agnostic and apply to any web application. They focus on standardizing naming conventions, explicit imports, and component design rather than locking into a specific UI library.

Why should I avoid barrel files when organizing frontend code by feature?

Avoiding barrel files in feature-based frontend organization enforces explicit imports. This prevents circular dependencies and improves codebase traceability for scalable web applications.

When do I need to standardize UI codebase patterns across multiple teams?

You need to standardize UI codebase patterns when starting a new web app or scaling existing teams. Consolidating architecture rules into reusable guidelines ensures consistent component design and faster onboarding.