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/client-facing-copy.md
View on GitHub# Client-Facing Copy Review
## Scan and repair
| Failure | Typical signal | Repair |
|---|---|---|
| Internal workshop language | “我们内部判断”, “客户透露”, “咨询团队”, “TP团队” | State the client-relevant conclusion and evidence; move process talk to notes. |
| Empty atmosphere | slogan with no decision or mechanism | Use a concrete subject or supported conclusion; add the relevant explanation below. |
| Hidden causality | short phrases requiring interpretation | State cause, mechanism, and outcome in reading order. |
| Process presented as value | “做调研/搭团队/开会” as payoff | Express the business effect, decision, or deliverable instead. |
| Artificially elevated language | TVC-style wording, noun stacks, over-oral copy | Use specific, client-credible language. |
## Page hierarchy
- Title: a specific subject or supported conclusion, chosen for the page job. Pricing, workflow and appendix titles can simply name their content.
- Subtitle: basis, scope, or qualification.
- Body: mechanism, evidence, action, owner, or boundary.
- Presenter script: oral transitions, context, and unresolved discussion.
Never rewrite a protected client-approved sentence without recording permission in the revision ledger.
## Clear business language
Use the audience term actually supported by the brief (often “客户”); do not impose procurement terminology on all proposals. Replace vague abstractions with the service, decision or deliverable being explained. Preserve precise tender terminology when the tender requires it.
Footnotes earn their space through source attribution, concept/demo status, scope, uncertainty or material commercial conditions. Remove repeated process explanations and internal edit history. Concision must not conceal case provenance or exclusions.
See [revision examples](../examples/proposal-revisions.md) and [argument traceability](argument-traceability.md).
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 |