Tip Slides

tip-slides — tip of the day as a slide deck

Overview

The same tip the tip skill gives (shared catalog, shared shown history, shared numbers), laid out as a deck of one or more slides. The guiding principle: every slide and every visual element answers a specific question the reader has. A slide that answers no question is not made; a visual without which the tip is understood just as fast is not drawn.

Facts come only from the tip text that tip.sh printed. A diagram or a table must not contain keys, commands, flags or steps that are not in the tip.

State at invocation

${CLAUDE_SKILL_DIR}/tip.sh list

Invocation argument: "$ARGUMENTS"

If the state block above is missing, run ${CLAUDE_SKILL_DIR}/tip.sh list yourself.

Steps

1. Get the tip — one per invocation:
   • the argument is a number → ${CLAUDE_SKILL_DIR}/tip.sh show <number> <ticket> (an already shown tip is fine);
   • otherwise choose an id from the unseen list (the topic from the argument; with no argument, what is useful for the current session; in an empty session, a topic that is not in the "recently shown" line) and run ${CLAUDE_SKILL_DIR}/tip.sh take <id> <ticket>;
   • EXHAUSTED → say there are no unseen tips left and suggest /tip refresh.
2. Plan the deck with "How many slides" and "Does it need a visual" — before creating anything.
3. Build the deck — section "Publishing".
4. Reply — section "Reply format".

Everything the reader sees — slide text, labels, the reply — is in the language of the lang: line (reply-lang in the take output); see "Language" in the tip skill for the labels and for the one-time language offer.

How many slides

The content of the tip decides the number of slides, not a wish to "make a presentation":

The upper bound is 5. The first slide is always #<number> · <title as a statement> with the point in one or two sentences. The last content element of the deck is always the "try it now" block with the exact action; in a one-slide deck it sits on that slide. Every slide title is a statement, not a heading ("Ctrl+S stashes the prompt and brings it back", not "Description").

Does it need a visual

For each slide ask the questions in the left column. A "yes" → the matching form. No "yes" at all → a text slide, and that is a perfectly good result.

The control question for every visual: "would the reader understand the tip just as fast without it?" If yes, remove it. Icons, illustrations, emoji and background effects always answer "yes".

Color carries meaning (the difference, the current state) rather than decoration: one accent color per deck. Commands and keys are set in a monospace face.

Series look

Every deck looks like part of one series and is built for a dark theme — the look is not reinvented each time:

The Slides artifact type accepts only fixed hex colors, so the palette there is always dark. The HTML template of the fallback path switches between light and dark with the system theme — leave its tokens alone.

Publishing

1. The main path is the Artifact tool: call action: "quickstart" with intent: "slides", create an artifact from the Slides type it names, titled Tip #<number> — <short title> (in the reply language), and fill it strictly by the instructions that creating the type returns. Do not ask for a design system — "Series look" replaces it. Build diagrams by the type's own references (artifact-type/reference/diagrams.md, and diagram-recipes.md when needed): boxes and labels are separate <p> elements with exact coordinates inside one host, lines are <x-connector>, there is no text inside <svg>; a <span> can change color only, so a keycap is its own painted <p>, never a fragment of a line.
2. When the session has no Artifact tool (as in claude -p), copy ${CLAUDE_SKILL_DIR}/deck-template.html to <slides dir>/<number>-<id>.html, where ${CLAUDE_SKILL_DIR}/tip.sh slides-dir prints the slides directory, and fill it in: keep the styles, color tokens and navigation script as they are and use the ready-made classes (.keys, .term, table, .cols, .diagram, .try), so that all decks look like one series. Check each slide with a screenshot (a #2 in the address opens the second slide), then open the file with open. For a complex diagram in HTML load the artifact-diagramming skill, for a numeric scale dataviz.

The tip is already marked as shown in step 1; if publishing fails, say so and name the number so the deck can be rebuilt with /tip-slides <number>.

Reply format

Brief, in the reply language, in this order:

1. The title: **Tip of the day #<number>: <title>**.
2. One or two sentences with the point.
3. **Try it now:** the action from the tip, with real names from the current project when you know them. Claim only what you verified about the user's settings and files, and do not suggest setting up something they already have.
4. The link to the deck (or the file path) and the number of slides.
5. A Visuals: line — one item per visual element: its form and which question from the table it answers; or "none — the tip is a single fact, a diagram would add nothing".
6. The footer in italics: <topic> · #<number> · shown N of M.

Common mistakes