Loading...
Loading...
Found 2 Skills
Used for end-to-end generation and acceptance of React/HiUI pages from requirement refinement. Suitable for tasks such as generating and accepting pages from vague product requirements, pre-test checks for HiUI pages, experience walkthroughs after page generation, and closing the loop from requirement to implementation to UX acceptance for pages. Orchestrates hiui-refine, hiui-design, and ux-walkthrough: uses requirementGate, generationInputGate, and uxGate to control requirement confirmation, page generation input confirmation, engineering acceptance, graded UX acceptance, before/after screenshots, repair closure, and report output.
As a standard S0 pre-skill for larger page workflows like `hiui-page-workflow`, it focuses on requirement refinement for B-end back-office systems and before HiUI page generation. It transforms vague or abstract back-office/management/operation/configuration/approval workflow requirements into executable product solutions, MVP scopes, user flows, business rules, traceable page inventories, product PRDs, global generation contexts, page-level prompts, and HiUI handoff packages. It is suitable for clarifying back-office product ideas, converting rough requirements into PRDs or product solutions, breaking down work surfaces such as lists/details/editing/configuration, defining role permissions/data permissions/state machines/audit rules, and supplementing permission matrices, state transition tables, field dictionaries, exception and audit matrices, batch/import-export specifications, and legacy system transformation and release strategies when needed; it also acts as a B-end product expert to provide judgments including business value decomposition, priority suggestions, solution trade-offs, multi-tenant/version/activation models, master data and system boundaries, anti-pattern identification and risk prompts, continuously turning vague B-end requirements into implementable inputs; when requirements arise in existing projects/repositories, it is also used to perform context-aware requirement refinement combining the current repository's pages, modules, interfaces, types, and documents.