screenshots
Skill8 starsChanged 5 months agoMITView on GitHub
Generate the README hero + Mac App Store marketing screenshots (retina, Prose theme, light/dark) via Playwright.
- Reads credentials
18 other projects use a version of this.
Adopted by
Most recently taken up by
- kashaziz/claude-skillstheir own version, first seen Nov 16, 2026
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- yicheng47/runnertheir own version, first seen Nov 8, 2026
- artsy/eigentheir own version, first seen Nov 2, 2026
- bloknayrb/tandemtheir own version, first seen Oct 29, 2026
- petecurran/sortedtheir own version, first seen Oct 17, 2026
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- tabler/tabler★ 42ksame name
- artsy/eigen★ 3.8ksame name
- d4rken-org/permission-pilot★ 694same name
- pablopunk/SwiftShift★ 664same name
- yicheng47/runner★ 519same name
- bloknayrb/tandem★ 28same name
- xfstudio/skills★ 9same name
- keinstn/drover★ 5same name
- moasq/ios-dev-agent★ 4same name
- magnusrodseth/dotfiles★ 3same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accelerateSkill
- implement-issueSkill
- pipeline-engSkill
- pipeline-orchestrateSkill
- pipeline-peSkill
- pipeline-scorerSkill
- qa-acceleratedSkill
- qa-prSkill
- qa-webSkill
- releaseSkill
- review-feedbackSkill
- roadmap-prioritizationSkill
- roadmap-refinementSkill
- security-auditSkill
- accelerateSkill
- implement-issueSkill
- pipeline-engSkill
- pipeline-orchestrateSkill
- pipeline-peSkill
- pipeline-scorerSkill
- qa-acceleratedSkill
- qa-hitlSkill
- qa-prSkill
- qa-webSkill
- releaseSkill
- review-feedbackSkill
- roadmap-prioritizationSkill
- roadmap-refinementSkill
- security-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 89
Don't try to wire a live call.
- Very specific: line 103
If a scene is added/removed/renamed there, update the spec scenes and this table, regenerate, and replace the files in …
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketing Screenshot Generator
Produces the README hero and the Mac App Store screenshot set from a clean, isolated, seeded Prose instance — deterministic, retina (2560×1600), no private data, no live API calls. Built on the e2e Playwright harness.
What it produces
| Output | Scene (App Store copy) | Mode |
01-hero-editor.png (also the README hero) | Hero — post + Projects explorer | ☀️ Light |
02-ai-chat.png | AI Alongside You — chat + mode-switch card | 🌙 Dark |
03-review-diffs.png | Review Every Suggestion — Quick Review | ☀️ Light |
04-edits-history.png | Edits History — the Activity panel | 🌙 Dark |
05-projects-favorites.png | Projects & Favorites — Favorites view | ☀️ Light |
Light hero, then alternating dark/light. Scenes mirror the shot list in
docs/app-store-copy.md. Keep that copy and
this generator in sync when the shot list changes.
Files
| File | Purpose |
e2e/electron.screenshots.spec.ts | Scenes 1, 3, 4, 5 — isolated profile, seeded projects/favorites + the blog fixture |
e2e/electron.screenshot-chat.spec.ts | Scene 2 — the chat mode-switch, injected deterministically (no live AI) |
e2e/fixtures/a-chorus-of-human-voices.md | Demo document (a real blog post). Frontmatter is stripped at runtime so the title leads; a few obvious typos are injected below the fold for the review/activity demos |
docs/app-store-screenshots/ | Destination for the App Store set |
docs/images/prose-screenshot.png | Destination for the README hero (= scene 1) |
Both specs are excluded from the normal e2e run — they self-skip unless
SHOOT=1 is set (test.skip(process.env.SHOOT !== '1', …)).
Run
# 1. Free port 9222 — the dev build binds it; a running dev server blocks the
# screenshot instance. Stop it first (PID file), restart when done.
kill "$(cat .dev.pid)" 2>/dev/null
# 2. Build (the specs launch the built app at out/main/index.js).
npm run build
# 3. Generate → writes to /tmp/prose-shots/
SHOOT=1 npx playwright test electron.screenshots electron.screenshot-chat --workers=1
# 4. Review every shot before committing (they're marketing assets).
open /tmp/prose-shots/*.png
# 5. Place into the repo.
cp /tmp/prose-shots/0{1,2,3,4,5}-*.png docs/app-store-screenshots/
cp /tmp/prose-shots/01-hero-editor.png docs/images/prose-screenshot.pngInspect each PNG (e.g. with the Read tool) and iterate — re-run a single scene
with ... electron.screenshots -g "03 review" --workers=1.
How it works
- Isolated profile — each spec seeds a throwaway
PROSE_USER_DATA_DIRwithsettings.json(Prose themecolor: 'prose', projects/favorites, a fakellm.apiKeyso the chat renders configured,aiConsent). No private data, reproducible. - Retina — the window is set to 1280×800 logical; on a retina Mac that
captures at 2560×1600 (DSF 2), the App Store spec. Verify with
sips -g pixelWidth -g pixelHeight. - Theme —
color: 'prose'(the gold theme; not themonodefault). Light/dark per scene via thedarkclass on<html>. - Seeded content via test seams (always-on, see
src/renderer/main.tsx):window.__prose_tools.executeTool(name, args, mode, provenance?)— driveopen_file,suggest_edit(passprovenance.modelso the Activity panel shows a real model, not "Unknown"),add_comment,accept_diff.window.__prose_chat— seed a conversation + inject messages. Scene 2's mode-switch is an assistant message whosecontentcarries a real<tool-result name="request_mode_switch" success="true">{json}</tool-result>tag, so the rendered card is the actualRequestModeSwitchResultcomponent.
Gotchas
- Live AI can't be automated. The real API key lives in the OS Keychain;
safeStorageis unavailable to the Playwright-launched Electron, so a fresh automated run can't read it. Scene 2 is therefore mocked (the card is the real component with scripted content) — visually identical to a live exchange. Don't try to wire a live call; if you must, you'd seed a plaintext key into the profile'ssettings.json(ipc.tsreadssettings.llm.apiKeyfirst). - Port 9222. The unpackaged build runs in dev mode and binds the DevTools port; a running dev server (or a second screenshot run) collides. One at a time.
- Don't
open -a Prosewhile generating — it launches the installed app, which sharesuserDataon the case-insensitive filesystem and fights the single-instance lock. - Demo content — to change the document, replace the fixture (keep it a real,
on-brand piece). Typos for the review/activity scenes are injected at runtime
in
electron.screenshots.spec.ts(heroBody.replace(...)), not in the fixture.
Updating the App Store set
The shot list is owned by docs/app-store-copy.md (issue #612 owns the assets).
If a scene is added/removed/renamed there, update the spec scenes and this table,
regenerate, and replace the files in docs/app-store-screenshots/.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

