bama-clone
Walk through any existing app (native Mac app with computer use, web app with a browser), screenshot every screen, menu, and dialog, write a screen index, and turn it into user stories. Use when the user wants to clone, rebuild, replace, or copy the design of an app, or says "screenshot every screen".
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- bama-clone
- description
- Walk through any existing app (native Mac app with computer use, web app with a browser), screenshot every screen, menu, and dialog, write a screen index, and turn it into user stories. Use when the user wants to clone, rebuild, replace, or copy the design of an app, or says "screenshot every screen".
- argument-hint
- <app name as shown in the menu bar, or a URL>
02 资源文件 2
- 参考文档agents/openai.yaml102 B
- 脚本scripts/window-shot.sh1.4 KB
03 SKILL.md 正文
<!-- Version-Timestamp: 2026-10-27 07:36:32 AST -->
Adapted execution contract
This is the pinned, MIT-attributed BAMA capability adapted for the owned design kit. Read ADAPTATION.md at the BAMA package root before executing helpers. Project instructions, approved DESIGN.md and canonical tokens take precedence. Use supported Codex or Claude Code tools. Resolve this skill's sibling files relative to its installed SKILL.md; skill_dir is a task-local shell variable that you set to that resolved directory before running the examples in either host. Invoke a named bama-* skill through the host's supported skill mechanism.
Stage local builds by default. Installation, signing identity selection, launch, CLI linking, MCP registration, system setting changes and capture access are separate explicit operations. Existing task authorization applies; ask only for an action not already authorized. Stage or commit only when the current task or repository workflow authorizes it. Stage explicit paths and include required attribution. The helpers do not commit. Preserve the feature, story and testing workflow below using the hardened helpers. Legacy installed-app paths in examples must be replaced by the staged binary returned by build.sh.
Before a new scaffold exists, keep planning evidence under the selected <AppName>-planning/docs/ sibling or an existing approved planning folder. Treat docs paths below as relative to that planning folder until the fresh app is scaffolded, then copy the planning docs explicitly without replacing existing files. For an existing app, keep its current project layout.
The upstream acceptance statements describe checks to perform, never completed results. Screenshots, runtime behavior, permissions and cross-host acceptance require actual evidence. Use synthetic data and owned temporary test roots. Do not run a hosted session over real app data without project authorization.
Clone
Output: a folder of screenshots, one index that describes everything the app shows, and a backlog built from it.
docs/screens/
INDEX.md
01-inbox.png
02-today.png
...
docs/STORIES.md (from the user-stories skill)
1. Pick the tool
| The app is | Use |
|---|---|
| A native Mac app, or Electron | Computer use (mcp__computer-use__*) |
| A web app | A browser tool: the built-in browser, Claude in Chrome, or Playwright |
Computer use needs a Pro or Max plan, and Accessibility and Screen
Recording permissions. Claude desktop: Settings > This computer > Enable
computer use. Claude Code CLI: /mcp > computer-use > Enable. Ask for
access to the reference app only. Browsers are view-only and terminals are
click-only for computer use.
2. Agree on privacy
Tell the user you will see everything in the app. Suggest a demo account or sample data. Look, do not touch: open screens and menus, press Escape to close dialogs. Type, create, change, or delete only when the user says so.
3. Save real files
Computer use screenshots come to you downscaled, not to disk. Save each screen at full resolution with the script in this skill:
"${skill_dir}/scripts/window-shot.sh" "<App Name>" docs/screens/01-inbox.png
It captures the app's largest window. For menus and popovers outside the
window, use screencapture -x docs/screens/<name>.png and note it in the
index. In a browser, use the tool's screenshot with a file path.
4. Walk the app in this order
- Main window, default page.
- Every sidebar item, top to bottom. Expand collapsed groups.
- Every view mode (list, board, calendar), sort menu, filter menu.
- One item opened in detail: panel, fields, sub-items.
- Creation flows: add button, quick-add panel (global shortcut), inline editor. Empty and half filled in, then Escape.
- Context menus on an item, a section, a sidebar entry.
- The menu bar: every menu once. Record every item and shortcut.
- Settings: every pane.
- Empty states.
- Dark mode: the two or three main pages again.
Name files NN-page-or-state.png in capture order. The walk is
exhaustive when every sidebar item, menu, and settings pane has a file.
Lessons from real walkthroughs
- Many "Mac apps" are Electron. Their menu bars are nearly empty, and the actions hide in hover toolbars, right-click menus, and command palettes. Hover rows and search the palettes (typing in a palette search is safe; do not press Return).
- Background clicks (
app_*tools) fail on some Electron screens. Then ask for full-screen control, and tell the user to keep off the mouse. - Preview fields test behavior without saving. A "Type a date" box in a to-do app shows how it parses a phrase before anything is stored. 30 phrases there corrected 3 answers from the docs.
- Note any change in the user's data during the walk, even if you are not sure you caused it, and tell them.
5. Write docs/screens/INDEX.md
One section per screenshot:
## 03-upcoming.png
Page: Upcoming. Reached from: sidebar > Upcoming.
Layout: header with month picker and "Today" button; week strip; tasks
grouped by day, each day a section with a heading and an add button.
Elements: task row (checkbox, title, description line, date, project tag,
priority flag color).
Actions: complete, open, drag to another day, add to a day.
Shortcuts seen: none.
End with three lists:
- Navigation map: sidebar items and where each leads.
- Command map: every menu item and keyboard shortcut.
- Data model guess: the nouns and fields you saw.
Describe structure and behavior. Take no text, logo, or icon from the app:
rebuilding for personal use is fine, copying a brand is not. Keep the PNGs
out of public repos (add docs/screens/*.png to .gitignore).
6. Turn it into stories
Invoke the host-supported skill bama-user-stories. Every screen in the index ends up
linked from at least one story, or listed under ## Dropped.
Done when INDEX.md has a section per PNG, the three maps exist, and
docs/STORIES.md covers every screen.
04 同仓库更多 Skills
web-design
Load before planning, designing, auditing or launching any website, landing page, cinematic hero, microsite or above-the-fold layout, or a prompt for Lovable, Bolt or v0 to build one, including regulated (prescription drug, health, finance), multilingual or market-specific launches. Covers page types (home, product, pricing, about, blog), conversion and ethical persuasion, responsive and fluid layouts, Core Web Vitals, SEO and structured data, localization and language-law requirements, stack and CMS choice (Astro, Next.js, WordPress, Webflow, Framer) and launch QA.
ux-design
Load before designing or reviewing any flow, form, onboarding, navigation or content for real users, especially low-literacy, older, neurodivergent, child or other specific audiences. Covers research and usability tests, heuristic reviews, personas and jobs to be done, journeys and service blueprints, information architecture, UX laws, SUS, SEQ and HEART metrics, plain language and reading level, and microcopy and error messages.
ui-design
Load before designing or specifying any interface screen or component, even a quick one: forms, tables, navigation, dashboards, onboarding, auth and passkeys, pricing, checkout, search and filters, settings, empty, loading and error states, notifications, consent and age-appropriate flows, and AI chat and agent interfaces, all to WCAG 2.2 AA. Also picks React UI libraries (toasts, drawers, command menus). Gives component specs, state matrices, sizes, density and keyboard and accessibility behavior.
typography
Choose, pair, size and set type for brand, web, app, print, slides, signage and motion: modular scales, fluid clamp() type, measure, leading, tracking, OpenType features, font licensing and web font loading, and multiscript setting for CJK, Arabic, Hebrew, Devanagari and Thai. Use when selecting or pairing fonts, building a type scale or type tokens, fixing weak hierarchy or bad line breaks, setting long-form text or numbers, loading web fonts, or localizing type for another market.
reference-reconstruction
Reconstructs the observed interface and behavior of a supplied app, site or screenshot set using a screen index, measurements, state and command maps, reusable components and matched-condition comparisons. Use when asked to reverse engineer, clone, reproduce or match a reference product, then adapt it if requested.
print-packaging-social
Load before any print, packaging, label, barcode, social, out-of-home, slide-deck or email design question, even a quick one, and before making finished collateral files. Specs: bleed, safe zones, 300ppi, CMYK, PDF/X preflight, dielines, barcodes, social formats with 9:16 safe areas, billboard letter heights, 16:9 decks, bulletproof email. Renders token-driven brand books, sell sheets, cards, carousels and decks to PDF and PNG with a Canva editable twin.