Migrate one small page
Start with settings, a list or an editor panel rather than packaging a whole browser application.
- Collect static HTML/CSS, images and fonts, keeping layout and design tokens.
- Identify React/Vue, JavaScript, browser storage, routing and network dependencies.
- Verify important values and behavior in the current reference; parsing alone is insufficient.
- Reconnect state through native handlers or Lua; use the host for storage, OS services and tasks.
- Check resizing, IME, focus, scrolling and delivered resource paths.
Use a component style without assuming its runtime
Ask an agent for HTML/CSS inspired by Ant Design or Evergreen UI. Their React/JavaScript logic does not automatically run in KUI; implement interactions with KUI DOM, Lua or native APIs.
A migration brief for an agent
Provide the page, SDK, build command and acceptance actions. Ask the agent to retain the visual structure, identify browser APIs needing replacement and inspect the actual window with MCP.
Based on KUI, migrate this desktop settings page using HTML/CSS web standards.
Keep its layout, type hierarchy and colors without a JavaScript component runtime.
Use the current SDK native events or Lua for editing, saving, errors and restoring.
Check: it builds, saves a new name, rejects blank input and works in a narrow window.
Use DevTools/MCP to inspect DOM, input, buttons and a result screenshot.Something unclear?
Report an issue on this page →