芸众原型助手

将本 Skill 作为芸众商城原型的统一入口。包内已包含 Router、后台原型规则、前台原型规则、运行时 Starter 与统一工作区契约。

1. 先路由，再设计

1. Read references/路由/decision-flow.md and references/路由/scope-routing.md.
2. Classify the requirement from actor, goal, operation, and surface as:
   - BACKEND_ONLY
   - FRONTEND_ONLY
   - BOTH
   - NO_PROTOTYPE_REQUIRED
3. For BOTH, also read references/路由/requirement-decomposition.md and references/路由/shared-domain-rules.md before designing either surface.
4. Record every atomic requirement in a coverage matrix. System/API/database/queue/native-SDK work is not automatically UI.

2. 后台子模式

For BACKEND_ONLY, or the backend work package of BOTH:

1. Read references/后台/entry.md as the backend sub-mode entry.
2. Follow its progressive-loading instructions, but resolve all backend reference paths inside references/后台/.
3. Use assets/后台/prototype-starter/ when a standalone admin runtime is useful.
4. Backend visual and interaction rules come only from the bundled backend references.

Backend scope includes Laravel/芸众 administration, plugin management, lists, forms, details, settings, workflows, records, logs, exports, permissions, and operator-facing actions.

Do not use backend UI patterns for H5/App/WebView storefront pages.

3. 前台子模式

For FRONTEND_ONLY, or the frontend work package of BOTH:

1. Read references/前台/entry.md as the frontend sub-mode entry.
2. Follow its progressive-loading instructions, but resolve all frontend reference paths inside references/前台/.
3. Use assets/前台/prototype-starter/ when a standalone mobile runtime is useful.
4. Frontend visual and interaction rules come only from the bundled frontend references.

Frontend scope includes customer-facing H5/App WebView/Mini Program WebView mall surfaces, goods, cart, checkout, orders, member flows, DIY pages, campaigns, plugin pages/extensions, and platform-capability mocks.

Do not use frontend mobile patterns for administration surfaces.

4. 前后台联动模式

For a cross-end requirement:

1. Build a shared domain contract first: vocabulary, objects, fields, states, actions, transitions, and dependencies.
2. Split responsibilities into:
   - Shared domain
   - Backend responsibilities
   - Frontend responsibilities
   - System/non-UI responsibilities
3. Apply Backend mode only to the backend package.
4. Apply Frontend mode only to the frontend package.
5. Read references/路由/cross-end-consistency.md and verify terminology, state names, fields, role semantics, and action availability across both prototypes.
6. Assemble the result using references/路由/output-contract.md and, when useful, assets/工作区/workspace-starter/.
7. Never visually merge desktop admin and mobile storefront into one design system. A unified launcher may link them as separate surfaces.

5. 无需原型模式

If the request is purely non-UI work such as queue optimization, database migration, API refactor, background synchronization, deployment, or algorithm changes:

• Return NO_PROTOTYPE_REQUIRED with the routing evidence.
• List the non-UI responsibilities.
• Generate UI only for explicitly requested configuration, searchable records, monitoring, exception handling, or manual operations.

6. Output contract

For generated prototypes:

• Keep one coherent entry point.
• Use local assets; avoid CDN dependencies unless the user explicitly asks otherwise.
• Make simulated data and simulated system/native behavior explicit.
• Include requirement summary, scope verdict, IA/page map, assumptions, interactions, coverage, and limitations.
• For BOTH, include shared domain and cross-end flow/consistency notes.
• Prefer independently runnable static prototypes.

Read references/路由/output-contract.md for detailed workspace rules.

7. Validation

Before delivery:

1. Read references/路由/validation-rules.md.
2. Verify every atomic requirement is COVERED, PARTIAL, NON_UI, OUT_OF_SCOPE, or UNVERIFIED.
3. Validate local HTML/CSS/JS/JSON paths and syntax.
4. When browser automation is available, test page load, console, navigation, interactions, states, and screenshots at the appropriate desktop/mobile viewport.
5. Do not claim real API, database, auth, payment, queue, upload, or native bridge behavior unless actually implemented.
6. For BOTH, run cross-end state/data consistency checks.

8. Isolation invariants

• Backend tokens/layout/components never become frontend defaults.
• Frontend dynamic theme/DIY/mobile patterns never become backend defaults.
• Shared domain rules define business semantics, not UI styling.
• Campaign styling stays scoped to campaigns.
• Legacy backend/frontend patterns remain excluded according to their respective legacy-boundary.md files.
• Do not invent a third unified design system.

9. Escalation

Read references/路由/escalation-rules.md only when scope remains materially ambiguous, a backend/frontend boundary is crossed, or validation reveals a reusable rule defect.