agentleFS
mannobeatsmannobeats/hyper-taste/skills/clone/SKILL.md

clone

Skill1 starsChanged 4 days agoMITView on GitHub

Walk through an existing app (a native Mac app with computer use, a web app with a browser, a phone app from screenshots), capture every screen, menu and dialog, write a screen index, and turn it into user stories. Use when the user wants to rebuild, replace or learn from an app, copy its structure, or says "screenshot every screen".

9 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use app-brief, design-from-app and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StijnusSkill

    app-brief

    One-page brief (docs/BRIEF.md) for a new macOS app, written before any code. Use when the user has an app idea, wants to replace an app they pay for, or the research and clone skills are done.

    Also in 3 projects that use this

  • StijnusSkill

    design-from-app

    Rebuild the look of an app the user likes as a native SwiftUI design kit, by measuring its screenshots (sizes, spacing, type, colors, icons), building its parts, and comparing pixel by pixel until they match. Use when the user names an app whose look they want, shares screenshots of one, or says "make it look like X".

    Also in 3 projects that use this

  • launchapp-devSkill

    layout-grid

    Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.

    Also in 3 projects that use this

  • timeplus-ioSkill

    build-and-verify

    Build, compile, run server/client/cluster, execute unit/stateless/SQL tests, verify results, and troubleshoot build/test failures. Make sure to use this skill whenever the user mentions building, compiling, ninja, cmake, running tests, test failures, starting the server, or pre-commit checks, even if they just say 'it doesn't build' or 'the test broke'.

    Also in 3 projects that use this

  • CrystalPlatformsSkill

    agent-cli

    Design and audit CLIs that AI agents (Claude Code, Codex, automated pipelines) consume. Applies ten agent-native principles in two tiers — Tier 1 table stakes (non-interactive default, structured output, errors that enumerate, safe retries, bounded responses) and Tier 2 compounding (cross-CLI vocabulary, three-layer introspection, async-aware execution, persistent profiles, two-way I/O) — with a Blocker / Friction / Optimization severity rubric across six command classes (read, mutate, stream, bootstrap, async, config). Use when building, reviewing, or specifying a CLI for agent invocation, mentions argparse, click, cobra, clap, commander, yargs, oclif, thor, agent-friendly or agent-native CLI design, --json output, exit codes, idempotent commands, --wait flags, agent-context introspection, persistent profiles, --deliver routing, --force bypass, vocabulary consistency, or repos with cli.py, main.go, src/cli.rs, bin/<tool>. Skip general shell scripting and human-only TUIs.

    Also in 3 projects that use this

  • bborok1234Skill

    design-kit

    새 프로젝트/화면의 디자인 시스템을 프로덕션급으로 빠르게 세우고(부트스트랩), 이미 만든 UI의 퀄이 안 잡힐 때 진단→교정하고, AI 슬롭 없이 폴리싱하는 개인 디자인 게이트. "디자인 시스템 잡아줘", "랜딩/UI 만들어", "슬롭 잡아줘", "이 화면 폴리싱", "퀄리티가 안 잡혀/디자인 고쳐줘/왜 싸구려 같지", 새 프론트엔드 시작 시 적용. 미학(팔레트·폰트·정체성)은 인터뷰로 함께 설계하고, 시스템 구성법·판단룰·안티슬롭·진단교정·빌드루프는 프로젝트 무관하게 재사용.

    Also in 3 projects that use this

  • +1 more from Stijnus

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every sidebar item, top to bottom.

    line 49
  2. Distinctive:

    Every view mode (list, board, calendar), sort menu, filter menu.

    line 50
  3. Distinctive:

    Command map: every menu item and keyboard shortcut.

    line 96
  4. Very specific:

    Call the Skill tool with user-stories.

    line 105

“Common” is measured: kept by at least 6 in 10 of the 9 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 isUse
A native Mac app, or ElectronComputer use
A web appA browser tool
A phone appScreenshots from the user, or a simulator

Computer use needs Accessibility and Screen Recording permissions. Ask for access to the reference app only.

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: find the app's window id (computer use, or a short CGWindowListCopyWindowInfo script) and capture it with screencapture -x -o -l <windowID> docs/screens/01-inbox.png. 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

  1. Main window, default page.
  2. Every sidebar item, top to bottom. Expand collapsed groups.
  3. Every view mode (list, board, calendar), sort menu, filter menu.
  4. One item opened in detail: panel, fields, sub-items.
  5. Creation flows: add button, quick-add panel (global shortcut), inline editor. Empty and half filled in, then Escape.
  6. Context menus on an item, a section, a sidebar entry.
  7. The menu bar: every menu once. Record every item and shortcut.
  8. Settings: every pane.
  9. Empty states.
  10. 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

Call the Skill tool with 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.