frontend-page-discovery

Original：🇨🇳 Chinese

Translated

Use when you need to generate "page list → function points → business processes → business rules" with evidence from frontend code, and the project has non-unique routing entries, complex dynamic routes/permissions/backend menus, and the team is prone to making assumptions or missing evidence chains.

2installs

Sourcezixun-github/aisdlc

Added on2026-03-02

NPX Install

npx skill4agent add zixun-github/aisdlc frontend-page-discovery

SKILL.md Content (Chinese)

View Translation Comparison →

Frontend Page List Reverse Generation (Evidence-based)

Overview

Goal: Generate page list and single-page description documents based on code evidence (saved to

docs/

directory).

When to use / When not to use

Usage scenarios (trigger signals)

You need to derive a traceable page list from frontend code, and further refine processes/rules
Complex project routing entries: coexistence of multiple SPAs/micro-frontends/multiple frameworks, runtime injected routes, backend-delivered menus
Common team problems: missing pages, duplicate pages, undocumentable permissions/dynamic routes, rule summaries lacking evidence

Non-usage scenarios

You only need to write PRD/prototypes (this is not code reverse engineering)
You are required to "provide the real page list/rule conclusions of your project even without code" (in this case, only templates/examples can be delivered, no factual output)

Default deliverables of this skill (saved to

docs/

directory)

```
docs/frontend/pages/index.md
```
```
docs/frontend/pages/<page_id>.md
```
```
docs/frontend/flows/index.md
```
```
docs/frontend/conflicts.md
```

Saved templates (minimum viable, can be copied directly)

The output templates of this skill have been moved to the

assets/

directory to reduce the length of the skill body and keep the templates reusable.

Template mapping:

docs/frontend/pages/index.md

←

<this SKILL.md directory>/assets/pages-index-template.md

docs/frontend/pages/<page_id>.md

←

<this SKILL.md directory>/assets/page-template.md

docs/frontend/flows/index.md

←

<this SKILL.md directory>/assets/flows-index-template.md

docs/frontend/conflicts.md

←

<this SKILL.md directory>/assets/conflicts-template.md

Hard rules (if any of the following occurs: stop and correct)

No assumptions allowed
- Any "page/process/rule" must point to evidence (see evidence format below); otherwise, write it into
```
Evidence Gaps
```
  , and no speculative conclusions are allowed.
Facts and examples must be physically isolated
- If the user requires "make bold assumptions without evidence", only output
```
EXAMPLE
```
  blocks or templates; do not write examples as project facts, nor mix them with fact tables.

Output fields must be complete

The page index must include
```
module_name
```
```
page_id
```
```
page_name
```
.

A single page must include

page_name

breadcrumb

ascii_wireframe

core tasks

key rule summary

.

Evidence format (unified and verifiable)

Each conclusion must be accompanied by at least 1 piece of evidence:

type:

page_title | route_decl | file_convention | menu_static | menu_backend | nav_call | guard | api_call | state_machine | form_validation | other

file: relative path
lines:
```
start-end
```
excerpt: 1–3 lines of key excerpts (original text)

When evidence is missing, you must write:

gap: What evidence is missing
candidate_locations: Where it may be found (directory/file type/keywords)
impact: Impact on the conclusion (e.g. "Cannot confirm whether there are hidden pages caused by backend-delivered menus")

Output fields (must appear in the final result)

Page index:
```
module_name
```
```
page_id
```
```
page_name
```

Single page:

page_name

breadcrumb

ascii_wireframe

core tasks

key rule summary