Back to Skills & Tools Dashboard Builder

Turn the messy question into a screen you can point at.

This is the showpiece example for the dashboard skill. It takes the creative strategist question everyone argues about in Slack and turns it into one decision screen.

Open the live dashboard Open the pattern picker
Creative Strategy Diagnostics dashboard preview.

The dashboard loop

Six checks before the page earns trust.

The skill is built for first dashboards, where the data is usually messy and the request is usually vague. It forces the decision into a sentence before design starts.

  1. Name the decision

    Who uses it, and what should they decide after reading it?

    If this sentence is fuzzy, the dashboard turns into decoration.

  2. Check the data

    What is trusted, what is stale, what is sample, and what is not counted yet?

    The dashboard is only as useful as the data it refuses to fake.

  3. Pick the lane

    Choose the screen shape based on the job, not based on a pretty layout.

    A review queue, a revenue map, and an evidence board should not look identical.

  4. Build the first page

    Make the smallest working screen with sample data that renders when opened.

    A page that opens blank is not done.

  5. Swap in real material

    Replace sample rows and prop images with the actual rows, screenshots, or deliverables.

    The shape can be sample. The decision cannot stay pretend.

  6. Run the check

    Use a pass or fail checklist before trusting the dashboard.

    A dashboard can look finished and still mislead the person using it.

Visual proof

The output should look like a real tool.

The pattern picker teaches how the skill chooses a screen shape. The live dashboard shows the finished artifact: data, visuals, and the next move on one page.

Creative Strategy Diagnostics dashboard preview.
Live decision dashboard
Dashboard Builder pattern picker preview.
Pattern picker
Full Creative Strategist dashboard preview.
Design brief + artifact

Dashboard lanes

Different decisions need different screens.

A review queue, a revenue screen, and an evidence board should not share the same layout. The skill chooses a lane so the page matches the job.

Client review

Approve the work?

Shows promised deliverables, status, proof links, blockers, and the next review action.

Ad decision

Scale, pause, or inspect?

Compares creative performance, confidence, spend, and the artifact that caused the result.

Revenue movement

What should we fix first?

Surfaces movement, bottlenecks, the likely driver, and the first action worth taking.

Ops readiness

What is blocked?

Maps owners, dependencies, readiness, and the one thing preventing the next step.

Product behavior

Which step needs attention?

Tracks funnel steps, user behavior, drop-off, and where a product change should focus.

Research evidence

What do we recommend?

Shows sources, confidence, contradictions, and the recommendation the evidence supports.

Paste-along starter prompt

Use the dashboard-setup skill. I want a weekly dashboard that helps me decide whether to approve a client's work for the week.

I trust my project tracker and the review links.
I do not trust unconfirmed chat updates yet.
One row is one promised deliverable.

What to notice

The skill labels what it cannot trust.

That is the teaching point. A dashboard can look expensive and still mislead the person using it. The trust layer comes first.

Install the workspace first.

Once the Script, memory map, and skills are in place, dashboard building becomes a normal use case instead of a separate trick.

Start with setup
← Back to home base