divine-mobile: Skill for Claude Code

Divine Context

The divine-context repo is the cross-repo handbook for the diVine platform. Every divine-* repo's AGENTS.md should pull in @../divine-context/AGENT_CONTEXT.md, but if it doesn't, load it manually before doing real cross-repo work.

On disk

Cloned as a sibling of the current repo:

~/code/divine/
├── divine-context/          ← read this
├── divine-web/
├── divine-mobile/
├── divine-funnelcake/
└── ... (~50 divine-* repos)

If divine-context isn't cloned:

(cd ~/code/divine && [ -d divine-context ] || gh repo clone divinevideo/divine-context)

Reading divine-context

For everyday work, AGENT_CONTEXT.md is enough. It links out to deeper files:

These files describe state at the time they were written. If a file in a divine-* repo contradicts divine-context, trust the code — and if the contradiction is durable, propose a divine-context update (see below).

Updating divine-context

When you learn a cross-repo fact while working in a divine-* repo, propose it back. Cross-repo means: would an agent in a different divine-* repo benefit from knowing this? If no, it stays in this repo's AGENTS.md or .claude/rules/.

Workflow

1. Read this repo's key files (5 min, no deep dive): README.md, AGENTS.md, .claude/rules/*, docs/**, package.json / Cargo.toml / pubspec.yaml / go.mod, top-level src/.
2. Read every divine-context file (they're short).
3. Build a proposal list — for each item: one line of what, one line of evidence (path:line in this repo).
4. Show the proposal list to the user before editing anything. Wait for approval.
5. For approved items only, branch from origin/main (not local main, which may be stale) and make the edits:

   cd ~/code/divine/divine-context
   git fetch origin main
   git worktree add .claude/worktrees/dc-<topic> -b update-from-<thisrepo>-<topic>-$(date +%Y-%m-%d) origin/main
   # edit files
   cd .claude/worktrees/dc-<topic>
   git add <only the files you changed>          # never -A
   git commit -m "<short desc>: <what changed>"
   git push -u origin HEAD
   gh pr create --title "..." --body "..."
   

   Use a worktree inside the divine-context checkout. Other agents may be editing divine-context concurrently; isolating in a worktree avoids branch-state collisions. Put it in .claude/worktrees/ (gitignored there) — not /tmp. On macOS /tmp is swept, and a worktree there takes any uncommitted work with it; see WORKTREES.md in divine-context. Remove it with git worktree remove once the PR merges, since nothing cleans it up for you.
6. One logical change per PR. Five unrelated improvements = five PRs.