epistex-dev/poteto-kit / templates/skills/verify-app
verify-app
UnverifiedRun 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.3 KB |
| references/cli-contract.md | markdown | 9.8 KB |
| references/cloud-environment.md | markdown | 5.3 KB |
| references/evidence-export.md | markdown | 2.6 KB |
| references/features/README.md | markdown | 8.9 KB |
| references/features/_feature.template.md | markdown | 3.1 KB |
| references/features/cross-cutting-flows.md | markdown | 3.3 KB |
| references/launch-by-app-type.md | markdown | 2.7 KB |
| references/test-account.md | markdown | 3.4 KB |
| references/worktree-isolation.md | markdown | 5.2 KB |
references/features/_feature.template.md
View on GitHub<!-- HOW TO USE:
1. Copy to <feature-id>.md in this directory (the id equals the directory name under {{FEATURES_DIR}}); delete this comment. Add the file to the index in README.md.
2. Write for an agent that has never seen the app. Describe use, not implementation. Every step is something a user does; every selector is something you checked in a running app.
3. Keep the four sections and their order. Sub-feature ids are the names you will cite in proofs ("sub-feature sidebar-toggle: pressed chord, final state X"), and ci/check-coverage.mjs reads them: keep each bullet exactly ``- `<id>` — <one line>``. An id you cannot reach ends with `skip: <reason>` (see "Proof and skip reporting" in README.md).
4. Files starting with "_" are templates and are ignored by the CI check.
-->
# {{Display name}} (`{{feature-id}}`)
{{One paragraph: what this feature is for, where it appears on screen, and how a user would describe it. End with the root selector, for example: Root: `[data-component="{{root-component}}"]`.}}
## Sub-features
One line each: a stable id, then what it is. A sub-feature that cannot be reached ends with `skip: <reason>`.
- `{{feature-id}}-toggle` — {{show or hide it; mention the shortcut}}
- `{{feature-id}}-{{sub-feature-2}}` — {{...}}
- `{{feature-id}}-{{sub-feature-3}}` — {{behind feature flag `{{FLAG_NAME}}`, if gated; add `skip: <reason>` if you cannot enable it}}
- `{{feature-id}}-empty-state` — {{what shows with no data}}
- `{{feature-id}}-error-state` — {{what shows when it fails}}
## How to get to it
User point of view, one bullet per sub-feature: the exact steps, shortcuts and the visible result that tells you that you arrived. Note edge behavior, such as a shortcut that yields to the text editor when it has focus (use the button then).
- **`{{feature-id}}-toggle`:** {{From a normal state press `Cmd/Ctrl+{{KEY}}` or click the "{{Button label}}" button in {{region}}. You arrived when {{visible result}}.}}
- **`{{feature-id}}-{{sub-feature-2}}`:** {{steps}}
- **`{{feature-id}}-empty-state`:** {{how to reach it: which data to remove or which fresh account to use}}
- **`{{feature-id}}-error-state`:** {{how to trigger it: for example block the request, or use a fixture}}
## Driving it
How to drive it with {{DRIVER}}.
- **Preconditions:** the baseline in `README.md`, plus {{extra preconditions, such as a seeded record or a specific setting}}.
- **Chords per OS:** macOS `press "Meta+Key{{KEY}}"`; Windows and Linux `press "Control+Key{{KEY}}"`.
- **Selectors:** root `[data-component="{{root-component}}"]`; {{sub-feature}}: `[aria-label="{{label}}"]`; {{sub-feature}}: `[data-action-id="{{action-id}}"]`.
- **Command ids** (documentation only; they point at the handler): `{{command.id}}`.
- **Observable end states** to poll: {{status label text, attribute value, enabled or disabled button}}.
- **Gotchas:** {{things learned the hard way, for example "the hover card opens only after the pointer leaves and re-enters the row", "an ARIA click is not enough for a double-click reset: dispatch two real clicks", "the list is virtualized: scroll before asserting"}}.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |