Start from a real example.

Say to @WalleBuild a pitch deck artifact for [company/idea]. Structure it as a multi-page site: index.html is the cover slide (company name, one-line promise), then one HTML page per slide — problem, solution, product, market, traction, team, ask — linked by next/previous nav. Bold typography, one idea per slide, consistent accent color. Add print CSS so each slide page-breaks to its own PDF page. Pull real numbers from my connected tools where you can.

Say to @WalleBuild a KPI dashboard artifact with our key weekly numbers: [metrics]. Pull the current values from my connected tools, render big stat cards with week-over-week deltas (green up, red down), a short "what changed" note under each, and a last-updated stamp. Then set it to refresh every Monday morning so the same link always shows current numbers.

Say to @WalleBuild a meeting-prep dossier artifact for my meeting with [person/company]. Sections: who they are (role, background), our email history summarized as a timeline, recent company news from web search, open threads between us, and five suggested talking points. Keep it one page, scannable in ninety seconds.

Say to @WalleBuild a project status artifact for [project]. Pull current state from my trackers: done this week, in progress, blocked (with owner), risks with severity chips, and the decisions we need. Top it with a one-paragraph executive summary and a simple progress bar. Stakeholder-ready tone.

Say to @WalleRun the GTM hunt from our guides and publish the result as an artifact: index.html with the ranked account table (company, fit score, the signal that fired) plus one page per top-5 account with the full evidence and a specific entry angle. Share-ready for the sales team.

Say to @WalleDraft a PRD artifact for [feature]. Sections: problem and evidence, goals and non-goals, user stories, functional requirements as a checklist table, success metrics, open questions. Pull any relevant context from my notes and docs. Crisp product voice, no filler.

Say to @WalleBuild an invoice artifact: [client, line items, rates]. Clean layout with our name and logo placeholder, invoice number and dates, line-item table with subtotal, tax, and total, payment details, and print CSS so it exports to a tidy single-page PDF.

Say to @WalleBuild a weekly digest artifact covering [team/topic]: the five things that mattered this week from my inbox and trackers, each with a two-sentence summary and a link; one chart or number of the week; and what to watch next week. Magazine-ish layout, forwardable.

Say to @WalleBuild a launch announcement artifact for [product/feature]: hero with the one-line promise, three benefit blocks with icons, a how-it-works strip, an FAQ, and a call-to-action. Confident marketing voice, tasteful gradients, mobile-responsive.

Say to @WalleBuild a vendor comparison artifact for [tools being evaluated]. Research each with web search: a criteria matrix (pricing, capabilities, integrations, support) with scores, a short verdict per vendor, and a clear recommendation with reasoning at the top. Decision-ready for the team.

Say to @WalleBuild a roadmap artifact from my tracker: lanes per workstream, cards per initiative placed by quarter, status colors (shipped, in progress, planned), and a "recently shipped" strip at the top. Keep it readable at a glance for execs.

Say to @WalleBuild a postmortem artifact for [incident]. Sections: summary and impact (who, what, how long), a minute-by-minute timeline reconstructed from my messages and alerts, root cause with the five whys, what went well, and action items as a table with owners and due dates. Blameless tone.

Say to @WalleBuild an all-hands deck artifact for [month]: cover, the numbers slide with our KPIs and deltas pulled from my tools, what shipped (from the trackers), customer voice slide with a real quote, shout-outs, and next month's focus. One slide per page with next/prev nav and arrow-key navigation via a small app.js; print CSS so it exports one slide per PDF page.

Say to @WalleBuild a sales demo deck artifact tailored to [prospect]: cover with their name, their problem in their industry's language, our approach in one diagram slide, a demo-flow slide per key capability, proof (logos, numbers, quote), pricing summary, and next steps. One slide per page, arrow-key nav, print CSS for the leave-behind PDF.

Say to @WalleBuild a conference talk deck artifact on [topic]: title slide, a narrative arc of one idea per slide with BIG statement typography (no bullet walls), code or diagram slides where the content demands it, and a closing slide with the takeaway and my handle. Add a hidden notes.html page with speaker notes per slide. Arrow-key navigation, print CSS.

Say to @WalleBuild a training deck artifact for teaching [skill/process]: agenda slide, sections of 3-5 slides each (concept, example, common mistake), an exercise slide per section, and a recap quiz page at the end. Number every slide, arrow-key nav, print CSS for handouts.

Say to @WalleBuild a project kickoff deck artifact for [project]: cover, why-now slide, goals and non-goals, scope in/out table slide, roles (RACI) slide with names from my notes, timeline with milestones, top risks with mitigations, and the communication plan. One slide per page, arrow-key nav, print CSS.

