styling-annotations
Customize Chartify labels, legends, axes, callouts, palettes, style settings, options, and trusted YAML configuration.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- styling-annotations
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Customize Chartify labels, legends, axes, callouts, palettes, style settings, options, and trusted YAML configuration.
- disable-model-invocation
- true
02 资源文件 5
- 参考文档references/api-reference.md7.6 KB
- 参考文档references/configuration.md3.6 KB
- 参考文档references/troubleshooting.md2.8 KB
- 参考文档references/workflows.md4.2 KB
- 脚本scripts/check_chartify_style_config.py5.9 KB
03 SKILL.md 正文
Styling and Annotations
Use this sub-skill when a task asks to polish or configure a Chartify chart: titles, subtitles, source labels, legend placement, axis labels/ranges/ticks, categorical factor order, callout lines/boxes/text, color palettes, accent colors, style settings, or Chartify YAML configuration.
Route data reshaping, plot-method selection, chart-type selection, second-axis plotting, radar plotting, and save/show basics to sibling basic-charting. Use the root skill for installation/import checks and cross-cutting browser export caveats.
Read/Run These Files
- Read references/api-reference.md when you need verified method signatures for labels, legends, axes, callouts, palettes, options, colors, or style settings.
- Read references/workflows.md for copyable patterns that customize labels, axes, legends, callouts, and palettes on a chart object.
- Read references/configuration.md before creating or loading Chartify option, style, color, or palette YAML files.
- Read references/troubleshooting.md when a palette name is invalid, a config directory is ignored, axis labels/ticks do not appear as expected, callouts land in the wrong place, or style settings do not apply.
- Run scripts/check_chartify_style_config.py to inspect a Chartify install, print option keys, verify palette lookups, or write a small trusted sample config directory.
Quick Route Map
| Task | Start here |
|---|---|
| Set title, subtitle, source label, or legend location | references/workflows.md |
| Set numeric/date ranges, tick values, tick formats, or factor order | references/workflows.md |
| Add vertical/horizontal reference lines, segments, shaded boxes, or text labels | references/workflows.md |
| Select categorical/sequential/diverging/accent palettes | references/workflows.md |
| Create custom colors or palettes | references/api-reference.md |
Persist defaults through CHARTIFY_CONFIG_DIR |
references/configuration.md |
| Diagnose style/config issues | references/troubleshooting.md and scripts/check_chartify_style_config.py |
Core Workflow
- Build or receive a
chartify.Chart/chartify.RadarChartobject frombasic-charting. - Apply labels first (
set_title,set_subtitle,set_source_label) so the chart communicates the takeaway before visual polish. - Choose axis controls that match the chart orientation and axis type. Categorical charts use factor order methods; numeric and datetime charts use range/tick methods.
- Choose the palette type before plotting when color assignment should affect glyph creation. Use accent palettes when a few categories should stand out and all other categories should use a default color.
- Add callouts after plotting so coordinates are meaningful in the rendered chart. For datetime axes, pass pandas timestamps or parseable datetime strings.
- Validate by checking
ch.figureproperties,ch.data, or a safe HTML save; avoid relying on notebook display as the only proof.
Decision Points
- Use
style.set_color_palette('categorical', ...)for unordered groups; usesequentialordivergingonly when values have meaningful order. - Use
accentpalettes withaccent_valueswhen one or more groups should be highlighted and the rest should fall back tostyle.color_palette_accent_default_color. - Use
set_xaxis_factors/set_yaxis_factorsfor categorical axis ordering; useset_xaxis_range/set_yaxis_rangefor numeric or datetime axes. - Use list tick orientations only for grouped categorical axes; each level can have a different orientation.
- Treat Chartify YAML config as trusted local configuration. Do not load YAML from untrusted users because some config paths use unsafe YAML loading.
Expected Outputs
A successful styling/annotation task usually returns code that mutates and returns a Chartify chart object, plus a validation note such as the updated figure title, axis range/factors, selected palette behavior, or an HTML save result. When a task asks for reusable defaults, provide a config-directory recipe from references/configuration.md and call out the trusted-file requirement.
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).