agentleFS
Sign inStart free
harrychuangharrychuang/cursor-skills/cross-platform-parity/SKILL.md

cross-platform-parity

Skill19 starsChanged 5 months agoNo licenceView on GitHub

Export a lead-to-follower platform parity handoff pack after the lead platform's feature slice merges to its integration branch, or audit the follower platform against that pack before and after implementation. Derives the freeze point, change inventory, screen-by-state matrix, visual values, string ids, behavior contract, API/remote-config/event keys, shared component impact and declared platform differences from the merged diff and source code instead of narrative docs; project-specific paths and patterns come from a JSON project profile. Use whenever one platform's feature is handed to the other (iOS to Android or the reverse), the second platform must match an existing implementation, or a cross-platform parity report is requested; not for shared contract rules, feature planning or single-platform work.

The file

Create a free account to mount

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