agentleFS
Sign inStart free
daveebbelaardaveebbelaar/bama/.claude/CLAUDE.md

bama

CLAUDE.md1.7k starsChanged 11 days agoMITView on GitHub

Agent skills for building native macOS apps. Installed as a Claude Code and Codex plugin from .claude-plugin/, or through npx skills add. AGENTS.md at the root is a copy of this file (.claude/CLAUDE.md); keep them identical. - skills/<stage>/<name>/SKILL.md, stages in pipeline order: start, plan, code, design, ship. - References sit next to SKILL.md (recipes.md, patterns.md) and are linked relatively. Scripts go in scripts/, templates in template/. - agents/openai.yaml in every skill: Codex display name and short description. A user-invoked skill…

  • Commits and pushes

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about daveebbelaar/bama

The biggest 5 of 42 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 42

Talked about on GitHub, YouTube and the web (42 times).

On GitHub · 20

15 more on GitHub

On YouTube · 13

8 more on YouTube

On the web · 9

4 more on the web

The file

We split this CLAUDE.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow Matt Pocock's writing-for-agents rules:

    line 24
  2. Distinctive:

    Every step ends on a checkable condition.

    line 31
  3. Distinctive:

    No em dashes. Plain words, short sentences, active voice.

    line 38
  4. Very specific:

    Create skills/<stage>/<name>/SKILL.md and agents/openai.yaml.

    line 42
  5. Very specific:

    Add it to plugin.json skills, the README table, and the router (skills/start/bama/SKILL.md).

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “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
CLAUDE.md

BAMA

Agent skills for building native macOS apps. Installed as a Claude Code and Codex plugin from .claude-plugin/, or through npx skills add. AGENTS.md at the root is a copy of this file (.claude/CLAUDE.md); keep them identical.

Layout

  • skills/<stage>/<name>/SKILL.md, stages in pipeline order: start, plan, code, design, ship.
  • References sit next to SKILL.md (recipes.md, patterns.md) and are linked relatively. Scripts go in scripts/, templates in template/.
  • agents/openai.yaml in every skill: Codex display name and short description. A user-invoked skill also sets policy.allow_implicit_invocation: false.
  • .claude-plugin/plugin.json lists every shipped skill in skills.
  • specs/<app>.md: build plans for small apps, taken from Onyx. Each has Brief, How it works, Stories, Gotchas, and a "Done when" line, in that order. specs/README.md lists them.

Writing skills

Follow Matt Pocock's writing-for-agents rules:

  • The description is a context pointer: one short sentence on what it is, then "Use when" and one trigger per branch. Front-load the leading word.
  • Inline what every branch needs. Push what only some branches need into a sibling file behind a link.
  • Every step ends on a checkable condition. Every skill ends with a "Done when" line.
  • Prompt the positive. Use a prohibition only as a hard guardrail, next to the positive target.
  • Cache only what the environment cannot tell the agent: conventions, reasons, gotchas from real apps.
  • One skill calls another with "Call the Skill tool with <name>".
  • No em dashes. Plain words, short sentences, active voice.

Adding a skill

  1. Create skills/<stage>/<name>/SKILL.md and agents/openai.yaml.
  2. Add it to plugin.json skills, the README table, and the router (skills/start/bama/SKILL.md).
  3. Run claude plugin validate . --strict.

Releasing

  1. Bump version in plugin.json. Installed copies update only when this string changes. Keep version out of marketplace.json.
  2. Run claude plugin validate . --strict.
  3. Merge to main. Use a merge commit for a branch with contributor commits, so their pull requests show as merged.
  4. On main, run claude plugin tag . --push. It creates bama--v<version>.
  5. Run gh release create bama--v<version> --generate-notes.

Done when claude plugin update bama@bama installs the new version.

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.

Check your setup, free