agentleFS
Sign inStart free
hyodotdevhyodotdev/openiap/.claude/skills/iapkit-e2e-martie/SKILL.md

iapkit-e2e-martie

Skill166 starsChanged 5 months agoMITView on GitHub

Run IAPKit local receipt-validation E2E with the dev.hyo.martie React Native or Expo examples, the compiled packages/kit server, real Convex, and Apple or Google sandbox purchases. Use when preparing an iOS Sandbox Apple Account for a development-signed or TestFlight build, verifying purchase-token or JWS routing, Local (IAPKit) baseUrl behavior, local server logs, receipt validity, transaction finishing, or the Martie purchases view; distinguish safe smoke checks from approval-gated live purchase verticals.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read it and follow it exactly — targets, smoke vs live lanes, safety gates, preflight, server startup, example configuration, the Martie …

    line 9

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

IAPKit Martie Receipt E2E (Claude Code)

The canonical procedure lives in .codex/skills/iapkit-e2e-martie/SKILL.md. Read it and follow it exactly — targets, smoke vs live lanes, safety gates, preflight, server startup, example configuration, the Martie catalog, the approval-gated live vertical, its LIVE RECEIPT PASS assertions, and cleanup are all agent-agnostic and apply as written.

Claude Code Notes

  • The safety gates are non-negotiable in Claude Code too: never press Purchase/Subscribe or confirm a store sheet without explicit approval in the current run, never persist sandbox account credentials, never rotate or reveal IAPKit API keys, and never mutate the store catalog from this workflow.
  • Report results with the same vocabulary: SMOKE PASS / SMOKE FAIL for the server smoke lane, LIVE RECEIPT PASS only when every live-lane assertion holds, and BLOCKED when a device, account, catalog, key, Convex URL, or network route is missing.
  • Also read the Local (IAPKit) Receipt Vertical section of .claude/commands/e2e-tests.md during preflight, as the canonical file requires.

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.

Check your setup, free