mobile-blog-chart-visual
Skill1 starsChanged 3 months agoMITView on GitHub
Mobile-readable **blog / article SVG (and static) charts** without wrecking desktop density — viewBox/fontSize scale formula, soft type floors, label wrap, plot-share, fixed right value column, no max-h / overflow-hidden clip, no chart subtitles under the title. Use when blog figures are squinty, clipped, sparse, "mobile chart", "fix blog charts", or /mobile-blog-chart-visual. Prefer mobile-app-echarts-visual for product card/portfolio ECharts. Prefer tufte for chart-type honesty; browser-verify for e2e proof.
In this repository47 other files it gives its agents.
- data-apache-lakehouseSkill
- data-apiSkill
- dataSkill
- data-duckdbSkill
- data-identity-resolutionSkill
- data-pipeline-operationsSkill
- data-pokemon-tcg-foundationsSkill
- data-product-evalSkill
- data-reelsSkill
- data-semantic-qualitySkill
- data-table-lifecycleSkill
- html-designSkill
- ebay-listingSkill
- flutter-pro-ux-reviewSkill
- flutterSkill
- browser-testing-with-devtoolsSkill
- browser-verifySkill
- design-systemSkill
- frontend-designSkill
- mobile-app-echarts-visualSkill
- mobile-chart-visualSkill
- mobile-product-uxSkill
- mockup-implementSkill
- product-designSkill
- product-ui-craftSkill
- prototypeSkill
- react-performanceSkill
- ui-exploreSkill
- visual-verifySkill
- web-qualitySkill
- high-retention-insight-reels-instagramSkill
- instagramSkill
- instagram-virality-insightsSkill
- marketing-cashvertisingSkill
- marketing-contagiousSkill
- marketing-going-viralSkill
- marketingSkill
- marketing-offersSkill
- marketing-storybrandSkill
- quality-checkSkill
- elements-of-styleSkill
- style-clarity-graceSkill
- writer-styleSkill
- writing-docsSkill
- writing-proseSkill
- writingSkill
- writing-technicalSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Prefer data density: the plot carries most of the frame.
- Distinctive: line 70
Prefer no in-SVG title when HTML title exists (duplicate titles waste height on mobile).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mobile blog chart visual
Job: Blog/article charts readable at ~390×844 and useful at ~720–880 article width. Mobile floors are a floor, not a reason to explode type. Prefer data density: the plot carries most of the frame; labels wrap rather than steal the plot.
Scope: Static / SSR SVG and carefully authored blog PNGs. Not product ECharts (card price matrix, portfolio history) — use mobile-app-echarts-visual.
Sources (cite when extending this skill)
| Source | What we take |
| Nadieh Bremer — Mobile vs desktop dataviz | Technique ladder: scale (non-linear fonts), fit width, stack/horizontal rows, reposition, or two charts — no one-size-fits-all |
| Responsive SVG charts — viewBox pitfalls | Uniform viewBox scale stretches text; floors/caps required |
| Constant font size in responsive SVGs | Industry workarounds for label size under scale |
| Tableau — mobile dashboard design | Simple marks, fewer chrome layers, high-level stats |
| Tufte (data-ink / density) | Plot share ≥ ~0.48; empty gutters = defect |
Core formula (always)
rendered_css_px ≈ paint_width × (fontSize_user_units / viewBoxWidth)
min_fontSize(role) = ceil(TARGET[role] × viewBoxW / 332)Design width 332px (390 viewport, padded figure).
| Role | Soft floor @ 332 | Soft cap @ ~720 |
Title (prefer HTML h3 text-base+, not in-SVG) | 13 | — |
| Category / row label | 11 | ≤ ~24 |
| Value tip | 11 | ≤ ~22 |
| Axis tick | 10 | ≤ ~20 |
| Source | 10 | — |
Squint: ≤~9px @ 332 → fail. Oversized: labels >~24px @ 720 or plot share < 0.48 → fail density.
Data density
| Rule | Pass |
| Plot share | plotW / viewBoxW ≥ ~0.48 |
| Wrap over pad | ≤ 11 chars/line (forces “Umbreon VMAX”-class wrap) |
| Row pitch | ~1.7× (1 line) / ~2.15× (2 lines) |
| Bar thickness | ~0.4–0.5 of rowH |
| Values | Fixed right column (textAnchor=end), not tip-after-full-bar |
| Char width | Label 0.62×, value 0.65× (Inter 600 — not 0.55 regular) |
Chart title rule (hard)
- One title only: HTML heading immediately above the figure (
h3/ section title). - No subtitle under that title (no second line restating the axis or “Figure N: …” above the plot).
- Captions / sources below the plot only (
Source: silphcoanalytics.xyz, one insight sentence). - Prefer no in-SVG title when HTML title exists (duplicate titles waste height on mobile).
Hard bans
max-h-*crushing aspectoverflow-hiddenon chart frames that clips labels/tips- Tip-after-bar without reserved right column
- Synthetic-only unit tests (must use real strings:
$140M,Umbreon VMAX) - Chart subtitles after the title
Workflow
- List every figure in the article.
- Record viewBoxW, fonts, pads, plot share, frame classes.
- Soft floors + wrap + fixed value column.
- Assert plot share + desktop soft caps.
- Strip subtitles; source under plot.
- Verify 390 and desktop.
- e2e: blog geometry probe (see verification.md).
Verification (V1–V14)
See references/verification.md. Critical:
| # | Check |
| V5/V13 | No clip; longest tip complete |
| V11 | Plot share ≥ 0.48 |
| V12 | Desktop soft cap |
| V14 | No overflow-hidden clip |
| V15 | No subtitle under title |
Hand off
| Need | Skill |
| Product ECharts (card/portfolio) | mobile-app-echarts-visual |
| Chart type honesty | tufte |
| Sticky chrome / buttons | product-chrome-craft / product-ui-craft |
| Browser e2e | browser-verify |
Done criteria
- V1–V3, V11–V15 at dual viewports
- Real-string unit tests green
- Blog geometry e2e green (or documented skip with reason)
- Live mobile screenshot: no clip, no subtitle under title
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.