fullstorydev/subtext-verify/subtext-recipe-sightmap-setup
Claude Code and agent skill by fullstorydev/subtext-verify
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Short recipe to create sightmap definitions for a project from scratch.
Install
npx vskill@latest install fullstorydev/subtext-verify/subtext-recipe-sightmap-setupSKILL.md
Recipe: Sightmap Setup
PREREQUISITE: Readsightmap-authoring(from Subtext) for the full schema reference, andsubtext-verify-sharedfor the sightmap upload step.
Steps
- Navigate to the page:
live-view-navigate(url=...)orlive-view-new(url=...) - Take a baseline snapshot:
live-view-snapshot()to see the current a11y tree with generic roles - Identify key UI components in the snapshot (navigation, forms, cards, modals, etc.)
- Find good selectors using
live-view-inspect()— this returns the full component tree with CSS selectors (tag, id, classes,data-*attributes,aria-*,href, etc.) on every node. Use it to identify stable targeting info, then switch back tolive-view-snapshot()for normal interaction.
Prefer data-* attributes when available — they're stable and semantically meaningful (e.g., [data-component="ProductTile"], [data-testid="checkout-button"]).
- Create `.sightmap/components.yaml` with component definitions (see
sightmap-authoringfor schema) - Add memories to key components — contextual notes that appear in a
[Guide]section at the top of every snapshot. Focus on:
- Auth/access: passwords, test accounts, login flows (e.g.,
"Password is 'argus'") - Stateful components: how toggles, tabs, or modes change the UI (e.g.,
"Audience toggle switches copy between builder/agent perspectives") - Forms: required fields, validation rules, expected formats
- Complex interactions: multi-step flows, known quirks, non-obvious behavior
```yaml
- name: LoginForm
selector: "[data-component='LoginForm']" source: src/components/LoginForm.tsx memory:
- "Test account: user@test.com / password123"
- "Shows CAPTCHA after 3 failed attempts"
```
- Take another snapshot to verify component names appear (definitions are re-read on each snapshot)
- Add views if the app has distinct routes — specify route patterns and view-scoped components
- Add requests if key API endpoints should have semantic names — use
live-net-listto identify them - Verify enrichment: take snapshots on different views, check
[View: ...]headers, semantic names, and[Guide]section with memories all appear
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/subtext-recipe-sightmap-setup/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/fullstorydev/subtext-verify/subtext-recipe-sightmap-setup)