component-renderer-development
Use for Dash component wrapper generation, built-in component packages, resources, and dash-renderer internals.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- component-renderer-development
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Use for Dash component wrapper generation, built-in component packages, resources, and dash-renderer internals.
- disable-model-invocation
- true
02 资源文件 7
- 参考文档references/component-generation.md2.5 KB
- 参考文档references/renderer-internals.md2.7 KB
- 参考文档references/resources-and-react.md2.2 KB
- 参考文档references/troubleshooting.md4.1 KB
- 脚本scripts/check_component_generator_cli.py1.2 KB
- 脚本scripts/check_renderer_cli.py1.2 KB
- 脚本scripts/check_update_components_cli.py1.2 KB
03 SKILL.md 正文
Dash Component and Renderer Development
Use this sub-skill when a task concerns component wrapper generation, built-in Dash component packages, resource loading, or the dash-renderer frontend and its callback pipeline.
Start here
- Read references/component-generation.md
for component metadata, generated wrappers, and
dash-generate-components. - Read references/resources-and-react.md
for
_js_dist,_css_dist, resource loading, and React version notes. - Read references/renderer-internals.md
for renderer hydration, callback queues,
setProps, and clientside runtime. - Read references/troubleshooting.md when a build, wrapper, bundle, or React runtime issue fails.
- Run scripts/check_component_generator_cli.py, scripts/check_update_components_cli.py, and scripts/check_renderer_cli.py for safe CLI help checks before heavier builds.
Main routes
Generate or refresh component wrappers
Use this route when a task mentions component metadata, wrapper generation, or
maintaining built-in component packages such as dcc, html, or dash_table.
Inspect renderer behavior
Use this route for callback hydration, layout crawling, state paths, shared
worker/WebSocket client behavior, window.dash_component_api, or React/runtime
compatibility problems.
Work on resource loading and React versions
Use this route when a task mentions resource URLs, asset fingerprints,
serve_locally, _js_dist, _css_dist, or React version/shim behavior.
Route elsewhere
- App-level callback and page use: app callback workflows.
- Server-side async, WebSocket, background, or MCP runtime behavior: server backends and async.
- Choosing focused tests or build/lint commands: testing and maintenance.
Validation checklist
Before marking component or renderer work complete:
- The component package can be imported from Dash and its generated wrapper class names are available.
dash-generate-components,dash-update-components, andrendererhelp text are healthy before a full build is attempted._js_dist/_css_distentries use the correct resource fields and do not point at the wrong namespace or package path.- Renderer changes are checked against the current React/runtime assumptions.
- If a build script needs Black or other formatter/tooling, the failure mode is documented and the prerequisite is installed first.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).