<Purpose> Provide the complete base architecture contract for this repository so agents can work without external docs. </Purpose>

<Use_When>

Always, for every implementation/refactor task.
Before activating any other repository skill.
When task scope is unclear and a base architecture decision is needed. </Use_When>

<Architecture_Overview> Fractal Layered Architecture (FLA) is a frontend architecture approach designed for stable growth under changing business requirements.

Its core idea is responsibility isolation through one-way layer direction. This limits blast radius when failures happen and makes root-cause localization faster. </Architecture_Overview>

<Layer_Direction> Allowed direction (left to right): _pages -> _containers -> _states -> _components -> _apis -> _utils

Rules:

Lower layers must not reference upper layers.
Upper layers may access lower layers. </Layer_Direction>

<Nested_Layers> Layers may contain nested sub-layers for strong cohesion and easier feature moves/deletions.

Example:

└── _pages
    └── profile
        ├── profile.tsx
        └── _containers
            └── user
                ├── _components
                │   ├── avatar
                │   └── info
                ├── _states
                └── _apis

<Purpose> Provide the complete base architecture contract for this repository so agents can work without external docs. </Purpose>

<Use_When>

Always, for every implementation/refactor task.
Before activating any other repository skill.
When task scope is unclear and a base architecture decision is needed. </Use_When>

<Architecture_Overview> Fractal Layered Architecture (FLA) is a frontend architecture approach designed for stable growth under changing business requirements.

Its core idea is responsibility isolation through one-way layer direction. This limits blast radius when failures happen and makes root-cause localization faster. </Architecture_Overview>

<Layer_Direction> Allowed direction (left to right): _pages -> _containers -> _states -> _components -> _apis -> _utils

Rules:

Lower layers must not reference upper layers.
Upper layers may access lower layers. </Layer_Direction>

<Nested_Layers> Layers may contain nested sub-layers for strong cohesion and easier feature moves/deletions.

Example:

└── _pages
    └── profile
        ├── profile.tsx
        └── _containers
            └── user
                ├── _components
                │   ├── avatar
                │   └── info
                ├── _states
                └── _apis

Fla Architecture

Fla Architecture

Openclaw Ghsa Maintainer

Gh Issues

Security Triage

Github

Author Contributions

Repository Setup