yjmeqt
- 7 skills
- 0 followers
- 9 hours ago last updated
- ▌ Prd · yjmeqtUse when starting or referencing work on a feature module — loads PRD requirements, Figma nodes, and per-platform implementation spec context. Invoke with `/prd <module/feature>` or `/prd <module/feature>#R<n>`.
- ▌ Xc Dev · yjmeqtUse for iOS / Xcode build, run, test, clean/DerivedData, and simulator workflows in projects that have an `.xc-dev/` directory. Routes work through `xc-dev <task>` or builtins like `:clean` instead of raw `xcodebuild`.
- ▌ Remo · yjmeqt bundleUse when Remo is already integrated and you need day-to-day iOS verification with screenshots, capability calls, checkpoints, or a reviewable report of what changed.
- ▌ Remo Setup · yjmeqt bundleUse when adding Remo to an iOS project for the first time — integrating RemoSDK, wiring Remo.start(), choosing between installing the Remo CLI or driving real Chrome DevTools directly, and verifying the running app is reachable.
- ▌ Remo Capabilities · yjmeqt bundleUse when mapping an iOS app's screens, routing, and state into Remo capabilities, registering new capabilities, or updating the capabilities reference after feature changes.
- ▌ Remo Design Review · yjmeqt bundleUse when comparing a running iOS app against Figma designs, constructing the required app state for each screen, capturing screenshots, and writing a design compliance report.
- ▌ Example IOS Feature Dev · yjmeqtUse when building or changing a feature inside examples/ios/RemoExamplePackage/ and you need the agentic dev loop — register Remo capabilities for the new surface, then drive and validate it with the remo CLI plus XcodeBuildMCP.