メニュー
Use when setting up a fused-render checkout or git worktree for the first time — before running pytest, the dev server, or any daemon — so tests and the server actually work instead of silently failing on missing deps or an unbuilt React shell.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How to create and register a custom preview template for fused-render — a user-owned template that overrides, reorders, or extends the built-in extension → template mode list, so opening a file of that extension renders the user's template (or offers it as a switchable mode) instead. Use this whenever the user wants a custom/own preview for a file extension (e.g. "my own parquet viewer", "add a mode for .xyz files", "render .xyz files with my template"), wants to override, add, reorder, or disable template modes, mentions ~/.fused-render, registry.json, or _mode, or asks to "register a template". For actually writing the template's html and py files, this skill delegates to the fused-render-authoring skill — read that one too.
How to run and use a fused-render project — open files and views in the FusedRender desktop app and browse the filesystem. Use this whenever the user wants to open, run, launch, start, show, or explore a fused-render project or its views/files; asks to "open this in fused-render", "run fused-render", "show me this view", "look at this file in the explorer"; or is orienting inside a fused-render repo without yet authoring code. For creating/editing/debugging an .html view or .py data file, use fused-render-authoring instead; for registering custom preview templates, use fused-render-custom-templates.
How to author HTML views and Python data files for fused-render (the local HTML explorer with a fused.runPython() bridge, URL-synced params, and file IO helpers). Use when creating, editing, or debugging an .html view, a .py data file, or a preview template; when a view renders blank, shows a traceback overlay, or params don't sync to the URL; or when the user mentions fused.runPython/params/readFile/writeFile or asks for "a view for <file/data>".
Use when cutting a new fused-render release, bumping the version, or creating a release tag — bumps __version__, commits, tags vX.Y.Z, and pushes to trigger the DMG build/release workflow.
| name | setting-up-dev-env |
| description | Use when setting up a fused-render checkout or git worktree for the first time — before running pytest, the dev server, or any daemon — so tests and the server actually work instead of silently failing on missing deps or an unbuilt React shell. |
Every fresh checkout/worktree needs a 3.14 venv and a built React shell — both are gitignored, so they don't carry into a worktree. Without them, pytest/python silently run against the wrong interpreter or fail on missing deps, and every server test dies with RuntimeError: React shell not built.
Use scripts/dev.sh — never launch python -m fused_render.cli (or uvicorn) directly. It does almost all the setup for you: bootstraps a repo-local .venv (with [fused,bundled]) if missing, npm installs the frontend, builds shell-dist/, then runs vite build --watch + the server with Python auto-reload and per-worktree port/state isolation.
scripts/dev.sh # defaults
scripts/dev.sh --port 9000 # extra args pass through to the server
dev.sh covers the server, but its auto-venv has [fused,bundled] only — not the dev extra (pytest/xdist). And tests need a built shell-dist/ or create_app() refuses to start. So the venv install is the one manual step:
uv venv --python 3.14 .venv # 3.14 wheels now exist for the whole stack
uv pip install --python .venv/bin/python -e ".[dev,bundled,fused]" # dev extra now includes pytest-xdist
For shell-dist/: if you've run scripts/dev.sh, it's already built. If you'll only run tests and never start the server, build it once directly (repo uses npm, per package-lock.json):
cd frontend && npm install && npm run build && cd ..
Verify: ls fused_render/static/shell-dist/index.html and .venv/bin/python -m pytest -q (~1170 pass).
| Item | Why |
|---|---|
| Python 3.14 | whole stack (duckdb, rasterio, geopandas, shapely, zarr, scipy, pymupdf…) now ships 3.14 wheels; fused wheel is pure-python py3-none-any (marker needs ≥3.11). requires-python is ≥3.10, so 3.12/3.13 also work — 3.14 is just the current default |
dev extra | pytest + httpx (backs TestClient) |
bundled extra | duckdb, rasterio, zarr, pandas, geopandas… (templates + daemons) |
fused extra | compute-engine wheel for /api/run |
| frontend build | create_app() refuses to start without shell-dist/ |
ensurepip | only for the Deploy one-click path, not the suite |
Parallel tests: the suite is xdist-safe (process isolation), so pytest -n auto works (~4.5x faster). Process-based only — os.chdir + importlib.reload would race under a threaded runner.