agentleFS
bitomulebitomule/Koubou/AGENTS.md

Koubou

AGENTS.md211 starsChanged 8 months agoMITView on GitHub

Install the Koubou skill pack so your agent has built-in knowledge of how to generate screenshots: This installs to all detected AI coding agents (Claude Code, Cursor, Windsurf, and others) automatically. Requires Node.js. Koubou generates App Store screenshots from YAML configuration files. Input: YAML config + image assets. Output: pixel-perfect screenshots organized by {language}/{device}/. This project uses a .venv virtualenv at the project root. All commands must run through it: Screenshots are written to the configured output_dir: Example: Screenshots/Generated/en/iPhone_15_Pro_Portrait/welcome_screen.png Koubou…

  • Installs packages
  • Commits and pushes
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Explicit flags only: - no single-letter abbreviations.

    line 19
  2. Very specific:

    No interactive prompts: - use --force to overwrite, --confirm to approve destructive actions.

    line 20
  3. Very specific:

    --help is the source of truth: - run kou --help or kou <command> --help for full flag documentation.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md

AGENTS.md

Agent Skill Setup

Install the Koubou skill pack so your agent has built-in knowledge of how to generate screenshots:

kou install-skills --yes

This installs to all detected AI coding agents (Claude Code, Cursor, Windsurf, and others) automatically. Requires Node.js.

What is Koubou?

Koubou generates App Store screenshots from YAML configuration files. Input: YAML config + image assets. Output: pixel-perfect screenshots organized by {language}/{device}/.

CLI Principles

  • Explicit flags only - no single-letter abbreviations. --verbose not -v.
  • No interactive prompts - use --force to overwrite, --confirm to approve destructive actions.
  • JSON output for agents - pass --output json to get machine-readable output on stdout. Default is table (human-readable rich output).
  • --help is the source of truth - run kou --help or kou <command> --help for full flag documentation.

Project Structure

src/koubou/
  cli.py          # Command-line interface (typer)
  config.py       # YAML parsing with Pydantic models
  generator.py    # Core screenshot generation engine
  renderers/      # Background, text, frame rendering
  frames/         # Device frame PNG assets + Frames.json + Sizes.json

Commands

kou generate config.yaml              # Generate screenshots
kou generate config.yaml --output json # JSON results to stdout
kou list-sizes                         # Show available App Store sizes
kou list-sizes --output json           # JSON sizes to stdout
kou list-frames                        # Show available device frames
kou list-frames iPhone --output json   # Filtered JSON frames to stdout
kou live config.yaml                   # Live editing mode
kou --create-config sample.yaml        # Create sample config
kou --create-config sample.yaml --force # Overwrite existing
kou --version                          # Show version

Virtual Environment

This project uses a .venv virtualenv at the project root. All commands must run through it:

.venv/bin/pip install ".[dev]"      # Install dev deps (includes playwright)
.venv/bin/playwright install chromium  # Install browser for HTML rendering tests
.venv/bin/pytest tests/ -v          # Run tests
.venv/bin/python -m black src/      # Format

Build & Test

make install-dev    # Install with dev dependencies
make format         # Run black + isort
make lint           # Run flake8 + mypy
make test           # Run pytest with coverage
make check          # All of the above
make install-hooks  # Enable pre-commit hooks

Output Structure

Screenshots are written to the configured output_dir:

{output_dir}/
  {language}/
    {device}/
      {screenshot_id}.png

Example: Screenshots/Generated/en/iPhone_15_Pro_Portrait/welcome_screen.png

Upload

Koubou does not handle uploads. Use App Store Connect CLI:

brew install appstoreconnect-cli
asc auth login

asc screenshots upload \
  --version-localization "LOC_ID" \
  --path "./output/en/iPhone_16_Pro_.../" \
  --device-type "IPHONE_69"

The output directory structure maps directly to individual asc upload calls per device type and language. iPhone Duo configs use project.displays and produce one folder per display; both folders go into the same set with --device-type IPHONE_DUO.

Release Process

Version is derived from git tags via setuptools-scm.

# 1. Update CHANGELOG.md with new version section
# 2. Commit all changes
git add -A && git commit -m "Prepare vX.Y.Z release"

# 3. Tag and push
git tag vX.Y.Z
git push origin main --tags

GitHub Actions handles PyPI publishing and Homebrew formula updates on tag push.

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.