flat-composition

Organize frontend code into flat, zero-props components with container-driven layouts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/maxlogvn/AiCMR --skill flat-composition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flat-composition
Source: https://github.com/maxlogvn/AiCMR/tree/main/.claude/skills/flat-composition
Command: npx skills add https://github.com/maxlogvn/AiCMR --skill flat-composition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize frontend code with a flat composition pattern to avoid deep nesting and promote self-contained UI units.

Core Features & Use Cases

  • Flat component structure with no nesting
  • Zero-props components that self-fetch data
  • Container-driven layout with clear boundaries across features
  • Guidance on component organization and migration workflows as described in DESIGN_ADN.md

Quick Start

Create independent, zero-prop components and wire them through a thin container using the flat composition rules.

Frequently Asked Questions about flat-composition

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

FAQPage Schema
What is flat composition in frontend architecture?

Flat composition is a frontend architecture pattern that eliminates deep component nesting to promote self-contained UI units. It organizes code into zero-props components that self-fetch data, wired through a thin container-driven layout with clear boundaries across features.

How do I build zero-props components that manage their own data?

To build zero-props components, you create independent UI units that self-fetch data and wire them through a thin container. This flat composition approach enforces component autonomy by removing nested prop drilling and standardizing directory structure across features.

How do I avoid deep component nesting in my frontend codebase?

To avoid deep component nesting, apply a flat composition pattern using container-driven layouts and clear component boundaries. This enforces zero-props components and standardized directory structures to keep UI units self-contained across features.

When should I use a container-driven layout for UI components?

Use a container-driven layout when you need to enforce clear component boundaries and eliminate deep nesting across features. This pattern works best for scaling frontend codebases with zero-props components that require standardized organization and migration workflows.

How do I migrate an existing frontend codebase to a flat component structure?

Migration to a flat component structure uses provided workflow checks, component templates, and migration guidance. You refactor deeply nested UI units into zero-props components and wire them through a thin container while enforcing clear boundaries across feature directories.

How does DESIGN_ADN.md work with flat composition patterns?

DESIGN_ADN.md serves as the source of design tokens for flat composition patterns. It standardizes component templates and migration workflows, ensuring zero-props components and container-driven layouts maintain consistent design boundaries across feature directories.