Say to @WalleBuild a retrospective deck artifact for [sprint/quarter]: the goals we set vs what happened (honest deltas from the trackers), what went well, what did not, the lessons as crisp one-liners, and the concrete process changes we commit to with owners. One slide per page, arrow-key nav.

Say to @WalleBuild a board update artifact for [period]: cover page, metrics page with the KPI table and deltas pulled from my tools, highlights page, lowlights page (honest, with mitigation), cash and runway, and an asks page. One page per section with nav, print CSS for PDF. Investor-grade tone, no fluff.

Say to @WalleBuild a QBR deck artifact for [customer]: cover, usage and value recap pulled from our data, wins this quarter, open issues with status, roadmap preview relevant to them, and next-quarter goals. One slide per page, their name throughout, print CSS for PDF.

Say to @WalleBuild a sales one-pager artifact for [product, aimed at persona]: the pain in their words, how we solve it in three bullets, one proof point or customer quote, pricing summary, and a clear next step. Print CSS for a clean single-page PDF leave-behind.

Say to @WalleBuild a case study artifact about [customer]: their context, the problem in their words, what we deployed, and the results with real numbers (pull from my notes and threads with them). Include one strong pull-quote. Classic challenge → solution → results layout.

Say to @WalleBuild a proposal artifact for [client and engagement]: summary of their goals, our approach, deliverables as a table, timeline with milestones, team, commercial terms, and assumptions. Multi-page with a cover; formal but human tone; print CSS for PDF.

Say to @WalleBuild an OKR tracker artifact from our objectives: each objective as a card with its key results as progress bars (current vs target from my trackers), confidence chips, and an owner. Add a weekly refresh schedule so the link stays current.

Say to @WalleBuild a competitive teardown artifact on [competitor]: their product surface, pricing and packaging (web-researched, cited), positioning and messaging analysis, strengths honestly assessed, exploitable weaknesses, and how we win against them. Index page with the verdict, detail pages per section.

Say to @WalleBuild a market map artifact for [space]: segment the landscape, place the notable players in each segment with one-line descriptions (web-researched), mark where we sit and why our segment wins, and finish with the three trends reshaping the map.

Say to @WalleResearch [question] across the live web and build a brief artifact: the answer up front in three sentences, the evidence organized by theme with citations linked, counterpoints taken seriously, and what we should do about it. Analyst tone.

Say to @WalleBuild a research readout artifact from my interview notes on [topic]: the five themes with supporting quotes, a severity/frequency matrix, surprises, and ranked product recommendations. Anonymize participants. Lead with the so-what.

Say to @WalleDraft a press release artifact for [announcement]: headline and subhead, dateline lede, two body grafs with the substance, a founder quote and a customer quote, and company boilerplate. Newsroom formatting, AP-ish style.

Say to @WalleBuild a content calendar artifact for [month/channel]: a week-by-week grid of planned pieces with title, format, owner, status chip, and target date; a themes legend; and a backlog strip of ideas at the bottom. Pull anything already planned from my notes.

Say to @WalleBuild an event brief artifact for [event]: goals, attendee list from my calendar invites, day-by-day agenda as a timeline, logistics (venue, travel, links), and open items with owners. One page everyone can bookmark.

Say to @WalleBuild an onboarding guide artifact for a new [role]: welcome page, who-is-who with what to ask each person about, our tools and how to get access, weekly rituals, how we work (norms), and their first-two-weeks checklist. Multi-page with nav; warm but direct.

Say to @WalleBuild a job description artifact for [role]: why this role matters here, what you will do (outcomes, not tasks), what great looks like at 90 days, requirements kept honest and short, comp range, and how we interview. Candidate-facing voice that sells without hype.

Say to @WalleBuild an interview scorecard artifact for [candidate/role]: the dimensions we assess with a 1-4 rubric each, space for evidence quotes per interviewer (pull any notes from my docs), red flags, and a final recommend/no-recommend with reasoning.

Say to @WalleBuild a changelog artifact from our recent shipped work (pull from my tracker): dated entries newest-first, each with a New/Improved/Fixed chip, a one-paragraph plain-language description, and a screenshot placeholder where it matters. Set a weekly refresh so it stays current.

Say to @WalleBuild API quickstart docs as a multi-page artifact for [API]: index with auth and a copy-paste first call, one page per core endpoint (request, response, gotchas) with highlighted code blocks, and an errors reference page. Developer voice, zero marketing.

Say to @WalleBuild a runbook artifact for [procedure]: preconditions, the steps as a numbered checklist with exact commands in code blocks, verification checks after each phase, rollback instructions, and who to page when it goes sideways. Battle-tested tone.