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/visual-finish-spec.md
View on GitHub# Visual Finish Specification
Apply this after identifying the existing deck’s visual system. It is a finishing specification, not an invitation to replace a client-approved design.
## System additions
- Define separate tokens for light and dark pages: title, body, secondary copy, numbers, rules, fills, and emphasis.
- Define standard geometry for recurring tables, three-column pages, image/text modules, headers, and bottom bars.
- Define image role by claim: product, audience lifestyle, research/data, mechanism, or conceptual illustration.
## Full-size review checklist
- Repeated modules share grid, header height, image height, gutter, line-height, and footer/bottom-bar alignment.
- Do not run the same layout silhouette for more than two consecutive pages; the third needs a purposeful rhythm change.
- Dark pages do not inherit low-contrast greys from light pages; title, labels, rules, and explanatory copy stay clearly tiered.
- Crop to the visual subject. Do not cut faces awkwardly, crowd a subject into an edge, or leave rough cut-out edges.
- Inspect full-size renders for overflow, irregular wraps, optical alignment, clipping, chart contrast, and usable whitespace.
## Forbidden shortcuts
- A product packshot cannot stand in for an audience, trend, mechanism, or research claim.
- Decorative cards cannot replace information design.
- A thumbnail/contact-sheet check cannot pass visual QA on its own.
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 |