proposal
VerifiedCreate, revise, or audit commercial proposals as editable PowerPoint, interactive HTML, or PDF, with proposal logic, case evidence, scope and pricing, presenter scripts, and format-specific validation. Use for client proposals, pitches, tenders, and proposal revisions, rather than general marketing websites.
references/quality-check.md
View on GitHub# Quality Check
Run this before delivery. Treat unchecked `[BLOCKER]` items as no-delivery conditions unless the user explicitly accepts the downgrade.
Use this format in the final handoff or internal QA note:
```markdown
## Delivery QA
- Runtime:
- PPTX backend:
- Preview/render method:
- QA status: passed / passed with warnings / downgraded / blocked
- Unresolved assumptions:
```
## 0. Runtime And Package Gate
- [ ] [BLOCKER] The current runtime can read `SKILL.md` and all required `references/*.md` files.
- [ ] [BLOCKER] The source brief/files were actually read or the missing source is marked.
- [ ] [BLOCKER] Output location is writable.
- [ ] [BLOCKER] If a `.pptx` is promised, a PPTX backend is available and named.
- [ ] [BLOCKER] If no PPTX backend is available, the delivery is downgraded to `blueprint-only`, `copy-and-script`, `template-spec`, or `html-demo` and clearly labeled.
- [ ] [BLOCKER] The final package includes the requested `.pptx` and same-name `.md` script, unless explicitly downgraded.
- [ ] [WARN] Runtime limitations are listed in the final response when rendering/open validation cannot be performed.
## 1. Story Gate
- [ ] [BLOCKER] The deck has a one-sentence winning thesis.
- [ ] [BLOCKER] The deck starts from the client's problem or decision criteria, not the vendor's service list.
- [ ] [BLOCKER] The chapter flow can be explained in roughly 3 minutes.
- [ ] Each chapter advances the commercial argument.
- [ ] The closing page returns to the opening thesis or cooperation promise.
- [ ] The proposal route matches the brief: brand/social/content, annual retainer, project execution, consulting/AI/SaaS, or partnership/sponsorship.
## 2. Per-Slide Gate
Check every slide:
- [ ] [BLOCKER] One slide has one core judgment.
- [ ] [BLOCKER] Title accurately names the subject or states a supported conclusion; it is not an empty slogan.
- [ ] [BLOCKER] A visible proof object supports the title.
- [ ] The slide has an obvious reason to exist in the story.
- [ ] Long reasoning is in the presenter script, not the slide body.
- [ ] Unknown claims are marked as `待确认`, `暂无公开数据`, `需客户确认`, or equivalent.
- [ ] No slide relies on oral explanation to repair missing visual logic.
- [ ] No internal wording appears on client-facing slides, such as `赢标逻辑`, `客户透露`, `内部判断`, or `释标会之后`, unless the user requested an internal draft.
## 3. Evidence Gate
- [ ] [BLOCKER] No invented data, cases, awards, client names, screenshots, platform permissions, or results.
- [ ] [BLOCKER] Public or third-party data/screenshots have source labels where needed.
- [ ] Benchmark pages extract transferable methods, not only visual examples.
- [ ] Case pages explain relevance and transfer, not only credentials.
- [ ] AI-generated visuals are marked as conceptual when they are not real proof.
- [ ] Sensitive customer examples are not used in reusable/public skill assets.
## 4. Visual And Layout Gate
- [ ] [BLOCKER] PPT/staged HTML uses the chosen slide ratio; responsive HTML reflows at the required viewport sizes.
- [ ] [BLOCKER] No unreadable text below 8 pt.
- [ ] [BLOCKER] No accidental overlap, clipping, broken connectors, or text overflow.
- [ ] [BLOCKER] No page has major content clustered in one corner or one half unless deliberately balanced by a visual anchor.
- [ ] [BLOCKER] No large empty lower-third, empty bordered placeholder, or unused media frame remains on a client-facing slide.
- [ ] Each slide has an explicit layout recipe and density class when building a new deck.
- [ ] Standard and proof-dense pages use the lower third deliberately through proof, conclusion, timeline, source status, or a visual anchor.
- [ ] Every 3-5 slides, the deck changes rhythm through a section divider, big-idea slide, visual proof page, quote, summary, or low-density transition.
- [ ] Margins, title positions, page numbers, and footer/source style are consistent.
- [ ] Chapter dividers are visually unmistakable and cannot be confused with normal body pages.
- [ ] The deck has visible silhouette variation across chapter, reasoning, image-led, diagram, and proof-dense pages without changing art direction.
- [ ] Repeated split/table/image layouts share exact top and bottom coordinates, proof-block heights, baselines, gutters, and conclusion-strip positions.
- [ ] Tables, ledgers, cards, and column modules have enough internal safety distance: text is not visually attached to dividers, borders, or vertical rules.
- [ ] Tables have clear headers, units, assumptions, and exclusions.
- [ ] Screenshots are cropped cleanly and aligned.
- [ ] Images preserve the intended subject, product, face, UI focus, and text-safe area; image, caption, and conclusion read as one proof object.
- [ ] No meaningless decoration, fake logos, low-resolution images, or stretched media.
- [ ] Palette does not become a one-color monotone or cheap gradient theme.
- [ ] Dark pages maintain at least 4.5:1 contrast for normal text and 3:1 for large text, with stronger contrast when projector viewing is likely.
- [ ] When no VI is provided, a named palette from `palette-library.md` is selected and applied consistently.
## 5. Rich Style Gate
Use this only when a strong style system is selected.
- [ ] [BLOCKER] The style changes more than color: typography, layout grammar, components, proof-object forms, and asset treatment match the chosen style system.
- [ ] [BLOCKER] If no approved reference deck exists, the style passes the three-page sample gate: cover/big idea, proof/mechanism, and dense business page.
- [ ] [BLOCKER] Style-critical pages have been reviewed full-size; contact sheets alone are not enough.
- [ ] [BLOCKER] If no client VI exists, one of the public template families in `style-template-strategy.md` is selected or an explicit custom route is documented.
- [ ] [BLOCKER] New style/template routes pass the three-page sample gate: cover/big-idea, strategy/mechanism, and proof-dense.
- [ ] Components are not identical across different style routes. A magazine collage page, Web3 dashboard, pixel quest path, and editorial proof board should not share the same generic card grid.
- [ ] Asset-heavy styles use real client assets, sourced assets, AI-generated conceptual images, or explicit placeholders.
- [ ] Shape-only substitutes for photographic, editorial, ink, oil, pixel, or Web3 styles are labeled as wireframes, not final templates.
- [ ] HTML/SVG-generated style layers do not turn core business text, budgets, KPI, or risk controls into uneditable screenshots unless the user accepts that tradeoff.
- [ ] Reject public template candidates where all sample pages share the same card-grid silhouette.
- [ ] Reject style-rich pages where the style becomes unrecognizable after removing the title text.
- [ ] Reject proof-dense style samples where budget, KPI, risk, timeline, or brief coverage is not readable and editable.
## 5A. Public Demo Hard-Fail Gate
Reusable public demos and skill showcase decks have a higher bar than working drafts. A demo must be rejected, not scored as acceptable, if any full-size slide has one of these issues:
- [ ] [BLOCKER] Text overflows, clips, wraps awkwardly, or escapes its intended module.
- [ ] [BLOCKER] A module is visually cramped while another large area is accidentally empty.
- [ ] [BLOCKER] The lower third is blank without being a deliberate breathing-page composition.
- [ ] [BLOCKER] Images collide, stack, or mask each other in a way that makes the viewer unsure where to look.
- [ ] [BLOCKER] Connectors are broken, disconnected, visually random, or fail to explain the logic path.
- [ ] [BLOCKER] A sidebar, caption strip, tag, or conclusion band is only decoration and does not carry proof, source status, or decision logic.
- [ ] [BLOCKER] Text is visually attached to a divider, border, or column rule because internal padding/gutter is missing.
- [ ] [BLOCKER] Repeated proof images are used as filler instead of distinct evidence.
- [ ] [BLOCKER] The page relies on a red-box-worthy empty area, ornamental border, or floating component to feel complete.
- [ ] [BLOCKER] The slide would make a reasonable user conclude the skill produces ugly or untrustworthy decks.
If one of these appears, do not publish the deck as a demo and do not describe it as high-end. Mark the sample as failed, write the failure reason, and rebuild from a simpler layout system.
For public demos, full-size visual inspection is mandatory for every slide. Contact sheets, ZIP integrity checks, and keyword searches for overlap warnings are not sufficient.
## 5B. HTML Demo Visual QA Gate
Use this when a style demo or prototype is produced as HTML before PPTX conversion.
- [ ] [BLOCKER] Fixed-stage demos use the chosen slide geometry; responsive proposals use the separate viewport/state checks in web-proposals.md.
- [ ] [BLOCKER] Full-size PNG screenshots were rendered and inspected for every public-demo slide.
- [ ] [BLOCKER] Visual review confirms text is not attached to dividers, borders, image masks, or column rules.
- [ ] [BLOCKER] Visual review confirms no image/caption/component stack obscures the intended reading order.
- [ ] [BLOCKER] DOM checks, `scrollHeight`, and contact sheets are treated as support checks only, not final approval.
- [ ] HTML/SVG/raster layers are limited to style assets unless the user accepts non-editable text or proof objects.
## 6. Commercial Gate
- [ ] [BLOCKER] Brief requirements are mapped to proposal responses.
- [ ] [BLOCKER] Budget pages show deliverables, frequency/cycle, inclusions, exclusions, assumptions, and acceptance criteria.
- [ ] Base service, project modules, optional items, media/third-party costs, and client-provided resources are separated where relevant.
- [ ] KPI are layered and measurable, not a mixed list of exposure, conversion, and brand asset metrics.
- [ ] Team page shows operating responsibility and response mechanism, not only titles.
- [ ] Risk page includes risk point, trigger, response, owner, and boundary.
- [ ] Timeline or cadence page shows sequence logic, not only a calendar.
## 7. Presenter Script Gate
- [ ] [BLOCKER] A same-name `.md` presenter script exists unless the user explicitly declined it.
- [ ] The script includes overall presentation logic.
- [ ] Each slide has objective, why it appears here, exact talk track, transition sentence, and confirmation notes.
- [ ] The script does not merely repeat slide text.
- [ ] Missing information and assumptions are listed clearly.
- [ ] Generated/conceptual images, unverified data, and pending client inputs are disclosed.
## 8. PPTX Compatibility Gate
- [ ] [BLOCKER] Final `.pptx` passes ZIP integrity check.
- [ ] [BLOCKER] Final `.pptx` XML is well-formed when XML validation is available.
- [ ] [BLOCKER] For bundled skill assets or reusable templates, do not rely on ZIP validity alone; validate that PowerPoint, Keynote, LibreOffice, or the local preview pipeline can open/render the file.
- [ ] The deck can be rendered or converted by an Office-compatible tool before delivery when available.
- [ ] If a generated PPTX is valid XML but fails to open, rewrite it through an Office-compatible exporter and deliver the repaired copy.
- [ ] If render/open validation was unavailable, the final response says what was checked and what remains unverified.
## 9. Font And Asset Gate
- [ ] [BLOCKER] No unlicensed commercial font dependency is required.
- [ ] Free/commercial-safe fonts or documented fallbacks are used.
- [ ] If a preferred font is unavailable, the fallback stack in `font-system.md` is used without breaking layout.
- [ ] For CJK decks, document font choices and any CJK preview limitation in the script or final handoff.
- [ ] Public assets, screenshots, third-party marks, and generated visuals follow the asset rules in `visual-system-card.md`.
- [ ] No fake client logos, platform icons, award badges, or fake screenshots appear.
## Common Failure Modes
- Generic table of contents with no winning thesis.
- Market analysis that does not change the strategy.
- Competitor screenshots with no transferable learning.
- Creative concept with no production cadence.
- Budget number without deliverables and acceptance criteria.
- KPI list that mixes exposure, conversion, and brand asset metrics without hierarchy.
- Presenter script that merely repeats slide text.
- Deck that looks good but cannot answer why the client should choose this vendor.
- Style library that uses the same card component under different style names.
- Runtime that cannot generate PPTX but still claims a finished PowerPoint was delivered.
## Responsive HTML and live delivery
Use the behavior and viewport checklist in [web-proposals.md](web-proposals.md). Record reverse-scroll boundaries, dialogs/focus, media, exact price states, reduced motion and live access checks where relevant. The fixed-stage `.slide` audit is not evidence of responsive or production correctness.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |