Skip to content

ChuluuMGL/proposal-skill

proposal

Verified

Create, 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.

FileKindSize
SKILL.mdskill md8.1 KB
agents/openai.yamlconfig376 B
assets/demo/cover-premium-boardroom-v2.pngbinary118.6 KB
assets/demo/cover-premium-boardroom.pngbinary118.6 KB
assets/demo/dense-page-v2.pngbinary226.1 KB
assets/demo/dense-page.pngbinary226.1 KB
assets/demo/editorial-brand-3up.pngbinary228.5 KB
assets/demo/editorial-brand-cover-v2.pngbinary139.7 KB
assets/demo/editorial-brand-cover.pngbinary139.7 KB
assets/demo/premium-boardroom-3up.pngbinary520.0 KB
assets/demo/showcase-overview-v2.pngbinary183.0 KB
assets/demo/showcase-overview.pngbinary183.0 KB
assets/demo/tech-launch-3up.pngbinary188.0 KB
assets/demo/tech-launch-page-v2.pngbinary137.9 KB
assets/demo/tech-launch-page.pngbinary137.9 KB
assets/minimal-proposal-template.pptxbinary52.8 KB
examples/final-polish-anonymized-case.mdmarkdown1.1 KB
examples/proposal-revisions.mdmarkdown3.4 KB
references/argument-traceability.mdmarkdown2.4 KB
references/brief-compliance.mdmarkdown4.2 KB
references/client-facing-copy.mdmarkdown1.9 KB
references/external-capability-adapters.mdmarkdown859 B
references/final-polish-workflow.mdmarkdown3.3 KB
references/font-system.mdmarkdown6.0 KB
references/iteration-learning.mdmarkdown2.1 KB
references/layout-rhythm.mdmarkdown12.6 KB
references/manual-edit-protection.mdmarkdown1.5 KB
references/output-contract.mdmarkdown8.6 KB
references/page-types.mdmarkdown4.6 KB
references/palette-library.mdmarkdown7.2 KB
references/proposal-routes.mdmarkdown4.9 KB
references/quality-check.mdmarkdown12.7 KB
references/quality-levels.mdmarkdown1.1 KB
references/runtime-compatibility.mdmarkdown6.3 KB
references/story-map-and-sequencing.mdmarkdown1.0 KB
references/style-template-strategy.mdmarkdown16.9 KB
references/visual-finish-spec.mdmarkdown1.4 KB
references/visual-system-card.mdmarkdown3.0 KB
references/visual-system.mdmarkdown9.4 KB
references/web-interactions.mdmarkdown3.5 KB
references/web-proposals.mdmarkdown5.4 KB
references/workflow.mdmarkdown16.6 KB
scripts/audit_html_demo.mjsscript5.3 KB
scripts/audit_proposal_pptx.pyscript13.2 KB
scripts/build_revision_ledger.pyscript2.4 KB
scripts/check_release_consistency.pyscript2.7 KB
scripts/compare_protected_elements.pyscript5.3 KB
templates/README.mdmarkdown2.7 KB
templates/engine.cssother4.2 KB
templates/premium-boardroom.theme.cssother7.0 KB
templates/style-specs/README.mdmarkdown1005 B
templates/style-specs/consumer-lifestyle.mdmarkdown3.1 KB
templates/style-specs/editorial-brand.mdmarkdown3.1 KB
templates/style-specs/premium-boardroom.mdmarkdown3.5 KB
templates/style-specs/tech-launch.mdmarkdown3.0 KB
templates/tech-launch.theme.cssother2.2 KB
templates/web-components/README.mdmarkdown1.7 KB
templates/web-components/components.cssother6.0 KB
templates/web-components/components.jsscript5.0 KB
templates/web-components/concept-detail.svgother921 B
templates/web-components/concept-system.svgother939 B
templates/web-components/index.htmlother6.3 KB

references/final-polish-workflow.md

View on GitHub
# Final-Polish Workflow: Gate A–F

Use this workflow only for `edit-final-polish`: an existing PPTX has already been manually edited and now needs a client-final revision from screenshots, page-level feedback, or a revised script. Its purpose is to preserve confirmed human work while making the final deck inspectable and safe to hand off.

## Required package

Create a sibling `final-polish/` folder beside the output deck (or an equivalent user-approved location):

```text
final-polish/
  baseline-protection.md
  protected-elements.json
  story-map.md
  revision-ledger.md
  technical-qa.md
  visual-qa.md
  commercial-qa.md
```

The original baseline PPTX is read-only. Never overwrite it. The revised PPTX must receive a new versioned filename.

## Gate A — baseline and manual-edit protection

1. Identify the user-designated or most recently saved PPTX. Do not return to a prior build folder merely because it is easier to generate.
2. Read `manual-edit-protection.md`; create the protection register before editing.
3. Capture protected image geometry/crop and protected text using:

```bash
python3 scripts/compare_protected_elements.py capture baseline.pptx protected-elements.json
```

4. Record only what the user authorized for change. Treat every other manual copy change, image crop/position, brand asset, and confirmed page as protected.
5. After edits, compare the protected manifest. Explain every permitted difference in the revision ledger; unexplained differences are blockers.

## Gate B — story map and sequencing

Create `story-map.md` before changing page order. For each page write chapter, commercial question, conclusion, why it follows the preceding page, and what it makes possible next. Use `story-map-and-sequencing.md`.

Resolve duplicated or prematurely completed themes. A default causal order is: `opportunity and problem → overall strategy → trust building → audience asset → transaction validation → delivery mechanism → next-stage action`. Use another sequence only when the story map explains why.

## Gate C — client-facing copy

Scan every client-facing title, subtitle, label, and conclusion with `client-facing-copy.md`. Move internal discussion, caveats, and oral elaboration to the presenter script; do not leave them on the client page.

## Gate D — visual system and page rhythm

Lock the existing/approved visual system, then apply `visual-finish-spec.md`. Check repeated modules, dark-page tokens, image subject/crop, page rhythm, optical spacing, and full-size readability. Do not restyle a confirmed deck merely to make it look novel.

## Gate E — assets and evidence

Use images as evidence for the specific claim: products for product/benefit/conversion pages; people and situations for audience pages; report/data visuals for trend claims; information design for mechanisms. AI images are concepts, not research or client facts, and must be marked where necessary.

## Gate F — separate acceptance and delivery state

Run `audit_proposal_pptx.py` plus any available render/open check. Then complete `quality-levels.md` as three separate reports: technical package integrity, visual full-size render review, and commercial narrative review.

Only mark `客户可交付版` when all three pass or the user explicitly accepts named exceptions. If only automated checks pass, use: `技术通过,待视觉/商业复核`.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall