Inspect and search the target project's local design system before implementing a Lanhu design. Use when a Lanhu-to-code workflow needs existing components, variables, tokens, CSS classes, DESIGN.md rules, or reusable style conventions. This fills the local equivalent of Figma design-system library search for Lanhu workflows.
Generate an interactive HTML parity baseline from fetched Lanhu artifacts. Use after Lanhu schema/assets are downloaded and before translating a design into React, Next.js, Vue, Flutter, native code, or standalone HTML. Load lanhu-use first for script path and artifact safety rules.
Restore Lanhu designs into target project code with high visual fidelity. Use when the user provides a Lanhu URL and wants a screen/page/component implemented in React, Next.js, Vue, Nuxt, Flutter, Android, iOS, or standalone HTML. This is the high-level orchestration skill; load lanhu-use, lanhu-fetch-design, lanhu-generate-baseline, and lanhu-verify-parity as needed.
Core Lanhu tool-use rules for Codex. Use before running Lanhu plugin scripts, authenticating with Lanhu, parsing Lanhu URLs, fetching schema/assets, or handling Lanhu API errors. This is the foundational skill for all Lanhu design-to-code workflows and should be loaded alongside higher-level Lanhu skills such as lanhu-fetch-design, lanhu-generate-baseline, lanhu-verify-parity, and lanhu-restore-design.
Verify visual, interaction, and implementation parity for Lanhu design restoration. Use after generating a baseline or implementing Lanhu design code to check schema fidelity, preview PNG match, local asset usage, styling completeness, real control behavior, and framework adaptation risks.
Fetch Lanhu design data into local artifacts. Use when the user asks to list Lanhu designs, fetch Lanhu schema, download preview PNGs, localize image assets, inspect Lanhu tokens, or prepare design artifacts before implementation. Load lanhu-use first for authentication, URL parsing, and script safety rules.