iapkit-e2e-petgu
Skill166 starsChanged 5 months agoMITView on GitHub
Use for IAPKit product sync E2E testing in packages/kit with the Petgu React Native app, localhost dashboard, App Store Connect, and Google Play Console. Triggers when verifying kit product/entitlement create, update, delete, pull, push, or store sync behavior with Petgu.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/openiap-ssot.mdcCursor rule
- add-showcase-appSkill
- e2e-matrix-runner-appleSkill
- e2e-matrix-runner-googleSkill
- e2e-matrix-runnerSkill
- generate-docSkill
- github-labelsSkill
- iapkit-e2e-martieSkill
- loop-reviewSkill
- opencollective-stewardSkill
- openiap-workflowsSkill
- rebase-mainSkill
- review-selfSkill
- ship-releaseSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read it and follow it exactly — default targets, safety rules, the standard workflow, known good Petgu products, expected store behavior, …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
IAPKit Petgu E2E (Claude Code)
The canonical procedure lives in .codex/skills/iapkit-e2e-petgu/SKILL.md.
Read it and follow it exactly — default targets, safety rules, the standard
workflow, known good Petgu products, expected store behavior, and reporting
requirements are agent-agnostic and apply as written.
Claude Code Notes
- Apple product IDs are permanently unusable after deletion; treat the canonical safety rules as hard gates and only ever delete temporary SKUs created for the current verification run.
- Where the canonical file prefers temporary IDs under
dev.hyo.petgu.codex.*, IDs underdev.hyo.petgu.claude.*are equally acceptable — what matters is that the SKU is clearly temporary and is removed from IAPKit and both stores during cleanup. - Where it says to use Chrome for logged-in Play Console / App Store Connect tabs, use Claude's browser tooling (Claude in Chrome) against the user's existing signed-in session; never handle store credentials directly.
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
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.

