Skip to content

docs: add verify-sdk-demo agent skill - #376

Draft
cameronapak wants to merge 2 commits into
mainfrom
cursor/cp/verify-sdk-demo-68fe
Draft

docs: add verify-sdk-demo agent skill#376
cameronapak wants to merge 2 commits into
mainfrom
cursor/cp/verify-sdk-demo-68fe

Conversation

@cameronapak

@cameronapak cameronapak commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

I ran Poteto's /create-verification-skill on the React Web SDK.

Adds a project-local Cursor skill (.cursor/skills/verify-sdk-demo/) so later agents can launch the Vite SDK demo, check that the instance is worth driving, and exercise the live UI with Playwright.

What

  • Skill + feature map for the demo’s user-facing surfaces: Bible Reader, Verse of the Day, Bible Card, Sign in, Theme
  • Helpers: launch.sh, doctor.sh, drive.mjs, cleanup.sh
  • .gitignore exception so .cursor/skills/ can be versioned (other .cursor/ local state stays ignored)

Proven on this branch

Ran the skill’s own loop against a live YVP_APP_KEY:

  1. launch.shhttp://127.0.0.1:5177
  2. doctor.sh → renderer ready (57 verse wrappers)
  3. drive.mjs bible-reader → chapter picker John 1John 2, screenshots + result.json
  4. cleanup.sh → instance and port gone; evidence left at /tmp/verify-sdk-demo/evidence/

Notes

  • Default verification port is 5177 so a human demo on 5173 is left alone
  • Live Bible content still needs VITE_YVP_APP_KEY or injected YVP_APP_KEY
  • Sign-in OAuth is documented but not completed unattended
  • Keep the feature map honest with /maintain-verification-skill as the demo changes
Open in Web Open in Cursor 

Add a project-local skill that launches the Vite SDK demo, checks the
instance, and drives it with Playwright so later agents can prove
reader, VOTD, card, and theme behavior against the live UI.
@changeset-bot

changeset-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 4cef8ae

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

pnpm's recorded pid is not the listener. Doctor now walks ancestors;
cleanup records listenerPid and SIGTERMs the whole descendant tree so
port 5177 is not left behind.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants