We made all of these
in Claude Design.

P0 · Design-system priming

Run this once at the very start of the session to "prime" the design system.

I'm about to generate a series of slides for the MIXI Executive Workshop. Apply the following design system to every slide you generate for the rest of this session.

## Brand
- Company: MIXI
- Tone: "The Corporate Warmth" — enterprise trust plus approachability, white base with MIXI RED accents
- Audience: executives (board and officer level)

## Color palette (MIXI Slide Kit)
- Background: #FFFFFF (white)
- Text (primary): #282828 (do not use pure black #000)
- Text (muted): #9A9A9A
- Accent (primary): #E5004D (MIXI RED)
- Accent (secondary): #F5A000 (MIXI ORANGE — do not use RED and ORANGE together on the same slide)
- Callout background: #F5F5F5 (gray, 16px radius)
- Success: #1F7A3F / Warning: #F5A000 / Danger: #D85858

## Typography
- Font: Noto Sans JP only (Regular 400 + Bold 700, two weights)
- Body: line-height 1.4–1.8 for breathing room
- Heading 62–100px Bold / body 28–32px Regular (slide baseline)

## Layout principles (subtractive accent)
- One slide, one accent color (never RED and ORANGE competing on the same slide)
- Generous whitespace (96px minimum margins, 80–120px between sections)
- One slide, one message — at most 5–6 lines of content
- Group horizontal elements in cards (#F5F5F5, 16px radius, 32px padding)

## Things to avoid
- Carrying decorative color into the content area (decoration stays inside the template frame)
- Bright-colored callout backgrounds (gray #F5F5F5 only)
- More than 7 bullets on a single slide
- Pure black #000000, or over-using bold (at most one bolded phrase per sentence)

If you understand, just reply with one line: "Design system primed." Every slide after this follows these rules.

P1 · Opening hero slide

Generate one hero slide for the opening of the workshop.

## Composition
- Full-screen, left-aligned
- Small eyebrow text (top): "90-MINUTE EXECUTIVE WORKSHOP · 2026 APRIL"
- Huge Japanese-style title: "Claude, in the hands of the executive team."
- Subtitle (2 lines): "Claude Code Desktop / Claude Design / Claude Cowork — experience the three pillars of Claude's April 2026 lineup in 90 minutes."
- Bottom right, small: "MIXI Executive Workshop · 2026.04"

## Decoration
- Faint coral blur gradient in the top-right corner (opacity 10%)
- A short 40px coral line underneath the title

## Tone
- Calm authority. Not festival energy — the quiet of the moment just before a board meeting begins.

P2 · 3 PILLARS comparison slide

Create one slide comparing the three Claude products we'll cover today, side by side.

## Layout
- Eyebrow at top: "3 PILLARS"
- h2: "The three Claude products we'll cover"
- Three cards of equal width underneath

## Card contents

### Card 1
- Date badge: "2026-04-14 · GA Redesign"
- Title: "Claude Code Desktop"
- Body (2 lines): "The Code tab inside the Claude Desktop app. Parallel Sessions / Plan Mode / MCP / Visual Diff — all in a GUI, no terminal required. Mac and Windows."
- Status badges: GA / Mac / Windows

### Card 2
- Date badge: "2026-04-17 · Research Preview"
- Title: "Claude Design"
- Body: "Generate pitch decks, one-pagers, and UI mockups through conversation. Opus 4.7 underneath, exports to PPTX / PDF / Canva. The product that knocked 7% off Figma's stock the day it launched."
- Status badges: Preview / Web

### Card 3
- Date badge: "2026-02-24 · GA"
- Title: "Claude Cowork"
- Body: "A non-engineer autonomous agent that runs inside Claude Desktop. Spans local files, Gmail, and Drive to self-drive multi-step knowledge work. OSWorld 72.5%."
- Status badges: GA / Mac / Windows

## Visual rules
- Cards have a 1px border — no hover state needed (static slide)
- A 2px coral accent line under each card title

P3 · 90-minute timetable

Render the 90-minute workshop timetable as a Gantt-style set of horizontal bars on a single slide.

## Composition
- Eyebrow: "AGENDA"
- h2: "90-minute timetable"
- Horizontal axis graduated 0–90 minutes
- Five bars (differentiated by varying shades of coral)

## Bars
| # | Start | Length | Label |
|---|---|---|---|
| 1 | 0 min  | 5 min  | OPENING |
| 2 | 5 min  | 40 min | PART 1 — Claude Code Desktop × ai-executive (today's main event) |
| 3 | 45 min | 17 min | PART 2 — Claude Design (two scenarios) |
| 4 | 62 min | 18 min | PART 3 — Claude Cowork deep-research |
| 5 | 80 min | 10 min | CLOSING |

## Additional rules
- PART 1's bar is a deeper coral shade for emphasis
- A one-line sub-caption under each bar (e.g. "Code tab tour · 6 API-key principles · launch · add features in natural language")
- One line at the bottom: "Format: the facilitator's laptop is mirrored to the monitor; executives follow the same steps on their own laptops."

P4 · API-key 6 principles grid

Render the six principles of API-key placement as a 3×2 card grid on a single slide. The goal: executives walk out of the room with the grid memorized as an "operating rule."

## Composition
- Eyebrow: "WORKSHOP CORE"
- h2: "🔑 Six principles of API-key placement"
- A 3-column × 2-row card grid below — six cards total

## Cards
| # | Title | Why (1 line) |
|---|---|---|
| 1 | Never paste into a chat box | May end up in the LLM provider's logs — an audit risk |
| 2 | Use a .env file | The industry standard for separating code from secrets |
| 3 | Always confirm .gitignore | Thousands of accidental GitHub leaks per year, caught instantly by auto-scanners |
| 4 | Rotate on a schedule | Bounds the blast radius of a leak by time |
| 5 | Least privilege | One agent = one key = one purpose |
| 6 | Separate prod vs dev keys | Demo keys aren't production keys — revoke after the workshop |

## Visual rules
- The card number is a large numeral (38px coral) in the top-left of each card
- Card 6 gets a heavier coral border (it's the one we'll practice live today)
- Small footer: "MIXI Executive Workshop · 2026-04"

## Style
- 8px card radius
- Background #221C15 / border #3A3128

P5 · Code Desktop feature tour

Draw a schematic of the Claude Code Desktop "Code" tab on one slide. Not a faithful UI reproduction — an abstract diagram that tells executives "what lives where."

## Composition
- h2: "Claude Code Desktop · Code tab feature tour"
- Split the screen into five regions, each with a label + one-line description

## Regions
1. Left sidebar — "Parallel Sessions" / "Multiple sessions running in parallel, isolated via Git worktrees"
2. Upper center — "Chat + Prompt" / "Natural-language instructions to Claude"
3. Middle center — "Visual Diff" / "Claude's proposed changes shown as a diff → Accept/Reject"
4. Bottom — "Integrated terminal" / "Cmd+` to open · run docker compose etc."
5. Right — "Preview" / "HTML / PDF / dev server shown live inside a pane"

## Visual rules
- Line-art tone (thin borders, subtle shading)
- Each region gets a slightly different background tint to define its boundary
- Region numbers (1–5) in coral
- One line at the bottom: "Everything in one surface. No terminal required. Mac and Windows."

P6 · ai-executive architecture diagram

Create a one-slide architecture diagram for the "minimal AI Executive tool" we'll build in the workshop. A simple data-flow diagram.

## Composition
- h2: "ai-executive (minimal version) · architecture"
- Flow reads left-to-right

## Nodes (left to right)
1. Browser (single index.html) — user enters an "agenda item"
2. FastAPI backend (app.py) — receives POST /review
3. Three parallel agent calls
   - CEO agent (system prompt: "vision execution · competitive advantage · long-term shareholder value")
   - CFO agent ("ROI, risk management, financial discipline")
   - CTO agent ("technical feasibility, scalability")
4. API calls to OpenAI (gpt-4o-mini) — three in parallel
5. Results merged into a Markdown report
6. Response returned to the browser → report rendered

## Visual rules
- Connect nodes with arrows
- Stack the three CEO / CFO / CTO nodes vertically to make the parallel execution obvious
- The OpenAI API node lives outside the system (dashed border) to separate it from internal components
- Small footer in the bottom-right: ".env manages 4 keys (default + 3 officers)"

## Note
- Make it explicit that each agent has its own key (OPENAI_API_KEY_CEO, etc.)

P7 · Claude ecosystem landscape

Summarize the entire Anthropic Claude ecosystem (as of April 2026) on a single slide, in map form.

## Section layout (3×2 or 2×3 grid)

### MODELS
- Opus 4.7 (2026-04-16, 1M ctx, $15/$75) — "NEW" badge
- Sonnet 4.6 (2026-02-17, 1M ctx, $3/$15)
- Haiku 4.5 (200K ctx, $1/$5)

### CONSUMER SURFACES
- claude.ai (Web)
- Claude Desktop (Mac/Win) — "NEW" badge
- Mobile (iOS/Android)

### CODE SURFACES
- Code Desktop tab (2026-04-14 GA redesign) — "NEW" badge
- Claude Code CLI
- Code Web
- IDE (VS Code / JetBrains)

### ANTHROPIC LABS
- Claude Design (2026-04-17 Preview) — "NEW" badge
- Claude Cowork (2026-02-24 GA) — "NEW" badge

### DEVELOPER
- Anthropic API
- Agent SDK
- MCP
- Skills

### CLOUD (Japan residency)
- AWS Bedrock (Tokyo · Opus 4.7 available from 04-20)
- Google Vertex AI (Tokyo)
- Azure Foundry

### PARTNER
- Microsoft Copilot Cowork (2026-03-10, M365)
- Claude for Word (2026-04-10 beta)

## Visual rules
- Section titles in coral
- 2026 Q1–Q2 releases carry a coral border for emphasis
- Legend at the bottom: "Orange border = released 2026 Q1-Q2"
- Footer: "Last verified 2026-04-21"

P8 · Cowork autonomous-agent loop

Visualize the Claude Cowork autonomous-agent loop on one slide. Agent at the center, six steps around it.

## Composition
- h2: "Claude Cowork · Autonomous-agent loop"
- Center: a coral circle labeled "Cowork Agent" (with a double-circle halo)
- Six step boxes arranged clockwise around it

## The six steps (clockwise from 12 o'clock)
1. Receive goal — natural-language instruction from the executive
2. Plan — lay out a multi-step plan
3. Execute — act on files, apps, the web
4. Verify — check the result, correct if needed
5. Replan — re-plan when required
6. Report — deliver the result, flag anything that needs confirmation

## Visual rules
- Connect the steps with arrows (coral, dashed)
- No line between the center node and the six steps (emphasizes that the loop lives among the steps)
- Bottom caption: "OSWorld 72.5% (2026-02) · GA 2026-02-24"

P9 · Cowork top-5 use cases matrix

Create a one-slide table of the top 5 Cowork use cases for executives, from a MIXI-specific lens.

## Composition
- Eyebrow: "EXECUTIVE USE CASES"
- h2: "Top 5 Cowork use cases for executive work"
- A 5-row × 4-column table

## Table
| # | Use case | Time saved | MIXI context |
|---|---|---|---|
| 1 | Summarize a board-pack | 2h → 10min | Night before the monthly board meeting |
| 2 | Draft earnings-call Q&A | 4h → 30min | Earnings prep, anticipated-question bank |
| 3 | Cross-analyze a DD data room | Half day → 1h | M&A / new-investment decisions |
| 4 | Weekly Gmail × Drive brief | 1h → automated | Monday-morning executive catch-up |
| 5 | Contract review | 3h → 20min | First-pass before sending to legal |

## Visual rules
- Make the "→" in the "Time saved" column coral for emphasis
- Header row: background #2B241B, coral text
- Alternate rows shaded subtly for readability
- Footer: "Full list of 20 use cases in deep-cowork.html"

P10 · ROI infographic

Visualize the ROI of Claude Code Desktop on a single slide, in a way that lands for executives. Make the numbers huge.

## Composition
- Eyebrow: "ROI"
- h2: "If one executive spends 2 hours a week in Code Desktop…"

## Three huge numbers, stepping up
- "2h" (per week) → "104h" (per year) → "the research output of 3 corporate-strategy staffers"

## Supporting info (below)
- Math: "2h × 52 weeks = 104h"
- One supporting line: "Contract review, market research, draft earnings decks — work that used to go out to external help, now done in-house."

## Visual rules
- The three numbers are ~120pt, vertically aligned
- The "→" is a coral icon arrow
- Small footer bottom-right: "Assumption: corporate-strategy headcount = 35h/week × 52 weeks = 1,820h annually"
- Background mostly empty — let the numbers do the talking

P11 · Claude vs ChatGPT vs Gemini

Lay out a three-vendor comparison of Claude / ChatGPT / Gemini on one slide, framed by the fact that MIXI already runs the ChatGPT API in production.

## Composition
- Eyebrow: "LANDSCAPE"
- h2: "Claude / ChatGPT / Gemini · a comparison for the 'add, not replace' decision"
- A 4-row × 4-column table below

## Comparison matrix
| Dimension | Claude (Opus 4.7) | ChatGPT (GPT-5.4) | Gemini 3 Pro |
|---|---|---|---|
| Long-context | 1M | ※ see official | ~2M ※ |
| Coding | SWE-bench frontier | Top tier | Top tier |
| Agent capability | Cowork (GA) | Operator / Realtime | 3.1 Flash Live |
| Japan residency | AWS Bedrock Tokyo | Azure East Japan | Vertex Tokyo |

## Message (bottom of the slide, highlighted)
"MIXI keeps the ChatGPT investment. Claude gets added on for Code, contract review, executive-doc drafting, and long-context work. Multi-vendor-by-workload is the enterprise standard as of 2026 — single-vendor exclusivity is obsolete."

## Visual rules
- The "Dimension" column has a black background with cream text
- The Claude column gets a faint coral highlight
- ※ is a footnote marker (for items pending verification)

P12 · 14-day learning-path timeline

Visualize the post-workshop "14-day learning path" as a single-slide timeline.

## Composition
- Eyebrow: "14-DAY SELF-STUDY"
- h2: "30 minutes a day × 14 days — from executive to Claude power-user"
- Horizontal timeline from Day 1 to Day 14

## Milestone per day-pair
- Day 1-2: Claude Desktop basics
- Day 3-4: Code tab, first steps
- Day 5-6: API key operations
- Day 7-8: Adding MCP
- Day 9-10: Making a deck in Claude Design
- Day 11-12: First Cowork session
- Day 13: Shave 1 hour off a real task in your own work
- Day 14: Teach it (share internally)

## Visual rules
- Each Day shown as a milestone dot
- Group two days at a time, differentiate with color (coral / amber / success, varying shades)
- Footer: "Seven hours total. After 14 days, you're the kind of executive who modifies their own tools."

P13 · Part separators (3-slide set)

Generate three "section divider" slides — one each for Part 1 / Part 2 / Part 3 — with consistent design.

## Shared layout
- Near-full-screen, left-aligned, just a huge numeral and a heading
- One line of tagline at the lower third
- Eyebrow at top: "SECTION N OF 3"

## Part 1 (1 / 3)
- Huge numeral "01"
- Title: "Claude Code Desktop × ai-executive"
- Tagline: "Build an AI Executive tool from scratch in 40 minutes"

## Part 2 (2 / 3)
- Huge numeral "02"
- Title: "Claude Design"
- Tagline: "Executive documents, through conversation, in minutes"

## Part 3 (3 / 3)
- Huge numeral "03"
- Title: "Claude Cowork"
- Tagline: "The autonomous agent living on your desktop"

## Visual rules
- Numerals at ~240pt, coral
- Titles at 56pt, white-ish
- Full-screen dark background, a faint coral gradient in the top right

P14 · Q&A holding slide

Make one simple Q&A slide.

## Composition
- Full-screen, centered
- Huge title: "Q&A"
- Small subtitle below: "Anything · ask whatever came up"
- Bottom-right timer: "5 min"

## Visual rules
- Mostly empty background, one huge coral question mark (12% opacity) in the backdrop
- Keep it simple

P15 · 3 Takeaways closing

A single closing slide that spells out "three things to start tomorrow."

## Composition
- Eyebrow: "TAKE HOME"
- h2: "Three things to start using tomorrow"
- Three numbered cards stacked vertically

## The three
1. **In Code Desktop, throw one of your own work tasks at it in natural language — once a week.**
   Sub: summarizing decks, market research, competitor analysis, meeting minutes cleanup

2. **For the next exec doc you need to produce, draft 0 → 0.8 in Claude Design in three minutes.**
   Sub: stop starting from zero. 0 → 0.8 in Design, 0.8 → 0.95 in your existing tool.

3. **Start evaluating a Cowork pilot.**
   Sub: five people in corporate strategy, 30 days, decision within two weeks.

## Visual rules
- Each card = numeral (coral, 56pt) + title + one-line sub
- A 3px coral vertical line to the left of each numeral

P16 · Next Steps slide

One slide summarizing the three post-workshop items the facilitator will send.

## Composition
- Eyebrow: "NEXT STEPS"
- h2: "What's arriving from us tomorrow"
- Three items shown as a vertical timeline

## The three
1. **Every URL from today** (by end of day)
   - mixi-exec-ai-workshop.mocco.team
   - Bookmark it
2. **14-day learning path** (tomorrow morning)
   - 30-minute-a-day email cadence
3. **Cowork pilot proposal** (within 2 weeks)
   - 5 people × 30 days in corporate strategy, full trial design

## Visual rules
- A vertical timeline down the left (coral), a milestone per item
- Details on the right of each milestone
- Footer line: "Thank you."

P17 · Meta-reveal slide (we made all of these in Design)

One meta-reveal slide announcing "this entire deck was built in Claude Design." The facilitator can drop it at the top of Part 2, or hold it as a post-CLOSING surprise.

## Composition
- Eyebrow: "META"
- Huge centered text: "These 16 slides? All built in Claude Design."
- Smaller lines underneath:
  - "Time spent: 3 hours (one end-to-end generation pass + refinement, the evening before)"
  - "Human work: injecting the MIXI brand colors, sanity-checking the numbers, and refining 2–3 slides."
  - "Cost: included in the Claude Max subscription ($100/month). No separate billing."

## Visual rules
- Centered full-screen
- The title text is coral, with just "Claude Design" emphasized
- A simple line-art icon in the bottom-right (not the emoji itself — render as an SVG or small illustration)

## Tone
- Not bragging. Flat, factual.
- A single slide showing the reality of "executive documents in the AI era."

P18 · New-business one-pager (Part 2 live demo)

Create a one-page A4 portrait for a new business initiative: "AI Executive Talent Academy (an internal MIXI project)." Print-ready, at a quality you'd hand out in a board meeting.

## Required sections (top to bottom)
1. Title + one-line tagline
2. Problem — why now (3 lines)
3. Solution — what we offer (3 lines)
4. Target — who it's for (2 lines)
5. Differentiation — why MIXI is the right one to do this (3 points)
6. Monetization — revenue model (two options)
7. 12-month roadmap — four quarters as a horizontal timeline
8. Team — headcount assumption (3–5 people)
9. Bottom-right, small: "MIXI internal project · 2026 Q3 target kickoff"

## Visual rules
- Top third: title + problem (larger font)
- Middle third: solution + target + differentiation
- Bottom third: monetization + roadmap + team
- Muted color palette (print output)
- Coral accents only on headers and the roadmap

P19 · Monthly business review, 5 slides (Part 2 live demo)

Generate a 5-slide monthly business review deck, MIXI-style — a first draft an executive could tweak in 3 minutes before the morning leadership meeting.

## 5-slide structure

### 1. Executive summary
- Title: "2026-XX month · business summary"
- Three headline KPIs, big (revenue / operating income / MAU)
- MoM / YoY shown as arrows

### 2. Segment performance
- Table + small bar charts
- Per-segment (Games / SNS / Payments / Sports / Daily-life) revenue and profit

### 3. This month's 3 highlights
- Two positives
- One thing to improve
- 3 lines each

### 4. Concerns and countermeasures
- 2–3 risk items
- One-line countermeasure each
- RAG status (green / yellow / red)

### 5. Next month's focus
- Three themes
- Numeric target for each
- Owner (placeholder name is fine)

## Visual rules
- Consistent header across slides (MIXI + month + page number)
- Numbers displayed tabular
- Tables and charts clean, no over-decoration

P20 · Executive summary (pre-read handout, 1 page)

Create a "90-second read" executive summary of the workshop, on a single A4 landscape page. For the pre-read email attachment.

## Composition
- Top: title "MIXI Executive Claude Workshop · experience Claude 2026 in 90 minutes"
- Left column (40%):
  - Date / duration / format (offline, mixed hands-on)
  - Today's success criteria (3 lines)
- Right column (60%):
  - Each of the three products in 3 lines (Code Desktop / Design / Cowork)
- Bottom:
  - 90-minute timetable (horizontal bars, a simplified P3)
  - 3 prep items

## Visual rules
- MIXI logo at the top (placeholder is fine)
- Large "2026.04" date in the top right
- Light palette (print output) — white base with coral accents, not a dark background
- A4 landscape 297 × 210 mm