mit einem Klick
figure-recommender
// Use when the user wants help choosing a scientific chart type, matching a data-storytelling goal to a figure, or finding the right notebook template in Awesome-Scientific-Figures.
// Use when the user wants help choosing a scientific chart type, matching a data-storytelling goal to a figure, or finding the right notebook template in Awesome-Scientific-Figures.
| name | figure-recommender |
| description | Use when the user wants help choosing a scientific chart type, matching a data-storytelling goal to a figure, or finding the right notebook template in Awesome-Scientific-Figures. |
Recommend chart types and reference notebooks for users working with the figures curated in this repo.
This skill is for recommendation only. It does not replace notebook editing, data cleaning, or full plotting tutorials.
Use this skill when the user:
Awesome-Scientific-Figures/Do not use this skill as the primary workflow when the user:
references/figure-recommender.md.Not recommended / 不推荐 item.Keep the answer compact. Prefer this structure:
推荐图种 1:
- 图种:
- 参考文件:
- 适合原因:
推荐图种 2:
- 图种:
- 参考文件:
- 适合原因:
可选图种 3:
- 图种:
- 参考文件:
- 适合原因:
不推荐:
- 图种:
- 原因:
For English requests, use:
Recommended figure 1:
- Figure type:
- Reference file:
- Why it fits:
Recommended figure 2:
- Figure type:
- Reference file:
- Why it fits:
Optional figure 3:
- Figure type:
- Reference file:
- Why it fits:
Not recommended:
- Figure type:
- Why not:
Awesome-Scientific-Figures/热力图.ipynb.Load only this file unless the task expands beyond recommendation:
references/figure-recommender.md -> chart-selection rules, notebook mapping, anti-patterns, and bilingual cue wordsUse when the user wants a recent literature sweep for Awesome-Virtual-Cell, especially for latest papers, Nature-family journals, major labs, big groups, or a time-bounded update of what the README is missing.
Use when the user wants to judge whether a paper, dataset, benchmark, blog, or related resource belongs in Awesome-Virtual-Cell, whether an existing README entry should be updated, where an item should be placed, or how it should be written in house style.
Use when the user wants to design, restructure, diagnose, or improve an awesome-style repository, especially when a curated README feels hard to browse, poorly scoped, or difficult for new users.