analyzing-frontend-layer
Use when analyzing frontend/UI layer including components, state management, routing, and API integration (optional - skip if no frontend exists)
npx skills add majiayu000/claude-skill-registry --skill analyzing-frontend-layer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyzing Frontend Layer **Output:** `docs/unwind/layers/frontend/` (folder with index.md + section files) **Principles:** See `analysis-principles.md` - completeness, machine-readable, link to source, no commentary, incremental writes. ## Output Structure ``` docs/unwind/layers/frontend/ ├── index.md # Route overview, page count, tech stack ├── routes.md # Routing structure ├── pages.md # Page purposes and user flows [MUST] ├── state.md # State management └── api-hooks.md # API integration points ``` For large codebases (20+ pages), split by feature: ``` docs/unwind/layers/frontend/ ├── index.md ├── auth-feature.md ├── dashboard-feature.md └── ... ``` ## Process (Incremental Writes) **Step 1: Setup** ```bash mkdir -p docs/unwind/layers/frontend/ ``` Write initial `index.md`: ```markdown # Frontend Layer ## Sections - [Routes](routes.md) - _pending_ - [Pages](pages.md) - _pending_ - [State](state.md) - _pending_ - [API Hooks](api-hooks.md) - _pending_ ## Summary _Analysis in progress..._ ``` **Step 2: Analyze and write routes.md** 1. Find route definitions 2. Document URL patterns and nesting 3. Write `routes.md` immediately 4. Update `index.md` **Step 3: Analyze and write pages.
- Output Structure
- Process (Incremental Writes)
- Output Format
- Additional Requirements
- Focus on WHAT, not HOW
- MUST Document (Essential for Feature Parity)
- SHOULD Document (Valuable Patterns)
- DON'T Document (Tech-Specific)
- Page Documentation Format
- Mandatory Tagging
- Refresh Mode
mkdir -p docs/unwind/layers/frontend/
What does the analyzing-frontend-layer skill do?
Use when analyzing frontend/UI layer including components, state management, routing, and API integration (optional - skip if no frontend exists)
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-frontend-layer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.