Get Smith output into the other tools you already use. A note on how this works today: Smith writes the content and you copy it into the destination app; Smith generating downloadable files for you is coming soon, and each recipe notes this where it applies. This is one of the 6 Recipe categories. Each recipe below opens to reveal its full steps, an example, and a live demo you can run. Filter by effort if you want the quicker ones first.
Get Smith output into the tools you already use
What is a recipe?
A recipe is a short, numbered sequence that combines a few moves into a repeatable result. Each one below opens to reveal its purpose, when to use it, the full steps, an example, and a live demo. For single one-prompt moves, see the Playbook. Recipes are grouped into 6 categories; this article is one of them.
The Recipes
Each recipe is collapsed by default. Click one to expand its purpose, when to use it, the numbered steps, an example, and a demo you can run right there. The badge shows the effort.
Build an HTML page you can save and open a real, openable web page without writing code Few steps ▸
Purpose: Need a simple web page or formatted document and do not want to hand-code it. Smith writes the HTML; you paste it into a text file and save it with an .html extension.
When to use this: A quick landing snippet, a formatted standalone page, or an HTML email body.
| # | What you do | What you should see |
|---|---|---|
| 1 | "Write a complete, self-contained HTML page for [purpose] with inline styles" | A full HTML document in the chat |
| 2 | "Use these colors, fonts, and sections", give your brand | Styled to spec |
| 3 | Copy the code, paste into a plain text file, save as page.html | A file on your computer |
| 4 | Open it in a browser; ask Smith to tweak anything off | A working page |
You end up with: a real, openable web page without writing code.
Generate a Confluence page a structured wiki page in a fraction of the time Few steps ▸
Purpose: Stop hand-formatting wiki pages. Smith outputs Confluence-friendly markup (headings, tables, links, panels) you paste into a new page.
When to use this: Creating or updating team documentation in Confluence.
| # | What you do | What you should see |
|---|---|---|
| 1 | "Format this as a Confluence page: headings, a table, and links" | Structured markup |
| 2 | Give it the raw content to format | Organized into sections |
| 3 | Paste into a new Confluence page (Insert > Markup) | A formatted page |
| 4 | "Add a table of contents macro at the top" | Polished |
You end up with: a structured wiki page in a fraction of the time.
Write a Jira ticket (or a whole batch) clean, consistent tickets instead of one-line stubs Few steps ▸
Purpose: Turn a vague request or a meeting note into properly structured Jira tickets, summary, description, acceptance criteria, ready to paste in.
When to use this: Converting feature ideas, bug reports, or meeting notes into real tickets.
| # | What you do | What you should see |
|---|---|---|
| 1 | Paste the feature idea, bug report, or notes | Smith has the raw input |
| 2 | "Write this as a Jira ticket: summary, description, acceptance criteria" | A structured ticket |
| 3 | "Now split this into 4 separate tickets" if it is big | A batch of issues |
| 4 | Paste each into Jira | Tickets created |
You end up with: clean, consistent tickets instead of one-line stubs.
Write Azure DevOps work items a ready-to-load backlog, not a wall of text Few steps ▸
Purpose: Convert loose requirements into properly formed user stories and tasks with acceptance criteria, for ADO shops.
When to use this: Breaking an epic or requirement doc into a structured backlog.
| # | What you do | What you should see |
|---|---|---|
| 1 | Paste the requirement or epic description | Smith has it |
| 2 | "Break this into ADO user stories with acceptance criteria in Given/When/Then" | Structured stories |
| 3 | "Add child tasks under each story" | A work breakdown |
| 4 | Paste into ADO | Work items ready |
You end up with: a ready-to-load backlog, not a wall of text.
Craft a formatted Slack or Teams message an announcement people read instead of scroll past Quick ▸
Purpose: Announcements and updates that are actually readable, bold, bullets, sections, instead of a paragraph nobody reads. Smith writes it in the right format to paste in.
When to use this: Any team announcement, update, or call to action you post in a channel.
| # | What you do | What you should see |
|---|---|---|
| 1 | "Write a Teams announcement about [X]: scannable, bold headers, short bullets" | A formatted message |
| 2 | "Make it warmer / shorter / add a clear call to action" | Tuned |
| 3 | Paste into the channel | A clean post |
You end up with: an announcement people read instead of scroll past.
Generate a Word-ready document outline a Word doc that's 80% done before you open Word Few steps ▸
Purpose: Build a fully structured document, headings, sub-points, formatting cues, that pastes cleanly into Word and keeps its structure.
When to use this: Drafting any longer document you will finish in Word: a report, a proposal, a policy.
| # | What you do | What you should see |
|---|---|---|
| 1 | "Draft this as a structured document with H1/H2/H3 headings and body text" | A hierarchy |
| 2 | "Add a title line, a summary, and a conclusion" | Complete shape |
| 3 | Paste into Word; headings carry over | A formatted doc |
| 4 | "Suggest where a table or callout would help" | Refinement notes |
You end up with: a Word doc that's 80% done before you open Word.
Produce spreadsheet-ready data (CSV / Excel) structured data in a spreadsheet without manual entry Few steps ▸
Purpose: Turn messy notes or text into clean rows and columns you paste straight into Excel. Smith does the structuring; you do the analyzing.
When to use this: Any time you have unstructured information that belongs in a spreadsheet.
| # | What you do | What you should see |
|---|---|---|
| 1 | Paste the unstructured info | Smith has it |
| 2 | "Organize this into a table with these columns: [...]" | A clean table |
| 3 | "Output as CSV" | Comma-separated text |
| 4 | Paste into Excel or Sheets, or save as a .csv file | A populated sheet |
Send invites,Priya,Thu,Not started
Draft memo,Marcus,Q3,Not started
You end up with: structured data in a spreadsheet without manual entry.
Suggest Excel formulas and logic the formula you needed, and you understand why it works Quick ▸
Purpose: You know what you want the spreadsheet to do but not the formula. Smith writes it and explains it, so you paste it into the cell and move on.
When to use this: Any time you are stuck on an Excel or Sheets formula.
| # | What you do | What you should see |
|---|---|---|
| 1 | Describe what you need: "sum column B where A = closed" | Smith understands |
| 2 | "Give me the Excel formula and explain it" | A formula plus plain-English logic |
| 3 | "Now make a version with error handling" | A robust version |
| 4 | Paste into the cell | It works |
You end up with: the formula you needed, and you understand why it works.
Structure a OneNote / note page a tidy reference page instead of a wall of scribbles Quick ▸
Purpose: Turn a brain-dump into an organized note page with clear headings and checklists you paste into OneNote or any notes app.
When to use this: After a brainstorm or research session, when your notes are a mess.
| # | What you do | What you should see |
|---|---|---|
| 1 | Dump everything on a topic | Smith has the raw notes |
| 2 | "Organize into a note page: headings, bullets, and a checklist of actions" | A structured page |
| 3 | Paste into OneNote | An organized note |
You end up with: a tidy reference page instead of a wall of scribbles.
Build a PowerPoint presentation a deck outlined and written, ready to drop into PowerPoint Few steps ▸
Purpose: Stop staring at a blank deck. Smith writes everything that goes on the slides, titles, bullet content, and speaker notes, organized slide by slide, so you paste it into PowerPoint and focus on design.
When to use this: Any presentation where the thinking and the words are the hard part, and you just need the structure and content laid out.
| # | What you do | What you should see |
|---|---|---|
| 1 | "Outline a [N]-slide deck on [topic]: title and key points per slide" | A slide-by-slide outline |
| 2 | "For each slide, give the title, 3-4 bullet points, and speaker notes" | Full content per slide |
| 3 | "Suggest where a chart or image would strengthen each slide" | Visual cues |
| 4 | Create the slides in PowerPoint and paste each slide's title, bullets, and notes into place | A built deck |
You end up with: a deck outlined and written, ready to drop into PowerPoint.
Draft a Canva-ready content plan all the words your design needs, organized to drop in Few steps ▸
Purpose: Canva handles the visuals; Smith handles what goes on them. Get every text element, headlines, body, captions, CTAs, organized per slide or graphic.
When to use this: Building a carousel, poster, or one-pager in Canva and needing the copy laid out.
| # | What you do | What you should see |
|---|---|---|
| 1 | "I am making a [carousel/poster/one-pager] in Canva about X" | Smith understands the format |
| 2 | "Give me the text for each element: headline, subhead, body, CTA" | Copy blocks per element |
| 3 | "Now a punchier alternative for each" | Options |
| 4 | Drop the copy into your Canva design | A filled design |
You end up with: all the words your design needs, organized to drop in.
Write a README or Markdown doc a professional README without formatting fuss Quick ▸
Purpose: Clean Markdown for a README, internal doc, or any .md file, proper headings, code blocks, links, that you paste into a text file or repo.
When to use this: Documenting a project or writing any Markdown-based doc.
| # | What you do | What you should see |
|---|---|---|
| 1 | "Write a README in Markdown for [project]: overview, setup, usage" | Markdown source |
| 2 | "Add a features table and a badges line" | Enriched |
| 3 | Paste into a .md file | A rendered doc |
## Setup
1. Install...
## Usage
You end up with: a professional README without formatting fuss.
See a Full Workflow in Action
These recipes chain naturally. Here is a single deliverable built across three of them, structured data, a written deck, and an announcement.
Three tool recipes, one deliverable
Watch several of these recipes run together as one continuous flow.
Next Steps: Open one recipe and run it end to end today. For single one-prompt moves, browse the Playbook. Working through your first month? The First 30 Days plan tells you which recipes to use each week.
Related Articles
Recipes 4: Recurring Habits
The next category of multi-step recipes.
Recipes 2: Communications
The previous category of recipes.
The Playbook
Looking for single one-prompt moves instead?
Comments
0 comments
Article is closed for comments.