git.sr.ht/~timofurrer/nine (link)

commit signals (188)

source signals (11)

• CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  Guidance for agents working in this repo.
  
  ## What this is
  
  Nine is the umbrella project/brand for a suite of Android apps built for
  phones with a physical D-pad/keypad and no touchscreen (the target hardware
  T9 predictive text was designed for). Each app follows a `[Letter]9` naming
  convention:
  
  - **L9**: Launcher on 9 keys
  - **C9**: Calendars and Contacts on 9 keys
  - **P9**: Phone on 9 keys
  - **M9**: Messages on 9 keys
  
  Each app ships as its own installable APK with its own F-Droid listing -
  

• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claude/skills/tickets/SKILL.mdvia unspecified

  ---
  name: tickets
  description: How to file, triage, label, work on and close Nine tickets on SourceHut (todo.sr.ht) with the hut CLI, and what each label means. Use whenever you read, create, comment on, label or close a ticket, or the user says "issue", "ticket" or "P1/P2/P3".
  ---
  
  # Tickets
  
  All Nine work is tracked in one SourceHut tracker for the whole suite: **https://todo.sr.ht/~timofurrer/nine**
  (`hut todo ... -t nine`). Ticket URL form: `https://todo.sr.ht/~timofurrer/nine/<id>` (hut prints it with 

• .claude/skills/release/SKILL.mdvia unspecified

  ---
  name: release
  description: Cut a suite-wide Nine release - decide which apps changed, bump versionName/versionCode, write the fastlane changelogs, commit, push, tag and push the tag, then watch the release run and verify the published APKs and F-Droid repo. Use only when the user asks to release (or to bump versions / cut a tag) for L9, C9, P9 or M9.
  ---
  
  # Releasing the Nine suite
  
  A release is one suite-wide CalVer tag. Pushing it makes sr.ht's `.builds/release.yml` re-test and lint every
  module, then

• .claude/skills/chunk-of-work/SKILL.mdvia unspecified

  ---
  name: chunk-of-work
  description: The end-to-end flow for one chunk of work in Nine - understand, propose (survey the user on design/UX/refactoring decisions), implement (with Opus/Sonnet subagents where it pays off), review, test on the phone, commit, push and close the tickets. Use whenever the user asks to fix, implement or change something, directly or by ticket number ("fix #10", "implement #27, #28", "make the dialer do X").
  ---
  
  # A chunk of work
  
  One request from the user ("fix #10, #11", "implem

• .claude/skills/on-device-testing/SKILL.mdvia unspecified

  ---
  name: on-device-testing
  description: When, what and how to test Nine apps on the user's real phone over adb - asking the user to connect it, safety rules for their daily phone, adb patterns for driving the keypad UI and checking providers/alarms/notifications, and labelling tickets needs-device-testing when no phone is available. Use whenever a change touches platform behaviour unit tests can't prove (Telecom, SMS role, notifications, alarms, broadcasts, providers, sync, intents from other apps, permiss

• .claude/skills/commit-messages/SKILL.mdvia unspecified

  ---
  name: commit-messages
  description: How to write commit messages in this repo. Use whenever you create a git commit (or a squash/merge message) here, and when asked to reword one.
  ---
  
  # Commit messages
  
  Follow https://cbea.ms/git-commit/, with the project conventions below. Keep it short and written for a
  person reading `git log` in a year.
  
  ## Subject
  
  - Start with the thing it touches: `L9:`, `C9:`, `P9:`, `M9:` or `Core:` (`Contacts:` for the `:contacts`
    module). No other prefixes - no `feat:`, `fi

ignorefile signals (0)

none