一键导入
debug-viz
Debug hypergraph visualization issues: missing edges, wrong routing when expanded/collapsed, inputs outside containers, or mismatched layout bounds.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Debug hypergraph visualization issues: missing edges, wrong routing when expanded/collapsed, inputs outside containers, or mismatched layout bounds.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
End-to-end feature implementation with quality gates at each phase. Triggers: /feature, implement feature, build feature, new feature
Code quality checklist: code smells, design principles, SOLID, flat-code rules. Not directly invocable — loaded by agents via skills: [quality-criteria].
Technical documentation writer for Python libraries and frameworks. Produces clear, well-structured documentation following patterns extracted from best-in-class open source projects. - MANDATORY TRIGGERS: documentation, docs, write docs, doc page, getting started page, introduction page, tutorial, how-to guide, API reference, quickstart, README, explain this library, write a guide, improve docs, rewrite documentation - Use when creating or improving documentation for any Python library, framework, tool, or API - Use when rewriting existing docs to be clearer, better structured, or more developer-friendly - Use when creating any of: landing pages, concept explanations, tutorials, how-to guides, API references, pattern cookbooks, comparison pages, "when to use" pages
Stress-test the hypergraph framework by mapping capabilities against facets, spawning agents that build real-world scenarios for each combination to find bugs, inconsistencies, and feature gaps.
Creates comprehensive N-dimensional test matrices for codebases. Use when asked to analyze test coverage, identify testing gaps, create test plans, or review what tests exist vs what's needed.
| name | debug-viz |
| description | Debug hypergraph visualization issues: missing edges, wrong routing when expanded/collapsed, inputs outside containers, or mismatched layout bounds. |
Use this skill for visualization bugs in the compact GraphIR, the Python/JS
scene builders, or the split viz_*.js browser modules.
renderer/ir_builder.py converts the flat graph into a compact GraphIR.widget.py sends a compact GraphIR payload, initial expansion state, and
render options to html/generator.py; its embedded nodes and edges are
empty rather than a prebuilt scene.assets/viz.js and assets/scene_builder.js run in the browser: the
browser derives the visible scene and current debug data from the embedded
IR.scene_builder.py is the Python scene oracle for explicit states; it is not
the payload embedded by visualize().assets/viz_layout.js,
assets/viz_edges.js, assets/viz_nodes.js, assets/viz_controls.js, and
assets/viz_debug.js.meta.ir,
meta.initial_expansion, render options, and empty nodes/edges facts.Generate debug HTML and a summary of its exact compact GraphIR payload:
uv run python .claude/skills/debug-viz/scripts/debug_viz.py \
myapp.graphs my_graph_config --depth 1 --open
Use separate outputs mode:
uv run python .claude/skills/debug-viz/scripts/debug_viz.py \
myapp.graphs my_graph_config --depth 1 --separate-outputs --open
Inspect a scene derived for an explicit all-collapsed or all-expanded state:
uv run python .claude/skills/debug-viz/scripts/inspect_scene.py \
myapp.graphs my_graph_config --collapsed
uv run python .claude/skills/debug-viz/scripts/inspect_scene.py \
myapp.graphs my_graph_config --expanded --separate-outputs
meta.ir.meta.initial_expansion with the state passed to
build_initial_scene().ownerContainer is state-dependent;
deepestOwnerContainer is the deepest state-independent owner.nodes and edges are empty; the browser derives the
visible scene and post-layout debug data from meta.ir.inspect_scene.py when you need deterministic
nodes and edges for one explicit expansion state.scene_builder.py and assets/scene_builder.js.assets/viz_layout.js for dagre and compound
layout, then assets/viz_edges.js for final curve rendering.window.__hypergraphVizDebug is installed after layout for every visualization.
It exposes browser-derived nodes, edges, layout measurements, and a summary;
the compact widget payload does not embed routing maps. Wait for
window.__hypergraphVizReady === true before reading it.
window.__hypergraph_debug_viz = true is a separate pre-render flag that shows
the developer layout controls. The Python _debug_overlays option only records
metadata today; it does not gate the browser API or render extra UI.
src/hypergraph/viz/ir_schema.py: GraphIR schema.src/hypergraph/viz/renderer/ir_builder.py: flat graph to IR.src/hypergraph/viz/scene_builder.py: Python scene builder and test oracle.src/hypergraph/viz/assets/scene_builder.js: JavaScript scene-builder twin.src/hypergraph/viz/widget.py: compact payload embedded by visualize().src/hypergraph/viz/renderer/__init__.py: explicit Python scene-building
compatibility surface; it is not the widget payload path.src/hypergraph/viz/assets/viz_layout.js: layout and routing.src/hypergraph/viz/assets/viz_debug.js: window.__hypergraphVizDebug.src/hypergraph/viz/assets/viz.js: state management and scene refresh.src/hypergraph/viz/html/generator.py: standalone HTML assembly.uv run pytest -n 0 tests/viz/test_debug_skill_scripts.pyuv run pytest -n 0 tests/viz/test_scene_builder.pyuv run pytest -n 0 tests/viz/test_viz_modules_js.pyuv run pytest -n 0 tests/viz/test_renderer.py