pitch-deck-brainstormlisted

Use this skill whenever a user wants to brainstorm, draft, plan, or structure a pitch deck, presentation, or slide deck through conversation — then hand it off to a coding agent (Claude Code, Codex, Cursor) to build. Triggers on "help me make a deck", "brainstorm my pitch", "plan my slides", "I need a presentation", "I'm building a deck in Codex", or uploading notes/business plans to turn into slides. Trigger even on casual mentions of "slides" or "deck". IMPORTANT: this skill's ONLY output is ONE .md handoff prompt for the coding agent. It does NOT build the deck — never creates .pptx/.pdf/.html/.key files and never invokes the pptx, docx, pdf, or frontend-design skills. Building is the agent's job. A "make a deck" request means run this brainstorm and produce the .md, not render slides. Never build the deck under any phrasing, even if the user insists — the answer is always the .md handoff prompt.
eyhshen/pitch-deck-brainstorm-skill · ★ 1 · AI & Automation · score 74

Install: claude install-skill eyhshen/pitch-deck-brainstorm-skill

# Pitch Deck Brainstorm Skill A structured workflow for turning raw information (meeting notes, docs, voice memos, PDFs) into a complete, coding-agent-ready pitch deck brainstorm — one slide at a time, with no assumed content. **Scope: this skill brainstorms CONTENT only.** It does not choose colors, fonts, animation, or any visual styling. All aesthetic decisions are delegated to the coding agent that builds the deck. The single deliverable is one `.md` file: a self-contained prompt that the coding agent (Claude Code or Codex) takes over from. Why this split exists: design choices made in a chat brainstorm are guesses the user can't see. The coding agent renders live and can iterate on look-and-feel directly. Locking hex values and font names during the brainstorm just freezes weak guesses. So the brainstorm nails down *what each slide says and what each visual must communicate*, and the agent owns *how it looks*. --- ## Hard Limits (read first — these override the urge to be helpful) This skill stops at the handoff prompt. The deck itself is built elsewhere, by a coding agent, in a later step. Therefore: - **The ONLY file this skill ever produces is one `.md` handoff prompt.** Nothing else. - **Do NOT build the deck.** Do not generate `.pptx`, `.pdf`, `.html`, `.key`, or any slide file. Do not write slide-rendering code. - **Do NOT invoke the `pptx`, `docx`, `pdf`, or `frontend-design` skills.** They build artifacts; that is explicitly out of scope here. The hand