tufte-test
Review charts with a simple Tufte-style rubric. Use when judging whether a chart is clean, honest, readable, and insight-forward, or when iterating on a visualization until it passes a concise quality bar.
What this skill does
# Tufte Test
Use this skill to review a chart locally with a lightweight Tufte-style rubric.
This skill is intentionally simple:
- no external API
- no required scripts
- works from either a chart image or chart code/config
## When to use
- "Does this chart pass a Tufte-style review?"
- "Review this visualization"
- "What should I fix in this chart?"
- "Keep improving this chart until it passes"
## Inputs
This skill works with either:
- a rendered chart image or screenshot
- chart code/config that implies the rendered output
Prefer reviewing the rendered chart when available. If only code is available,
infer the likely output and call out uncertainty.
## Core rubric
Evaluate the chart against these 7 checks:
1. **Data-ink ratio**
- Pass if non-data decoration is minimal.
- Fail for heavy gridlines, ornamental borders, redundant legends, textures,
shadows, gradients, or other chartjunk.
2. **No 3D effects**
- Pass if marks are flat 2D.
- Fail for perspective, extrusion, bevels, or depth effects.
3. **Direct labeling**
- Pass if series/categories are labeled on or near the marks when practical.
- Fail if the chart depends on a separate legend where direct labels would fit.
4. **Axis readability**
- Pass if axis text is legible and units/context are clear.
- Fail for missing labels/titles when needed, cramped ticks, rotated text that
hurts readability, or unclear units.
5. **Muted, purposeful color**
- Pass if color is restrained and used to guide attention.
- Fail for loud rainbow palettes, highly saturated fills everywhere, or color
choices that do not communicate meaning.
6. **Integrated annotations**
- Pass if the chart includes a clear takeaway through title, subtitle, or
annotation when the data warrants it.
- Fail if the chart is purely descriptive and misses the key insight.
7. **Graphical integrity**
- Pass if scales and visual encodings are honest.
- Fail for misleading truncation, distorted proportions, broken baselines,
inconsistent scales, or other deceptive framing.
## Pass rule
The chart passes only if all 7 core checks pass.
If one or more checks fail, the overall result is `pass: false`.
## Review workflow
1. Inspect the rendered chart if available.
2. Score each of the 7 checks as PASS or FAIL.
3. Give a one-paragraph summary.
4. List only the failed checks.
5. Suggest the smallest set of concrete fixes needed to pass.
6. If asked to iterate, revise only the failed areas and re-review.
## Response format
Use this exact structure when possible:
```yaml
pass: false
checks:
data_ink_ratio: pass
no_3d_effects: pass
direct_labeling: fail
axis_readability: pass
muted_purposeful_color: pass
integrated_annotations: fail
graphical_integrity: pass
summary: "Clear and honest overall, but it still relies on a legend and lacks an integrated takeaway annotation."
failed_checks:
- direct labeling
- integrated annotations
fixes:
- "Replace the legend with direct labels on the marks or line endpoints."
- "Add a subtitle or annotation that states the main takeaway."
uncertainty: "Low"
```
If reviewing from code rather than an image, include an `uncertainty` note such as
`Medium` or `High` when the rendered result cannot be confirmed.
## Revision guidance
When suggesting fixes, prefer minimal edits:
- remove chartjunk before changing chart type
- replace legends with direct labels
- soften color before recoloring everything
- add one strong annotation before adding many notes
- fix misleading scales before polishing style
If the chart type itself is the problem, say so directly and recommend a better
alternative.
## Reference
For the expanded checklist, see:
- `references/rubric.md`
- `references/rules/01-data-ink-ratio.md`
- `references/rules/02-no-3d-effects.md`
- `references/rules/03-direct-labeling.md`
- `references/rules/04-axis-readability.md`
- `references/rules/05-muted-purposeful-color.md`
- `references/rules/06-integrated-annotations.md`
- `references/rules/07-graphical-integrity.md`
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.