SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsproposal-generator

proposal-generator

Office & productivity

View repository

Updated 10-16 08:54

About this skill

proposal-generator

This Skill is used to generate web PPT JSON data that can be opened directly by the frontend.

Its core constraint is not "output the deck all at once," but rather adopting a two-stage process:

  1. First generate and confirm outline.json
  2. Then generate deck.json + slides/*.json

Applicable scenarios

  • The user requests "make it into a PPT / report draft / pitch deck / deck"
  • The user wants to output a web PPT that can be opened directly
  • The user wants to obtain the structural outline, detailed pages, and graphic assets at the same time

Commands

/fppt:outline

Generate and write out work/ppt/001_项目名/outline.json, used to confirm the chapter structure, page order, layout choices, and the core conclusion of each page.

Process:

  1. Determine the PPT type (courseware type / proposal type / report type / presentation type)
  2. Read the corresponding type prompt (skills/prompts/ppt/01~04_*.md）
  3. Plan the chapter structure, page order, layout_type for each page, and decision purpose
  4. Write out outline.json
  5. Perform outline quality inspection; only after passing can you enter the next stage

/fppt:detail

Based on the confirmed outline.json, generate deck.json + slides/*.json, completing each page's copy, chart fields, and asset references.

Process:

  1. Read the confirmed outline.json
  2. Generate slide JSON page by page, filling in fields such as title/subtitle/blocks/table/chart/svg
  3. For graphic pages, proactively generate under work/assets/ generate SVG assets
  4. Write out deck.json and all slides/*.json
  5. Perform detailed page quality inspection; deliver only after passing

/fppt:viewer

Start the frontend preview service.

Process:

  1. If ppt-viewer/dist/ does not exist, first run npm --prefix ppt-viewer run build
  2. Run node server.mjs
  3. The service starts at http://localhost:9030/

You can also use the shortcut command in the project root directory:

  • npm run dev: build first, then start
  • npm start: start directly (requires prior build)

/fppt:review

Based on the generated detail (deck.json + slides), comprehensively review and evaluate the content from the audience's perspective.

Process:

  1. Read deck.json determine the PPT type (courseware type / proposal type / report type / presentation type)
  2. Read skills/prompts/ppt/05_review.md in the review standards
  3. First check the deck's page order, chapter attribution, transitions, and thematic consistency, then read the slides JSON page by page to evaluate:
    • Understandability: Can the audience understand the core information in one pass?
    • Structural clarity: Is the page's information hierarchy clear at a glance?
    • Information density: Is it too crowded or too empty?
    • Visual matching: Is the layout_type choice reasonable?
    • Transition coherence: Is the logic between pages smooth?
    • Reasonableness of chapter attribution: Is the page placed in the correct chapter?
    • Thematic relevance: Are the title, content, and chapter theme consistent?
    • Layout reasonableness: Is the current layout_type really suitable for expressing the content?
    • Graphic quality: For charts/SVGs/flowcharts, additionally check the structure, content, numbering, alignment, and complete display
  4. Add specialized review dimensions according to the PPT type (see 05_review.md)
  5. Output work/ppt/XXX/review-yyyyMMddHHmmss.md, including:
    • Overall score and overall evaluation
    • Page-by-page diagnosis (issues + severity level + improvement suggestions)
    • Prioritized revision checklist

Workspace structure

work/
  input/
    001_项目名/
  ppt/
    001_项目名/
      outline.json
      deck.json
      slides/
        001_cover.json
        002_agenda.json
        ...
  assets/
    *.svg

Type support

Before generation, you must first determine deck.type, choose one of four:

  • 课件类
  • 方案类
  • 汇报类
  • 演示类

Once the type is determined, you must continue by reading the corresponding prompt:

  • skills/prompts/ppt/01_课件类.md
  • skills/prompts/ppt/02_方案类.md
  • skills/prompts/ppt/03_汇报类.md
  • skills/prompts/ppt/04_演示类.md

Output requirements

Must output to the project directory:

  • work/ppt/001_项目名/outline.json
  • work/ppt/001_项目名/deck.json
  • work/ppt/001_项目名/slides/*.json

Diagram-type assets are output by default to:

  • work/assets/*.svg

The frontend project aggregates and displays by reading deck.json + slides/*.json , and no longer requires generating deck.html。

Quality requirements

  • Mandatory use of the outline -> detail two-stage process
  • outline After the stage ends, an outline quality check must first be performed
  • detail After the stage ends, another round of detailed page quality check must be performed
  • Diagram-type pages should preferentially use structured expressions such as svg_full、phases、swimlane_process、comparison_table and other structured expressions
  • svg_full By default, do not repeatedly write the page title inside the SVG; the title is handled by the deck page title
  • Page titles must be business topics or conclusions; it is forbidden to directly use layout names as titles; names such as "nine-grid", "four-grid", "step diagram", "flowchart", "Gantt chart", etc. must not appear

Prompt directory

fast_ppt/
  README.md
  LICENSE
  docs/
    usage.md
    workflow.md
    layouts.md
  skills/
    SKILL.md
    prompts/
      ppt/
        00_PPT生成.md
        01_课件类.md
        02_方案类.md
        03_汇报类.md
        04_演示类.md
        05_review.md
        layouts.md
        layout_rules.md
        examples/

Reference documents