From 57560319f07187fadaf1eb3da00d8c49a8340fbd Mon Sep 17 00:00:00 2001 From: ZGaetano Date: Fri, 29 May 2026 20:09:55 -0400 Subject: [PATCH] chore: add skills library --- claude-skills/verify.md | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 claude-skills/verify.md diff --git a/claude-skills/verify.md b/claude-skills/verify.md new file mode 100644 index 0000000..68ec88f --- /dev/null +++ b/claude-skills/verify.md @@ -0,0 +1,39 @@ +--- +name: verify +description: Launch and drive the app to confirm a change actually works. Use when asked to verify a fix, test a feature, confirm behavior, or validate before pushing. +--- + +# Verify / Webapp Testing Skill + +Use when: asked to run the app, verify a fix works, test a feature end-to-end, or confirm behavior before shipping. + +## Steps + +1. **Identify what to verify** — restate the specific behavior or fix being confirmed. + +2. **Start the app** — find the run command (check package.json scripts, README, or ask): + - `npm run dev`, `npm start`, `python manage.py runserver`, etc. + - Note the URL/port it starts on. + +3. **Define test cases** before opening the browser: + - Happy path (expected normal use) + - Edge cases (empty input, max length, no data) + - Error path (invalid input, network failure if testable) + +4. **Execute each test case** — use browser tools or curl: + - Screenshot or describe what you see + - Check console for errors (browser devtools or server logs) + - Verify network requests return expected status/data + +5. **Check regression** — does anything that worked before still work? + +6. **Report results** clearly: + - ✅ PASS / ❌ FAIL for each test case + - Include exact error messages for failures + - Screenshots or response bodies as evidence + +## Rules +- Never mark something as verified without actually running it. +- If the app won't start, fix that first and document what was wrong. +- If a test fails, diagnose root cause before declaring done. +- Log file checks count as verification for server-side behavior.