daveebbelaar/bama

user-stories

Prioritized backlog of user stories with checkable acceptance criteria (docs/STORIES.md) for a macOS app, built from a brief, research, or screen index.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/daveebbelaar/bama --skill user-stories

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

User stories

Screens show what an app looks like. Stories say what a person does with it. You build and test stories, not screens.

Read docs/BRIEF.md, docs/research/*.md, and docs/screens/INDEX.md where they exist. Write docs/STORIES.md.

Story format

markdown
### S-012 Complete a task with the keyboard
As the user, I select a task and press Command-Return to complete it.
Screens: 01-inbox.png, 02-today.png
Depends: S-004
Acceptance:
- [snap] The circle fills and the row fades out within half a second.
- [self] An "Undo" banner shows for five seconds; Command-Z also undoes it.
- [unit] A recurring task moves to its next date.
Status: todo
  • One action per story. "Rename a project from its context menu", not

"Manage projects".

  • Every acceptance line starts with how it is checked: [snap] snapshot,

[unit] unit test, [self] self-test, [manual] a person must try it. "Works well" is not checkable.

  • Screens: links reference screenshots, so improve-loop knows what to

compare. Without a reference app, name the snapshot pages that will show the story. A panel, sheet, or menu needs its own snapshot page.

  • Depends: (optional) lists stories that must be done first.
  • Keep a control and the only surface that shows it in one story: a

highlighting field that lives only in the quick-add panel ships with the panel.

  • Status: todo, doing, done, or dropped.

Milestones

Each milestone ends with an app the user can use for a day.

  1. M1 Core loop: the one thing the app is for, end to end. Data

survives a restart.

  1. M2 Organize: the main structure, sidebar pages, moving items.
  2. M3 Time: dates, Today and Upcoming, recurrence, reminders.
  3. M4 Speed: quick-add panel, global shortcut, natural language input,

keyboard navigation, search, menu commands.

  1. M5 System: menu bar, Share menu, Shortcuts, notifications, CLI.
  2. M6 Polish: drag and drop, context menus, empty states, icon, settings.

Rename milestones to fit the app. Inside a milestone, stories that others depend on come first.

Seed data

Every attribute the seed data sets (symbols, colors, notes) is something a story lets the user create in the app. Otherwise snapshots show features no one can use.

Leave things out

Drop what exists only for other people or for the vendor: accounts, sharing, teams, integrations, upgrade prompts, gamification. List them under ## Dropped, one line each, so the decision is visible.

UX notes

For each M1 story that adds a screen, an action, or words, call the Skill tool with ux-design. It adds a UX: block under the acceptance lines and starts docs/GLOSSARY.md, so every story uses the same names. Later milestones get their UX notes in improve-loop, just before they are built.

Size check

M1 has 5 to 10 stories. Over 60 stories in total means version one is too big: move stories to ## Later.

Done when every main job in the brief, every "Version one: yes" row in the research matrix, and every screen in the index maps to a story or a Dropped line, and every M1 story with UI has a UX: block.

do mesmo repositório

Mais Skills

Todos os Skills
daveebbelaar
Comunidade

mac-design

Design rules that make a SwiftUI app look and feel like a native Mac app on macOS 26 and later, from Apple's eight design principles to Liquid Glass, layout, toolbars, menus, search, keyboard, type, color, and dark mode. Use when building or reviewing any window, sidebar, toolbar, menu, panel, or settings screen, or when the user asks for a more native, Apple-like, or better designed app.

Instalações / 1h
1
GitHub Stars
1,9 mil
Atualizado
5 de nov.
daveebbelaar
Comunidade

os-integrations

Deep macOS integrations for a native app, such as global hotkeys, menu bar items, floating panels, window control with Accessibility, screen capture and recording, clipboard, Shortcuts and Spotlight, URL schemes, login items, a CLI, and the permissions each one needs. Use when an app must reach outside its own window or control other apps.

Instalações / 1h
1
GitHub Stars
1,9 mil
Atualizado
5 de nov.
daveebbelaar
Comunidade

agent-cli

Optional command line and MCP server for a macOS app, so Claude Code, Codex, and scripts can drive it (list, add, change, search, act) through the running app. Use when the user wants agents to work with their app or its data, asks for a CLI, an MCP server, or automation for the app, or says "Claude should be able to use my app".

Instalações / 1h
4
GitHub Stars
1,9 mil
Atualizado
5 de nov.
daveebbelaar
Comunidade

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.

Instalações / 1h
4
GitHub Stars
1,9 mil
Atualizado
5 de nov.