prd-createlisted

# PRD Create Keep the standard PRD document structure. Preserve every functional-page field and its restriction: field name, control/type, required state, default value, format, range, validation, linkage, editability, visibility, permission, and persistence rule when applicable. Simplify only redundant workflow prose; do not mistake product fields for PRD template fields. ## Default PRD Format 1. Start from `assets/prd-template.md`; retain its standard PRD sections. 2. In each Solution module, use the screenshot-first form in `assets/module-workflow-template.md`. 3. Put a screenshot under a short screen or scenario heading. 4. Put `需求描述` immediately below the screenshot. 5. For a screen with functional fields, put its `页面字段与限制` table directly below the description. Preserve all known field rules in that table. 6. Add branch flows, interaction constraints, page flows, data writes, error recovery, or technical contracts only when the screenshot, requirement description, and field table cannot express behavior R&D needs to implement. 7. Mark an unknown as `待确认`; never invent behavior or omit a known field restriction. One screenshot may support several clear requirements. Do not require a screenshot for every click. Use relative image paths and short alt text. When screenshots are design references rather than executable product evidence, describe their behavior as requirements, not observed facts. ## Page Field Rules - Treat a page field as any input, selector, switch, u