Browser Automation Edge Cases
aden-hive/hive
Step-by-step procedure for debugging browser automation failures on complex sites such as LinkedIn, Twitter/X, single-page apps and Shadow DOM pages.
Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions.
MITAuto-check passed
Install Vc Scenario
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-scenario --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vc-scenario .claude/skills/vc-scenario && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vc-scenario" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-scenario into .claude/skills/vc-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-scenario", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-scenarioType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-scenario --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/vc-scenario .agents/skills/vc-scenario && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vc-scenario" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-scenario into .agents/skills/vc-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-scenario", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-scenario --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/vc-scenario .cursor/skills/vc-scenario && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vc-scenario" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-scenario into .cursor/skills/vc-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-scenario", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/withkynam/vibecode-pro-max-kit.git --path .claude/skills/vc-scenario--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-scenario --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/vc-scenario .gemini/skills/vc-scenario && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vc-scenario" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-scenario into .gemini/skills/vc-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-scenario", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install withkynam/vibecode-pro-max-kit vc-scenarioInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/vc-scenario .github/skills/vc-scenario && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vc-scenario" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-scenario into .github/skills/vc-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-scenario", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-scenario --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/vc-scenario .opencode/skills/vc-scenario && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vc-scenario" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-scenario into .opencode/skills/vc-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-scenario", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vc-scenario- GitHub stars
- 1.1k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 758 words
- Files
- 1
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions.
- Works in 4 steps: Reads the actual source files being… → Locates and reads existing test files… → Reads any Public Contracts affected… → …
- SKILL.md covers Mode Selection, When to Use, When NOT to Use and 12 Decomposition Dimensions, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vc Scenario is an agent skill from withkynam/vibecode-pro-max-kit. Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use before implementation or testing to catch issues early.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Your AI forgets. This remembers. Spec-driven coding harness for vibecoders, product owners, CEOs and real builders — self-improving context memory, 15 agents, 33 skills working…. The licence is MIT.
Example prompts
- “/vc-scenario”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Reads the actual source files being modified (from plan Touchpoints)
- Locates and reads existing test files for those files (via grep for import paths or describe blocks)
- Reads any Public Contracts affected (from plan's Public Contracts section)
- Returns: real function signatures, actual data shapes, existing test coverage gaps, real failure modes visible in the code
What it can do on your machine
Read from SKILL.md and the folder at commit 3bcb2f9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vc Scenario loads about 1.9k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 758 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from withkynam/vibecode-pro-max-kit at commit 3bcb2f9, republished under its MIT licence (© withkynam). 758 words, ~1,886 tokens.
Download SKILL.mdSave it as
.claude/skills/vc-scenario/SKILL.md (or your agent's skills folder).- name
- vc-scenario
- description
- Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use before implementation or testing to catch issues early.
- argument-hint
- <file path or feature description>
- trigger_keywords
- edge cases, test scenarios, what could go wrong
- layer
- helper
- metadata.author
- claudekit
- metadata.attribution
- Scenario exploration pattern adapted from autoresearch by Udit Goenka (MIT)
- metadata.license
- MIT
- metadata.version
- 1.0.0
vc-scenario — Edge Case & Scenario Explorer
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Decompose any feature or code path across 12 dimensions to surface edge cases, risks, and test targets before implementation begins.
Mode Selection
Choose a mode before generating scenarios. Default is Simple unless a trigger condition applies.
Simple Mode (default)
Generates edge cases from the plan description, checklist item, or approach text provided in the prompt. No subagent spawned.
Use when:
- The checklist item is self-contained and clearly described
- Blast radius is narrow (1–2 files, single package)
- No auth, billing, schema, or external API surface is touched
- Speed matters and hypothetical coverage is sufficient
Deep Mode
Spawns a research subagent to read the actual source before generating scenarios. Scenarios reference real variable names, real function signatures, and real failure modes visible in the code rather than hypothetical ones.
Trigger conditions (any one):
- Checklist item modifies an auth, billing, schema, or external API surface
- Blast radius spans 3+ files or 2+ packages
- The plan marks the item as
HIGH_RISK - Caller explicitly requests deep mode
Deep mode subagent steps:
- Reads the actual source files being modified (from plan Touchpoints)
- Locates and reads existing test files for those files (via grep for import paths or describe blocks)
- Reads any Public Contracts affected (from plan's Public Contracts section)
- Returns: real function signatures, actual data shapes, existing test coverage gaps, real failure modes visible in the code
The orchestrator then generates scenarios using the research output.
Output quality difference
| Mode | Example scenario |
|---|---|
| Simple | "What if the input is null?" |
| Deep | "What if creditBalance.available is 0 but creditBalance.pending is positive — does deductCredits(amount) check available-only or available + pending?" |
Simple mode surfaces generic edge cases quickly. Deep mode surfaces scenarios that are only discoverable by reading the actual implementation.
When to Use
- Before implementing complex or stateful features
- Before writing tests (generates test targets)
- Risk assessment during planning or code review
- API design review — surface contract edge cases early
When NOT to Use
- Trivial single-line changes or cosmetic UI tweaks
- Already well-tested, stable code with no recent modifications
- Pure configuration changes with no logic paths
12 Decomposition Dimensions
Not all 12 apply to every feature. Identify relevant dimensions first, then generate scenarios only for those.
| # | Dimension | What to Look For |
|---|---|---|
| 1 | User Types | admin, guest, banned, new user, power user, bot/scraper |
| 2 | Input Extremes | empty, null, max length, unicode, special chars, SQL/script injection |
| 3 | Timing | concurrent access, race conditions, timeout, slow network, retry storms |
| 4 | Scale | 0 items, 1 item, 1M items, pagination boundary, cursor wrap |
| 5 | State Transitions | first use, mid-flow abort, resume after crash, partial completion |
| 6 | Environment | mobile/low-end CPU, no JS, screen reader, proxy/VPN, different timezone/locale |
| 7 | Error Cascades | DB down, API timeout, disk full, OOM, network partition, partial write |
| 8 | Authorization | expired token, wrong role, shared/public link, CORS, CSRF, privilege escalation |
| 9 | Data Integrity | duplicate entries, orphan references, encoding mismatch, concurrent schema migration |
| 10 | Integration | webhook replay, API version mismatch, third-party outage, contract drift |
| 11 | Compliance | GDPR deletion request, audit logging gap, data retention, accidental PII exposure |
| 12 | Business Logic | edge pricing (zero/negative), coupon stacking, refund after partial delivery, free tier limits |
Show full SKILL.md (228 more words)Show less
Workflow
Step 0 — Select mode using the Mode Selection rules above.
Simple mode:
- Parse feature description or checklist item from the prompt
- Filter dimensions — mark which of the 12 apply; skip irrelevant ones explicitly
- Generate 3–5 scenarios per relevant dimension
- Categorize severity — Critical / High / Medium / Low
- Output as structured table (see format below)
- Summarize total scenario count by severity
Deep mode:
- Spawn research subagent — pass Touchpoints, Public Contracts, and checklist item text
- Subagent returns real function signatures, data shapes, coverage gaps, visible failure modes
- Filter dimensions using research output to remove inapplicable ones
- Generate 3–5 scenarios per relevant dimension, referencing actual variable/function names
- Categorize severity — Critical / High / Medium / Low
- Output as structured table annotated with source evidence (file + line where relevant)
- Summarize total scenario count by severity
Severity Criteria
| Level | Meaning |
|---|---|
| Critical | Data loss, security breach, auth bypass, silent corruption |
| High | Feature broken for a subset of users, data inconsistency |
| Medium | Degraded UX, recoverable error not surfaced to user |
| Low | Minor visual glitch, non-blocking warning |
Output Format
## Scenario Report: [target]
Dimensions analyzed: [list]
Dimensions skipped: [list + reason]
| # | Dimension | Scenario | Severity | Expected Behavior |
|---|-----------|----------|----------|-------------------|
| 1 | Input Extremes | Empty string for required name field | High | Return 400 with field error |
| 2 | Authorization | Expired JWT accessing protected route | Critical | Redirect to login, invalidate session |
| 3 | Timing | Two users submit same form simultaneously | High | Idempotency key or conflict error |
### Summary
- Critical: N
- High: N
- Medium: N
- Low: N
- Total: N scenarios across X dimensionsIntegration with Other Skills
| Next Step | Skill | How |
|---|---|---|
| Generate test cases from scenarios | vc-test | Pass scenario table as input context |
| Inform implementation plan risks | generate-plan / plan-agent | Paste Critical/High rows into risk assessment |
| Deep persona debate on top risks | vc-predict | Feed Critical scenarios as the change proposal |
Example Invocations
# Simple mode (default — self-contained, narrow blast radius)
/vc-scenario src/api/payment.ts
/vc-scenario "User registration with OAuth providers"
/vc-scenario src/middleware/auth.ts
# Deep mode (auto-triggered: billing surface, 3+ files)
/vc-scenario "Deduct credits on model usage — touches CreditBalance, CreditTransaction, usage-sync.ts"
# Deep mode (explicit request)
/vc-scenario --deep "Add multi-tenancy to the database layer"© withkynam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/vc-scenario of withkynam/vibecode-pro-max-kit.
Open the folder on GitHubat commit 3bcb2f9
Compare with similar skills
Vc Scenario next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vc Scenario this skillwithkynam/vibecode-pro-max-kit | 1.1k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Browser Automation Edge Casesaden-hive/hive | 11k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dce Edgevercel/next.js | 143k | — | ~1k | Automated safety check: Pass | MIT | |
| Deliver Edge Casesproduct-on-purpose/pm-skills | 715 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Edge Casesrohunj/claude-build-workflow | 231 | — | ~1.5k | Automated safety check: Pass | None | |
| Edge Case GeneratorArabelaTso/Skills-4-SE | 253 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Dce Edge
vercel/next.js
DCE-safe require() patterns and edge runtime constraints. An agent skill from vercel/next.js.
Deliver Edge Cases
product-on-purpose/pm-skills
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for.
Edge Cases
rohunj/claude-build-workflow
Analyze a PRD for edge cases, failure modes, and scenarios that might be missed.
Edge Case Generator
ArabelaTso/Skills-4-SE
Automatically identify potential boundary and exception cases from requirements, specifications, or existing code, and generate comprehensive test cases targeting boundary conditions, edge cases…
Case Review
sickn33/agentic-awesome-skills
Quality-gate review of a reverse-engineering or assessment case package: scope readiness, Evidence-to-Finding-to-Path traceability, work-item coverage, timeline consistency, and artifact hashes.
More from withkynam/vibecode-pro-max-kit
All 32 skills in this repoLibrary Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
Vc Sequential Thinking
withkynam/vibecode-pro-max-kit
Apply step-by-step analysis for complex problems with revision capability.
Agent Browser Automation
withkynam/vibecode-pro-max-kit
Drives a browser through the agent-browser CLI, using compact snapshots with element refs to keep context small in long sessions, plus video recording and cloud browsers.
Context Routing Audit
withkynam/vibecode-pro-max-kit
Audits a project's context routing, skill discoverability and skill wiring by running a chain of validator scripts and fixing whatever they report.
Active Plan Audit
withkynam/vibecode-pro-max-kit
Reviews a codebase's active plan files for staleness and completion, then archives only the ones confirmed done or obsolete against the real code.
Systematic Debugging and Investigation
withkynam/vibecode-pro-max-kit
Forces root-cause investigation before any fix, combining a four-phase debugging method with log, CI and performance investigation techniques and a rule against unverified completion claims.
Questions about Vc Scenario
What does Vc Scenario do?
Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Vc Scenario is an agent skill from withkynam/vibecode-pro-max-kit. Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions.
How do I install Vc Scenario in Claude Code?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a claude-code`. Or copy the skill folder (.claude/skills/vc-scenario in withkynam/vibecode-pro-max-kit) into .claude/skills/vc-scenario in your project. Claude Code loads it when a task matches its description.
How do I install Vc Scenario in Codex?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a codex`. Or copy the skill folder (.claude/skills/vc-scenario in withkynam/vibecode-pro-max-kit) into .agents/skills/vc-scenario in your project. Codex loads it when a task matches its description.
Can I use Vc Scenario in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-scenario -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vc-scenario, .gemini/skills/vc-scenario, .github/skills/vc-scenario and .opencode/skills/vc-scenario in your project.
What does Vc Scenario need to run?
SKILL.md names no scripts, command-line tools or credentials: Vc Scenario is instructions for the agent only.
Does Vc Scenario access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vc Scenario safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vc Scenario use?
Vc Scenario is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vc Scenario use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vc Scenario?
Skills that share tags, products or a category with Vc Scenario: Browser Automation Edge Cases (aden-hive/hive, 11k stars), Dce Edge (vercel/next.js, 143k stars), Deliver Edge Cases (product-on-purpose/pm-skills, 715 stars) and Edge Cases (rohunj/claude-build-workflow, 231 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vc Scenario?
withkynam (a GitHub user) maintains it in withkynam/vibecode-pro-max-kit, which has 1,145 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on June 21, 2026.
Source: withkynam/vibecode-pro-max-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.