Claude prompt for data analysis: Dashboard Spec (Advanced)
Claude · Data Analysis · Advanced
You are a pragmatic coach using Claude for data analysis, specifically dashboard spec.
Job: who, questions, tiles.
Audience: bi. Constraint: no vanity charts.
Working style: precise and demanding. Optimize for constraints, evaluation, and edge cases.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.This Claude data analysis dashboard spec prompt helps you who, questions, tiles without rewriting instructions from scratch each time. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
When to use this prompt
When bi tackle dashboard spec inside data analysis, the hard part is not the model — it is the brief. Queries, insights, charts, and decision memos. This prompt encodes that context so Claude does not guess. Bookmark this page if you run dashboard spec weekly.
Why this prompt works
- Separates draft from critique so you can steal the structure later.
- Repeats the hard constraint: no vanity charts.
- Locks the audience (bi) before style so tone stays honest.
- Forces an output contract: headings, examples, and a final version.
- Keeps data analysis vocabulary specific instead of buzzwords.
How to use it in Claude
When bi review output, they should see constraints, evaluation, and edge cases without hunting for it. Queries, insights, charts, and decision memos. Keep that context in the thread when you iterate. Save the winning variant for dashboard spec — teams with a short library ship faster. Add one real example from your last week of work so the model mirrors your domain. This Advanced path is for bi who care about who, questions, tiles.
Start with the ugly first pass for dashboard spec. Name what is wrong in five bullets, then rerun in Claude. For dashboard spec in data analysis, the failure mode is usually no example. This prompt blocks that by design — especially "no vanity charts". Expect two minutes customizing and two minutes editing for Advanced output. Anthropic models still need your facts for dashboard spec; they cannot invent metrics or brand rules. analysts and operators teams bookmark slug dashboard-spec-advanced when constraints, evaluation, and edge cases matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (bi, offer, timeline).
- Confirm the constraint is still visible: no vanity charts.
- For data analysis work, paste a rubric and ask for a self-score.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Dashboard Spec, 3 short sections, bullet list of recommendations, closing line that states no vanity charts. Facts you supply appear; nothing invented.
Common mistakes
- Asking for dashboard spec plus three other jobs in one message.
- Deleting "no vanity charts" to save space — that is usually the whole point.
- Skipping the audience (bi) and hoping Claude infers it.
Expert notes
Anthropic users working on dashboard spec in data analysis should treat "no vanity charts" as non-negotiable. Queries, insights, charts, and decision memos. When bi run the Advanced variant, they usually care about constraints, evaluation, and edge cases more than length.
If text output feels generic, re-paste no vanity charts as the first follow-up message — do not rewrite the whole prompt.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a dashboard spec piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Ship a draft, then tighten. Do not chase a perfect first token.
- Keep no vanity charts visible in the prompt, not only in your head.
- Document what changed when you customized slug dashboard-spec-advanced.
- bi should recognize themselves in the first paragraph.
- Compare against other Claude angles on the same use case before you standardize.
FAQ
- What is a Claude prompt for dashboard spec?
- It is a structured brief that tells Claude how to produce data analysis output for bi. This advanced version stresses constraints, evaluation, and edge cases and keeps "no vanity charts" in the instructions.
- How do I customize this Claude data analysis prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "no vanity charts" should stay unless your brief truly changed.
- Why use the advanced angle for dashboard spec?
- Different angles solve different failures. Advanced helps when bi need constraints, evaluation, and edge cases. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.