uiux-react-jsx-packager
uiux-react-jsx-packager
Output Contract
- Create one new
*.jsxfile (do not overwrite existing files unless explicitly requested). - Export the root component via
export default. - Keep runtime dependencies to React only (no
react-router,lucide-react,echarts,classnames,zustand, etc.). - Keep styles in-file via
<style>injection and/or inlinestyle={{...}}. - Replace icon libraries with inline SVG components.
- Replace images with base64-inlined data URLs or deterministic placeholders.
- Implement navigation via component state (optionally sync to
location.hashfor shareable URLs). - Preserve all interactions/animations/state logic; do not simplify behavior.
- Prefer embedding the compiled CSS (if available) to preserve spacing/colors/shadows.
关于“像素级一致”(可选增强,不是默认门禁)
“像素级一致 / pixel-perfect”在工程上必须限定条件,否则不可验证。只有当你要对外宣称 pixel-perfect 时,才需要做像素 diff 验收:
- 同一台机器、同一 OS 与同一浏览器版本(建议固定 Chrome 版本)
- 固定 viewport(宽高)与
deviceScaleFactor(DPR) - 字体必须一致(包含字重):不要依赖系统字体差异;必要时把字体文件以
@font-face形式内联进 CSS(base64 data URL) - 截图对比时必须处于“稳定态”:避免进行中动画/过渡影响像素 diff(见 Verification)
默认交付的强门禁是“可携带可跑、不白屏、导航可用”(见 Verification Gate)。
Workflow (do in order)
1) Discover structure and runtime surface
- Find and follow any
AGENTS.mdinstructions that apply to the target directory tree. - Locate the actual app entry (
src/main.*,src/index.*,App.*) and identify:- Router entrypoints (hash router / react-router / custom)
- Pages and module switch logic
- Global providers (theme/style/toast/auth)
- Global CSS + theme tokens (CSS variables, dark mode attribute, etc.)
- Third-party runtime deps that must be removed (icons, charts, router, utilities)
- Prefer reading the demo source plus the built output CSS (if it exists) to lock visuals.
2) Choose a “visual parity” strategy for styles (pick one)
- Preferred: Embed production/built CSS (e.g.
dist/assets/index-*.css) intoconst APP_CSS = String.raw\...`;and inject via`.- Keep existing
classNamestrings unchanged. - This is the most reliable way to keep spacing/colors/shadows identical without Tailwind tooling.
- Keep existing
- Otherwise: Inline/merge source CSS files into one
<style>block (still in-file).
Pixel-perfect 强依赖样式与字体,请额外确认:
- CSS variables / theme tokens(暗色模式 attribute/class)与原工程一致
- 所有外部字体/图标资源都已本地化/内联(不要依赖远程 URL)
- 截图对比用同一套 reset /
box-sizing规则(建议直接使用构建后 CSS)
3) Create the merge target file
- Create
YourNameMerged.jsxwith:- A single React import (
import React, { ... } from 'react';) APP_CSSstring + aAppStyleTag()that injects exactly one<style>node- Helpers you will need (clamp, download, clipboard, etc.)
- A single React import (
4) Merge code into one file (no module imports)
- Copy code for components/pages/hooks/utils into the single file.
- Remove all non-React imports; replace with local definitions.
- Remove TypeScript syntax:
- Delete
interface,type, generics (useState<string>()), and annotations (x: string) - Remove
as Tassertions
- Delete
- Keep behavior identical:
- Same default state values
- Same reducers/actions
- Same animations (CSS-based or requestAnimationFrame-based)
5) Replace third-party runtime dependencies (patterns)
Router → state router
- Implement a tiny state router (context +
navigate(module, subPath)). - Optionally keep hash sync for shareable URLs, but the source of truth must be React state.
Minimal pattern (adapt, do not paste blindly):
const RouterContext = React.createContext();
function RouterProvider({ children }) {
const [route, setRoute] = React.useState({ module_key: 'text_workbench', subPath: '' });
const navigate = React.useCallback((module_key, subPath = '') => setRoute({ module_key, subPath }), []);
return <RouterContext.Provider value={{ route, navigate }}>{children}</RouterContext.Provider>;
}
function useRouter() { return React.useContext(RouterContext); }
Icons (lucide-react etc.) → inline SVG
- Replace icon imports with local React components that return
<svg ...>+<path ...>. - Keep size/stroke defaults consistent with the original icon system.
Charts (echarts etc.) → SVG/Canvas + fallback table
- Re-implement charts with pure SVG/Canvas.
- Preserve:
- Tooltips
- Click/hover actions (emit the same callbacks)
- Accessible labels (aria where relevant)
- Data table fallback (for regressions and accessibility)
6) Images and external assets
- Replace runtime-loaded images with:
data:image/...;base64,...(preferred when you need fidelity)- Or deterministic placeholders (solid blocks, initials avatars, etc.)
- Never leave remote URLs in the final file unless explicitly allowed.
7) Wire the root component to real pages
- Ensure the default export renders the real module pages (not placeholders).
- Wrap providers in the same order as the original app (style/theme/toast/auth).
- Keep module-level side effects intact (e.g. console events, reducers, mock async flows).
8) Verification (must run before “done”)
Verification Gate(默认必达)
必须按顺序验证,任何一步失败都不算“打包完成”:
-
静态门禁(必须)
- 只保留 1 条
import ... from 'react' - 有
export default - 无
require()/import() - 无资产导入(
.css/.svg/.png/...) - 运行:
python3 scripts/verify_singlefile_jsx.py /path/to/Merged.jsx
- 只保留 1 条
-
运行时门禁(必须)
- 用一个“临时预览工程”加载该
.jsx,确保首屏不白屏,并且能完成最小交互 smoke:- 侧边栏(或顶栏)切换主要模块/页面(至少点一轮能切换内容)
location.hash切换(如果你实现了 hash 同步)
- 推荐使用本技能自带脚本:
bash scripts/preview_single_jsx_vite.sh /path/to/Merged.jsx
- 用一个“临时预览工程”加载该
常见误判:端口被占用时,Vite 会输出
Port XXXX is in use, trying another one...并自动切换端口。必须以终端输出的Local:URL 为准,不要死盯一个固定端口。
- 可携带性门禁(必须)
- 不依赖远程资源(字体/图片不要用
https://...) - 不在 UI/注释中泄露绝对路径(例如本机用户名/目录结构)
- 不依赖远程资源(字体/图片不要用
可选增强(仅在你宣称 pixel-perfect 时才要求)
- 用截图 diff 做像素级对比(固定浏览器/viewport/DPR,禁用动画/过渡)。
- 可选做 bundle sanity:
npx esbuild merged.jsx --bundle --format=esm --external:react --outfile=/tmp/merged.js
Use the bundled verifier:
python3 scripts/verify_singlefile_jsx.py /path/to/YourMerged.jsx
Pixel-perfect visual regression (recommended, required if you claim pixel-perfect)
最稳妥的办法是把 YourMerged.jsx 暂时放回原 demo 工程里,用原工程的构建链路渲染它(保证字体/CSS 环境一致),然后用截图做像素 diff:
- 在原工程增加一个“对照页/对照路由”(只用于本地验证):
OriginalApp:原始页面MergedApp:渲染YourMerged.jsx的默认导出
- 用同一套 Playwright 配置跑截图:
- 固定 viewport /
deviceScaleFactor prefers-reduced-motion: reduce- 注入一个 snapshot CSS(仅测试环境)来禁用过渡与动画,例如:
*,*::before,*::after{animation:none!important;transition:none!important;}
- 固定 viewport /
- 用像素级阈值为 0(或极小阈值)做对比;若有差异,回到 CSS/字体/布局来源排查。
注意:npx playwright install 等命令可能会下载浏览器二进制(供应链与联网风险)。如果你的环境要求离线/固定版本,请使用已安装的 Playwright 与固定浏览器版本。
Bundled Scripts
scripts/verify_singlefile_jsx.py: Heuristic gate to catch non-React imports,require(), missing default export, and common TS residue.scripts/preview_single_jsx_vite.sh: Spin up an isolated Vite dev server under/tmpand preview a single.jsxfile with an ErrorBoundary and reliable URL output.
References
references/preview-and-smoke.md: Preview pitfalls (port switching, cache reuse), smoke checklist, and troubleshooting playbook.
More from okwinds/miscellany
prd-to-engineering-spec
Transform PRD (Product Requirements Document) into actionable engineering specifications. Creates detailed technical specs that developers can implement step-by-step without ambiguity. Covers data modeling, API design, business logic, security architecture, deployment, and agent system design. Use when: converting product requirements to technical specs, validating PRD completeness, planning technical implementation, creating task breakdowns, or defining test specifications. Triggers: 'PRD to spec', 'convert requirements', 'technical spec from PRD', 'engineering doc from requirements', 'validate PRD'.
45headless-web-viewer
Render and view webpages using a headless browser (Playwright) to fetch JS-rendered HTML, extract visible text, and optionally save full-page screenshots. Use when a user asks to “无头浏览器打开/查看网页”, needs the rendered DOM instead of raw curl HTML, or wants a screenshot of a page.
33prd-writing-guide
Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.
23codebase-spec-extractor
Extract complete, replicable engineering specifications from existing codebases. Produces documentation detailed enough to fully replicate a project without seeing the original source code—even using a different tech stack. Use when: analyzing existing projects, documenting legacy systems, creating technical specs from code, preparing for system migration, or onboarding new teams. Triggers: 'extract spec from code', 'document codebase', 'analyze project architecture', 'create spec from existing system'.
16brainstorming
Turn vague ideas into a validated design/spec through structured brainstorming. Use before any creative work - new features, UI/components, behavior changes, refactors, architecture decisions. Trigger whenever a user asks to brainstorm, define requirements, propose approaches, write a design doc, or says something like 'I want to build X' or 'how should we approach Y'. Even seemingly simple tasks benefit from a quick design pass.
10skill-review-audit
Use when a user asks to review, interpret, or audit an AI agent skill (SKILL.md plus bundled scripts/references/assets) for capabilities, triggering behavior, tool/command usage, safety & privacy risk, supply-chain provenance, quality gaps, and improvement recommendations; also use when validating a skill before installing or deploying it.
9