← ClaudeAtlas

kappmaker-screenshotslisted

Design and translate App Store and Play Store MARKETING screenshots with AI — headlines, brand panels, device frames. Use when the user asks for store screenshots, marketing screenshots, or screenshots in other languages. Capturing the app's real screens is different — that is the project-bundled capture-app-screens skill, whose output feeds this one as references.
KAppMaker/KAppMaker-CLI · ★ 3 · AI & Automation · score 64
Install: claude install-skill KAppMaker/KAppMaker-CLI
# KAppMaker — Screenshots ## Before running any command 1. **Prerequisites** — `kappmaker --version` (install: `npm i -g kappmaker`). If a credential is missing the CLI says so; re-run `kappmaker config init`. 2. **Read `AiGuidelines/` first** — the PRD, positioning and UI spec already answer most questions. ### generate-screenshots — AI Screenshot Generation **Syntax**: `kappmaker generate-screenshots --spec <spec.json> [options]` (agent flow) or `kappmaker generate-screenshots --prompt "<app description>" [options]` (OpenAI fallback) **You are the AI — author the spec yourself. NEVER use the bare `--prompt` path from this skill.** The `--prompt`-only path calls OpenAI (GPT-4.1) to write a JSON screenshot spec, which exists solely for users running the raw CLI without an agent. You can write that JSON better yourself, with full project context, and no `openaiApiKey` is needed. The flow: 1. Ask the user which style preset (1–8) they want if not specified. 2. Run `kappmaker spec-template screenshots --output Assets/screenshots/spec.json` — writes the canonical spec skeleton (the exact JSON shape the OpenAI path used; its `_instructions` key explains the rules and is auto-stripped before generation). 3. Run `kappmaker generate-screenshots --print-prompt --prompt "<one-line app description>" --style <id>` — it prints the style-specific visual direction (device framing, layout zones, typography rules) and exits without calling any API. It also reports whethe