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.
examples/proposal-revisions.md
View on GitHub# Revision patterns from a web proposal
Anonymized lessons; no client materials, commercial numbers or proprietary methodology are included. “After” examples illustrate choices, not mandatory wording for every project.
| Before / symptom | Better response | Why / check |
|---|---|---|
| “每份投入留下资产” above a fee table | “合作方案与报价” | Title identifies the actual decision; do not force a slogan. |
| “事实与方向” as the first implementation month | “品牌升级策略” when that is the actual work | Name the work and explain its outputs. |
| Generic company strengths followed by unrelated services | Link observed evidence to a diagnosis and each proposed action | Read the logic in both directions; remove unexplained services. |
| Existing website screenshot used to explain a redesign | Show the diagnosed issue and proposed information structure | A screenshot of the current site does not explain the improvement by itself. |
| Company capabilities listed as search topics | Convert capabilities into customer comparison, decision and supplier-selection questions; validate demand separately | Do not invent evidence that questions are commonly asked. |
| Article service framed mainly as review records | Confirm question → plan/write useful answer → publish/check; deliver manuscript and relevant publication/status evidence | Describe the product the client buys, with accurate scope. |
| Long full-width title pushes evidence low in a two-column page | Group title/body in the left column; align media with the intended reading axis | Check first entry, not only the final scroll position. |
| Dense table plus an unrelated image or a second table | One readable full-width structure | Remove filler; whitespace is not a defect by itself. |
| Two separate screens for standard/package price | Same-stage two-state comparison, reversible on scroll; static dual view on phone | Readable values must stay exact; no fictitious intermediate price. |
| Desktop sticky wheel covers the next phone section | Bound sticky lifetime to its section or disable on phone | Test both boundary crossings and reverse scroll. |
| Login fades to black while a model loads | Keep a visible state until text is ready; load optional 3D independently | Test slow/failing media and reduced motion, not just duration values. |
| New video still has the previous product caption/poster | Inspect subject; synchronize title, caption, alt text, poster and independent playback | A new file path alone does not complete a media change. |
| Logo plus separately typed brand name | Use the supplied official combination artwork | Check identity ownership, aspect ratio and surrounding hierarchy. |
| Repeated small-print caveats | Keep only source/provenance, scope, uncertainty and material conditions | Remove process chatter without concealing limitations. |
## Forward-use scenarios
- “Only move this website link lower”: adjust that component, verify its destination and phone layout; do not regenerate content or prices.
- “Make a PPT from this web proposal”: reuse approved facts and pricing; translate interaction states into editable slides; verify the PPT separately.
- “Use this as a public template”: neutralize content and assets first; keep actual approval and publishing boundaries explicit.
- “The inquiry demo works, so can we call the backend finished?”: no; page-memory state proves only the demonstrator behavior.
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: 470k | 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: 470k | 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: 470k | 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 |