mikeparcewski/wicked-garden / skills/draft
wicked-garden-draft
VerifiedThe quality floor for DOCUMENT deliverables drafted from a repo — brochures, one-pagers, flyers, pages, decks, memos — guidance plus a self-check before "done". Three floors: (1) READABLE — every text/background pair ≥ 4.5:1 (WCAG AA; 3:1 for large text) on COMPOSITED colours, print text ≥ 7pt; (2) SIZED TO THE BRIEF — the RENDERED page count honours the brief's page budget; (3) GROUNDED — every number, URL and claim cites a repo path, mocks visibly labelled, no placeholder ships. Use when: "draft a brochure / one-pager / page / deck / memo about <repo>", "print-ready A4 / Letter", "make it two pages", "is this brochure readable / grounded", before declaring a wicked-interactive draft/edit/revision done, or as the skill a governed drafting run (wicked-crew `interactive-*`) follows. A brief's `Kind:` line (narrative, status update, message, …) adds that kind's ref. NOT for code documentation (the engineering documentarian) or a running app's accessibility audit (the product or qe a11y skills).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.0 KB |
| refs/claims.md | markdown | 4.7 KB |
| refs/demo-script.md | markdown | 1.9 KB |
| refs/design-floor.md | markdown | 4.8 KB |
| refs/meeting-prep.md | markdown | 1.9 KB |
| refs/message.md | markdown | 1.6 KB |
| refs/narrative.md | markdown | 1.9 KB |
| refs/operating-model.md | markdown | 2.1 KB |
| refs/respond.md | markdown | 3.9 KB |
| refs/rework.md | markdown | 4.1 KB |
| refs/self-check.md | markdown | 7.0 KB |
| refs/status-update.md | markdown | 1.7 KB |
refs/demo-script.md
View on GitHub# Kind: demo script
A script a presenter follows to show working software live: what to click, what to say, what the
audience sees. It is a document to read, not a recording (a recording is the Demo video card). The
brief's `Kind: demo script.` line selects this ref. The skill's three floors still apply.
## Shape
1. **Audience and goal:** who is watching and the one thing they should believe at the end.
2. **Setup checklist:** environment, the URL or command that starts the app, test data, accounts by
role (never a password or token), browser state to reset. Each item is something a presenter can
check off.
3. **Run of show,** a table with one row per beat:
| Time | Action (what to click or type) | Say | They see |
|---|---|---|---|
The times add up to the brief's length. With no length given, aim for five minutes and say so in
the notes.
4. **Fallbacks:** for each risky beat, what to say and do if it fails (a prepared screenshot, a
second path, moving on).
5. **The close:** the line that restates the goal, and the ask.
## Rules
- **Only what exists.** Every beat shows a feature the repository has: cite the route, the
component or the command (`data-source`) for each action. A planned feature is said as planned,
never demonstrated as live.
- **Real actions.** Name the exact button, menu item, field and input value, as the code or the
running app spells them. Do not paraphrase a label.
- **One path.** The happy path, with the fallbacks beside it. Branches belong in a second script.
- **Say lines are spoken:** short sentences, no reading of the screen aloud.
- **Sized:** no page budget unless the brief names one (self-check `--no-pages`); the time budget
is the run of show's total.
## Never
- script a feature, a number or a screen the sources do not show;
- include a credential, a personal email or production data in setup or actions;
- promise a time the beats do not add up to.
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: 472k | 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: 472k | 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: 472k | 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 |