Prompy

Explore

What the community is sharing right now.

  1. Step 1: Obsidian
  2. Step 2: Gemini
  3. Step 3: NotebookLM (this prompt)
  4. Step 4: Claude Opus 5.5

Step 3 of Research a topic and write a cited report

ziedalsnoussi@ziedalsnoussi2d ago

Research Synthesizer with Sources

For NotebookLM or Gemini: turn a pile of notes and sources into a cited plan.

Using only the sources I've provided, build a plan for {{outputtype}} about {{topic}}. 1. Summary (5 sentences max): what the sources agree on. 2. Main sections: 4–7 sections in a logical order. For each give: - a working title - 2–4 key points - the source(s) each point comes from, cited by name 3. Conflicts: where sources disagree, and which one looks more reliable and why. 4. Gaps: what's missing from the sources that the audience will expect. 5. Best evidence: the 3 most striking facts, numbers or quotes, with citations. Rules: never state a fact that isn't in the sources. If you're unsure, say so. Write for {{audience}}.
  1. Step 1: Obsidian
  2. Step 2: Slidesgo
  3. Step 3: Gemini or NotebookLM
  4. Step 4: Claude Fable 5.2 (this prompt)
  5. Step 5: Claude Opus 5.5

Step 4 of Make a presentation

ziedalsnoussi@ziedalsnoussi2d ago

Slide Deck Planner from Notes and a Template

For a planning model such as Claude Fable 5.2: maps your research onto the slides of a chosen template.

You are a presentation designer. Plan a deck; do not write final slide copy yet. Inputs: - Research plan: {{plan}} - Template: {{templatename}}, with these layouts available: {{layouts}} - Talk length: {{minutes}} minutes, audience: {{audience}} Produce a table with one row per slide: | | Layout | Slide title | Purpose (1 line) | Content (bullets, data or visual) | Speaker note idea | Rules: - About 1 slide per minute, never more than 1 idea per slide. - Start with a hook, end with one clear call to action. - Use the template's layouts as they are meant to be used (section headers for transitions, big-number layouts for statistics). - Mark any slide that needs a chart or image with [VISUAL] and describe it. - After the table, list the 3 riskiest slides (confusing, too dense, weak evidence) and how to fix each.
ziedalsnoussi@ziedalsnoussi4d ago

Codebase-Aware Roadmap to GitHub Issues Generator

Use with Claude Code / Cursor CLI to inspect any repo's architecture, break down raw feature ideas into sequenced technical specs, and auto-create GitHub issues via gh CLI.

You are a Senior Technical Product Manager & Full-Stack Architect working on {{projectname}}. Project Context & Architecture {{projectreadmeorstacksummary}} Before designing any solution or creating tickets, inspect the existing repository structure, database schema/migrations, environment variables, auth/permissions setup, and package dependencies so every architectural decision matches our exact conventions. --- Raw Product Requirements to Plan & Ticketize {{featurerequirements}} --- Execution Instructions 1. Inspect Codebase First: Read the core configuration files, database schema, API routes, and relevant UI components to ground every ticket in real file paths, existing tables/models, and installed packages. 2. Break Down into Atomic, Sequenced Issues: Group the requirements into clean, well-scoped, logical issues (e.g., Database & Auth, Core Backend/Services, Admin/UI Components, Third-Party Integrations). Explicitly note dependencies between issues (e.g., Depends on #1). 3. Publish Directly to GitHub Now: Use gh issue create (or connected GitHub tools) to create every issue in the target repository with relevant labels (e.g., enhancement, backend, frontend, database, security). 4. Required Format for Each Issue: - Title: [Feature] <Clear Actionable Title> - Overview & Goal: What this adds to {{projectname}} and why it matters. - Technical Implementation Plan: Exact database migrations/schema changes, security/permission rules, new environment variables needed, specific files/routes/components to create or modify, and key edge cases. - Acceptance Criteria: Concrete - [ ] checklist for QA verification. 5. Final Recap: Once all issues are created on GitHub, output a Markdown summary table listing: Issue #, Title, Labels, Dependencies, and GitHub URL.