Koubou
Build a screenshot campaign from the app's actual visual language and useful
content. Use HTML/CSS templates, real device frames, and measured output.
Each slide communicates one concrete benefit. User direction sets the scope
and style; readability, honest product claims, and correct canvas geometry
remain the quality bar.
Read the app and settle the story
- Read style intake. Inspect the app, captures,
icon, assets, UI tokens, product docs, and existing marketing before asking
for direction. Summarize the palette, contrast, density, typography, tone,
and distinctive motifs that should carry into the campaign.
- Resolve only material uncertainty using the
style interview. Reuse answers and references
already supplied. Establish the audience, main benefit, requested slides,
target devices, and any localization. When captures are missing or weak,
capture useful app states with the project's documented run path and the
host's available device tools. Check assets' redistribution terms and retain
their required notices.
- Read the design guide. Draft the slide story
and two or three copy options before CSS. Choose useful, realistic app
content that makes each claim visible. Keep the app UI accurate.
- Record the campaign direction: product signals, style, copy voice,
backgrounds, device composition, and variation across slides. Ground each
choice in the app or user direction. For a full set, vary the first three
compositions; repeated upright centered phones are a weak default.
For step-by-step work, finish one requested slide and return its checked
preview before expanding the set.
Prepare and compose
- Use the project's existing Koubou installation, including a virtual
environment when present. Follow setup; prepare HTML
support with
kou setup-html. Linking this skill does not install the CLI.
- Read YAML configuration. Keep configuration,
templates, and source captures in the app repo's established location;
respect its ignored-output and machine-specific configuration rules.
- Select the real device with
kou list-frames, read project.device and
project.output_size, and inspect its geometry before writing CSS:
kou inspect-frame "<device>" --output-size <size> --output json.
Use the returned screen bounds, margins, orientation, and canvas class.
- Plan the text and device zones. Write HTML/CSS that fits the actual canvas,
copy length, and frame proportions. In HTML, annotate each headline, any
supporting copy, and the primary device when present with
data-kou-id
and data-kou-role so the output can
be measured. Use the design guide's canvas-specific typography and scale.
For highlights, zoom callouts, gradients, or content-mode composition,
consult capabilities.
- For each checked export, use a fresh, empty, ignored
project.output_dir;
preserve earlier accepted outputs. Scope a targeted export to the requested
slides/languages. Generate with kou generate <config.yaml> --output json
and retain stdout/stderr. Reject per-slide or per-language generation errors
even if the CLI reports success. Verify every expected slide × language PNG
and HTML sidecar was produced in this run; existing files alone are not proof
(see YAML configuration). Use kou live <config.yaml>
when the user wants to iterate in a live preview; read its
asset-watch limits.
Prefer the host's shared
browser tools for inspecting it.
Check and iterate
Read every generated slide at full resolution and thumbnail size. Account for
every requested language and slide from the current export. For HTML outputs, inspect each sibling
*.layout.json, using layout_path when reported, for objective bounds,
proportions, and mathematical overlaps. Judge appearance from the image.
Content-mode YAML does not emit HTML annotation sidecars: verify its configured
positions and inspected frame geometry against each PNG, and report that
element-level sidecar measurements were unavailable. Choose HTML when that
measured verification is required.
Apply the design guide's rejection checklist to every requested output:
- Copy is specific, readable, truthful, and supported by the visible app state.
- Device frame and screen align; cropping is intentional and useful.
- Text fits its zone, stays legible, and avoids unintended device overlap.
- Empty space, visual hierarchy, and composition serve the slide's benefit.
- A set has deliberate variation while keeping the app's visual identity.
- HTML layout sidecars contain the required annotated elements; empty sidecars
require an annotation fix before claiming measured verification.
Fix and regenerate failed slides before presenting them. A successful renderer
exit is not design acceptance. Return the checked visual preview, full-size
output paths, and any verification gap. For follow-ups, change only the scope
requested and recheck the affected outputs. Uploading or publishing belongs to
the user's authorized release workflow.
1---2name: koubou3description: Design and iterate on App Store screenshots with Koubou. Use when creating or redesigning store screenshots, framing existing app captures, or changing their copy, layout, device size, or localization.4metadata:5 source: https://skillmd.com/skills/sreejithraman/koubou6---78# Koubou910Build a screenshot campaign from the app's actual visual language and useful11content. Use HTML/CSS templates, real device frames, and measured output.12Each slide communicates one concrete benefit. User direction sets the scope13and style; readability, honest product claims, and correct canvas geometry14remain the quality bar.1516## Read the app and settle the story17181. Read [style intake](references/style-intake.md). Inspect the app, captures,19 icon, assets, UI tokens, product docs, and existing marketing before asking20 for direction. Summarize the palette, contrast, density, typography, tone,21 and distinctive motifs that should carry into the campaign.222. Resolve only material uncertainty using the23 [style interview](references/style-interview.md). Reuse answers and references24 already supplied. Establish the audience, main benefit, requested slides,25 target devices, and any localization. When captures are missing or weak,26 capture useful app states with the project's documented run path and the27 host's available device tools. Check assets' redistribution terms and retain28 their required notices.293. Read the [design guide](references/design-guide.md). Draft the slide story30 and two or three copy options before CSS. Choose useful, realistic app31 content that makes each claim visible. Keep the app UI accurate.324. Record the campaign direction: product signals, style, copy voice,33 backgrounds, device composition, and variation across slides. Ground each34 choice in the app or user direction. For a full set, vary the first three35 compositions; repeated upright centered phones are a weak default.36 For step-by-step work, finish one requested slide and return its checked37 preview before expanding the set.3839## Prepare and compose40411. Use the project's existing Koubou installation, including a virtual42 environment when present. Follow [setup](references/setup.md); prepare HTML43 support with `kou setup-html`. Linking this skill does not install the CLI.442. Read [YAML configuration](references/yaml-reference.md). Keep configuration,45 templates, and source captures in the app repo's established location;46 respect its ignored-output and machine-specific configuration rules.473. Select the real device with `kou list-frames`, read `project.device` and48 `project.output_size`, and inspect its geometry before writing CSS:49 `kou inspect-frame "<device>" --output-size <size> --output json`.50 Use the returned screen bounds, margins, orientation, and canvas class.514. Plan the text and device zones. Write HTML/CSS that fits the actual canvas,52 copy length, and frame proportions. In HTML, annotate each headline, any53 supporting copy, and the primary device when present with `data-kou-id`54 and `data-kou-role` so the output can55 be measured. Use the design guide's canvas-specific typography and scale.56 For highlights, zoom callouts, gradients, or content-mode composition,57 consult [capabilities](references/capabilities-reference.md).585. For each checked export, use a fresh, empty, ignored `project.output_dir`;59 preserve earlier accepted outputs. Scope a targeted export to the requested60 slides/languages. Generate with `kou generate <config.yaml> --output json`61 and retain stdout/stderr. Reject per-slide or per-language generation errors62 even if the CLI reports success. Verify every expected slide × language PNG63 and HTML sidecar was produced in this run; existing files alone are not proof64 (see YAML configuration). Use `kou live <config.yaml>`65 when the user wants to iterate in a live preview; read its66 [asset-watch limits](references/capabilities-reference.md#live-mode).67 Prefer the host's shared68 browser tools for inspecting it.6970## Check and iterate7172Read every generated slide at full resolution and thumbnail size. Account for73every requested language and slide from the current export. For HTML outputs, inspect each sibling74`*.layout.json`, using `layout_path` when reported, for objective bounds,75proportions, and mathematical overlaps. Judge appearance from the image.76Content-mode YAML does not emit HTML annotation sidecars: verify its configured77positions and inspected frame geometry against each PNG, and report that78element-level sidecar measurements were unavailable. Choose HTML when that79measured verification is required.8081Apply the design guide's rejection checklist to every requested output:8283- Copy is specific, readable, truthful, and supported by the visible app state.84- Device frame and screen align; cropping is intentional and useful.85- Text fits its zone, stays legible, and avoids unintended device overlap.86- Empty space, visual hierarchy, and composition serve the slide's benefit.87- A set has deliberate variation while keeping the app's visual identity.88- HTML layout sidecars contain the required annotated elements; empty sidecars89 require an annotation fix before claiming measured verification.9091Fix and regenerate failed slides before presenting them. A successful renderer92exit is not design acceptance. Return the checked visual preview, full-size93output paths, and any verification gap. For follow-ups, change only the scope94requested and recheck the affected outputs. Uploading or publishing belongs to95the user's authorized release workflow.