All authors
Claude Skills by EPISTEX0
github.com/EPISTEX07 skills0 installs0 views
- Verify AppRun the real Notes app in headless Chromium, drive it through a feature's scenarios, and produce evidence (screenshot, console log, CDP performance trace, report). Use after any change to src/ and before claiming a feature works, a bug is fixed, or opening a PR. Also use to reproduce a vague bug report or screenshot.Votes: 0GitHub stars: 3
- Are You Sure You Need XChallenge skill. Use when you are about to reach for a risky API or pattern ({{RISKY_LIST}}, for example requestAnimationFrame, useEffect, setTimeout polling, global mutable state, manual DOM access). Asks for evidence that it is needed, lists safer alternatives, and states what the PR must show if you proceed.Votes: 0GitHub stars: 3
- Create VerificationBootstrap verification for this repo. Explore the codebase with parallel subagents (routes, top-level components, menus, keybindings, test ids), write verify-app/SKILL.md and the feature map directory verify-app/references/features/, add missing stable selectors, then prove it works by verifying 2-3 features end to end. Use once per repo, or when verification is missing or badly out of date.Votes: 0GitHub stars: 3
- InvestigateFind the root cause of a bug, regression, slowdown or surprising behavior without guessing. Use before stating any cause or proposing a fix for a problem you have not already proven. Requires reading the actual code path, reproducing first, holding at least two hypotheses, and separating observed facts from inference.Votes: 0GitHub stars: 3
- Maintain VerificationKeep the feature map (verify-app/references/features/) and its selectors in sync with the code. Use on any PR or change that adds, renames, moves or removes a feature, route, menu item, keyboard shortcut or test id, and whenever a verification run finds a stale or wrong feature file.Votes: 0GitHub stars: 3
- Team ModeRouter for {{OWNER}}'s way of working. Use for "{{OWNER}} mode", "/team-mode", or when asked to work to this team's standard of rigor (concise detailed answers, deliberate subagents, plain prose, simple code, verified work). Routes each situation to the leaf skill or playbook that owns it.Votes: 0GitHub stars: 3
- Verify AppRun the real {{APP_NAME}} the way users reach it, drive it, and capture evidence (screenshot, console errors, performance trace, heap snapshot). Use to reproduce a bug report, verify a fix or feature before claiming it works, or measure performance. Never report "should work" without evidence from a real run.Votes: 0GitHub stars: 3