Skip to main content

appeeky.spec.yaml

Everything else in the spec

All optional. Each block is explained on the page that uses it.

Listing files

App Store, appeeky/store/app-store/en-US.yaml:
Google Play, appeeky/store/google-play/en-US.yaml:
Rules for every listing file:
  • A field you leave out is not managed. It is never diffed or pushed. You can adopt the spec one field or one locale at a time.
  • "" clears a field on the store.
  • Values are compared the way the stores store them: trailing spaces and line endings do not count as changes.

Limits

All limits are in characters, the way App Store Connect and Play Console count them. A Cyrillic or Japanese letter is one character.

Folders under appeeky/

.appeeky/ holds the keyword cache (cache/, 7 days), data/ (private business numbers from data pull), media/ (clips rendered with ugc generate --local) and proposal.md (the weekly review’s pull request text). Keep it out of git.

Releases

push writes one file per store per push to appeeky/releases/:
verify adds the checks. Edit the note freely; leave the rest to the CLI.

Experiments

experiment add writes appeeky/experiments/<id>.yaml with a hypothesis, one metric, a baseline, a target and a check date. experiment close records the measured value and the result. See Experiments and screenshots.

Playbook

appeeky/playbook.md is plain Markdown. verify --playbook and experiment close --playbook append one line per result; you can write in it too. Agents read it before proposing a change, so failed ideas are not repeated.