adf-frontend-prototype

Original：🇨🇳 Chinese

Translated

Build a Frontend Prototype according to UI Rules and Standards.

2installs

Sourcechungtsai/adf-framework

Added on2026-10-02

NPX Install

npx skill4agent add chungtsai/adf-framework adf-frontend-prototype

SKILL.md Content (Chinese)

View Translation Comparison →

ADF Frontend Prototype

Purpose

The Prototype is used to validate workflows and interactions and may use Mock Data. It is not Production Code. If there is no UI Impact, the reason may be documented before skipping it.

ADF Common Invariants

Work Type may only use
```
NEW
```
,
```
CHANGE
```
, and
```
MIGRATION
```
.
Each Module may have only one Active Work Item at a time; the Module is the primary isolation boundary.

Compact Artifacts are used by default:

requirements.md

,

rules.md

,

standards.md

,

design.md

,

test-cases.md

, and

traceability.md

.

The presence of a file does not mean that the Stage is complete.
Stable identifiers remain in English:
```
REQ-*
```
,
```
BR-*
```
,
```
VAL-*
```
,
```
Q-*
```
,
```
UI-*
```
,
```
DEV-*
```
, and
```
MIG-*
```
.
Any behavior that cannot be substantiated must be marked as
```
UNKNOWN
```
or
```
REVIEW_REQUIRED
```
.
Expected Result must not be weakened to obtain a
```
PASS
```
.
Project-wide Standards are located under
```
standards/
```
.

Evidence-Guided Q&A

Parse the interactive-review, question-schema, approval-gate, and terminology from the single official source under

adf-project-install/references/

, and follow their rules. If the source is missing or its version is incompatible, stop any Stage requiring Review and do not maintain a local copy.

v5.1 Resources and Legacy Project Compatibility

The sole authoritative location for official resources is
```
adf-project-install/references/resources.json
```
; do not copy them to the project’s
```
.adf/templates/
```
or use custom templates.
Resolve sources from the project’s
```
.agents/skills/
```
or
```
.claude/skills/
```
; the installed Skill’s
```
scripts/project.mjs resolve <project> <resource-key>
```
may be used. If the versions or content of the two locations conflict, stop and do not fall back to the global scope.
If the Skill providing the official resources is not installed or its version is incompatible, prompt the user to install the applicable official version at the project level using
```
npx skills
```
. Review must not be skipped.
Read the project’s
```
standards/
```
and approved Evidence first; examples in official specifications are not project-approved standards and are not applied automatically.
Preserve the Module documentation, completion status, and approval records from v5.0. Fields or documents missing in the new version should be listed as remediation recommendations and must not automatically result in the revocation of approvals. Any remediation must follow a separate CHANGE.
For legacy Modules that have not adopted the new Gate, list only Functional Scenario or specification differences. Check the new requirements only for new work that has explicitly adopted them.