dogfood
Skill2 starsChanged 13 days agoMITView on GitHub
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence. Not for test-runner, accessibility-auditor.
81 other projects use a version of this, 19 of them edited.
Adopted by
Most recently taken up by
- rodos4312/Meu-Agenttheir own version, first seen Nov 15, 2026
- getlien/lientheir own version, first seen Nov 15, 2026
- IgorGanapolsky/mac-yolo-safeguardstheir own version, first seen Nov 15, 2026
- axiom-desu/ZCodiumedited, first seen Nov 15, 2026
- lsjwzh/MultiCCtheir own version, first seen Nov 14, 2026
- NousResearch/hermes-agenttheir own version, first seen Nov 13, 2026
Used with
Projects with it also use dep-refs, feature-boundary-planner and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
betacatslingSkilldep-refs
Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.
Also in 5 projects that use this
betacatslingSkillfeature-boundary-planner
Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.
Also in 5 projects that use this
lir-navcooSkillyuanbao
Yuanbao (元宝) groups: @mention users, query info/members.
Also in 18 projects that use this
Cartograf666Skillarchitecture-governance
Bootstrap, document, enforce, and review a project's architecture through layer responsibilities, dependency direction, architecture manifests, legacy baselines, Change Envelopes, cross-layer approval policy, and deterministic architecture checks. Use when starting a project, auditing an existing codebase, planning cross-layer work, preventing architecture erosion, reviewing structural changes, or deciding whether implementation may expand into another layer.
Also in 5 projects that use this
john-data-chenSkilltouchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Also in 7 projects that use this
math-incSkillminecraft-modpack-server
Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.
Also in 5 projects that use this
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 19
- vercel-labs/agent-browser★ 51k36% same
- zai-org/ZCode★ 8.6k36% same
- salesforce/cloudsplaining★ 2.3k36% same
- coder/mux★ 2.1k35% same
- coder/cmux★ 2.1k35% same
- phodal/routa★ 1.8k39% same
- gronxb/codex-relay★ 73312% same
- ZCodium-project/ZCodium★ 25336% same
- gmickel/gno★ 11739% same
- vobase/vobase★ 6037% same
9 more not listed
Wrote their own version · 62
- NousResearch/hermes-agent★ 264ksame name
- coder/coder★ 17ksame name
- callstack/agent-device★ 5.4ksame name
- callstackincubator/agent-device★ 5.3ksame name
- math-inc/OpenGauss★ 1.3ksame name
- Tommy-yw/RunbookHermes★ 546same name
- redf0x1/camofox-browser★ 438same name
- RedWoodOG/Hermes-Desktop★ 177same name
- paiml/paiml-mcp-agent-toolkit★ 171same name
- paiml/aprender★ 137same name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/avoid-ai-writing/AGENTS.mdAGENTS.md
- .agents/skills/do-web-doc-resolver/AGENTS.mdAGENTS.md
- .agents/skills/skill-evaluator/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- accessibility-auditorSkill
- agent-browserSkill
- agentic-abstentionSkill
- agents-mdSkill
- api-design-firstSkill
- architecture-diagramSkill
- avoid-ai-writingSkill
- cicd-pipelineSkill
- cloudflare-worker-apiSkill
- codacySkill
- codeberg-apiSkill
- code-review-assistantSkill
- css-render-performanceSkill
- database-devopsSkill
- debuggerSkill
- delegateSkill
- dependency-upgradesSkill
- dist-channel-selectionSkill
- docs-hookSkill
- document-rendering-and-locatorsSkill
- dora-reportSkill
- do-web-doc-resolverSkill
- durable-objectsSkill
- eu-ai-act-complianceSkill
- git-github-workflowSkill
- goap-agentSkill
- implementerSkill
- intent-classifierSkill
- iterative-refinementSkill
- jules-delegatorSkill
- learnSkill
- lifecycle-managementSkill
- local-context-sanitizationSkill
- memory-contextSkill
- migration-refactoringSkill
- nested-build-isolationSkill
- privacy-firstSkill
- progressive-deliverySkill
- pwa-offline-syncSkill
- reader-ui-uxSkill
- readme-best-practicesSkill
- secrets-managementSkill
- secure-invite-and-accessSkill
- security-code-auditorSkill
- shell-script-qualitySkill
- skill-creatorSkill
- skill-evaluatorSkill
- static-analysisSkill
- testing-strategySkill
- test-runnerSkill
- triz-solverSkill
- turso-dbSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 13 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 81 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Only the Target URL is required.
- Distinctive: line 31
If the user says something like "dogfood vercel.com", start immediately with defaults.
- Very specific: line 33
Always use agent-browser directly -- never npx agent-browser.
- Distinctive: line 52
Start a named session:
- Distinctive: line 61
If the app requires login:
- Distinctive: line 74
After successful login, save state for potential reuse:
- Distinctive: line 94
Start from the main navigation.
- Distinctive: line 96
Check edge cases: empty states, error handling, boundary inputs.
- Distinctive: line 98
Check the browser console for errors periodically.
- Distinctive: line 109
Use your judgment on how deep to go.
- Distinctive: line 113
Every issue must be reproducible.
- Very specific: line 116
Start a repro video: agent-browser --session {SESSION} record start {OUTPUT_DIR}/videos/issue-{NNN}-repro.webm
- Distinctive: line 119
Stop video and write numbered repro steps in report
- Distinctive: line 134
Repro is everything: Every issue needs proof matched to its type.
- Distinctive: line 138
Never read the target app's source code: All findings must come from browser observation.
“Common” is measured: kept by at least 6 in 10 of the 81 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dogfood
Systematically explore a web application, find issues, and produce a report with full reproduction evidence for every finding.
When to Use
- User asks to dogfood, QA, or exploratory test a web application
- Need to find bugs, UX issues, or other problems in a web app
- Even if they just say "test this app" or "find issues in this site"
Setup
Only the Target URL is required. Everything else has sensible defaults -- use them unless the user explicitly provides an override.
| Parameter | Default | Example override |
| Target URL | (required) | vercel.com, http://localhost:3000 |
| Session name | Slugified domain (e.g., vercel.com -> vercel-com) | --session my-session |
| Output directory | ./dogfood-output/ | Output directory: /tmp/qa |
| Scope | Full app | Focus on the billing page |
| Authentication | None | Sign in to user@example.com |
If the user says something like "dogfood vercel.com", start immediately with defaults. Do not ask clarifying questions unless authentication is mentioned but credentials are missing.
Always use agent-browser directly -- never npx agent-browser. The direct binary uses the fast Rust client. npx routes through Node.js and is significantly slower.
Workflow
1. Initialize Set up session, output dirs, report file
2. Authenticate Sign in if needed, save state
3. Orient Navigate to starting point, take initial snapshot
4. Explore Systematically visit pages and test features
5. Document Screenshot + record each issue as found
6. Wrap up Update summary counts, close session1. Initialize
mkdir -p {OUTPUT_DIR}/screenshots {OUTPUT_DIR}/videosStart a named session:
agent-browser --session {SESSION} open {TARGET_URL}
agent-browser --session {SESSION} wait --load networkidle2. Authenticate
If the app requires login:
agent-browser --session {SESSION} snapshot -i
# Identify login form refs, fill credentials
agent-browser --session {SESSION} fill @e1 "{EMAIL}"
agent-browser --session {SESSION} fill @e2 "{PASSWORD}"
agent-browser --session {SESSION} click @e3
agent-browser --session {SESSION} wait --load networkidleFor OTP/email codes: ask the user, wait for their response, then enter the code.
After successful login, save state for potential reuse:
agent-browser --session {SESSION} state save {OUTPUT_DIR}/auth-state.json3. Orient
Take an initial annotated screenshot and snapshot to understand the app structure:
agent-browser --session {SESSION} screenshot --annotate {OUTPUT_DIR}/screenshots/initial.png
agent-browser --session {SESSION} snapshot -iIdentify the main navigation elements and map out the sections to visit.
4. Explore
Strategy -- work through the app systematically:
- Start from the main navigation. Visit each top-level section.
- Within each section, test interactive elements: click buttons, fill forms, open dropdowns/modals.
- Check edge cases: empty states, error handling, boundary inputs.
- Try realistic end-to-end workflows (create, edit, delete flows).
- Check the browser console for errors periodically.
At each page:
agent-browser --session {SESSION} snapshot -i
agent-browser --session {SESSION} screenshot --annotate {OUTPUT_DIR}/screenshots/{page-name}.png
agent-browser --session {SESSION} errors
agent-browser --session {SESSION} consoleUse your judgment on how deep to go. Spend more time on core features and less on peripheral pages.
5. Document Issues (Repro-First)
Every issue must be reproducible. When you find something wrong, stop exploring and document it immediately.
For interactive issues (functional, UX, console errors on action):
- Start a repro video:
agent-browser --session {SESSION} record start {OUTPUT_DIR}/videos/issue-{NNN}-repro.webm - Walk through steps at human pace with screenshots between actions
- Capture the broken state with annotated screenshot
- Stop video and write numbered repro steps in report
For static issues (typos, clipped text, visual glitches on load):
- Single annotated screenshot is sufficient. No video needed.
6. Wrap Up
Aim to find 5-10 well-documented issues, then wrap up. Depth of evidence matters more than total count.
- Re-read the report and update summary severity counts
- Close the session:
agent-browser --session {SESSION} close - Tell the user the report is ready with summary
Guidance
- Repro is everything. Every issue needs proof matched to its type.
- Verify before collecting evidence. Retry at least once to confirm reproducibility.
- Use the right snapshot:
snapshot -ifor interactive elements,snapshotfor reading content. - Never delete output files mid-session. Work forward, not backward.
- Never read the target app's source code. All findings must come from browser observation.
- Check the console. Many issues are invisible in the UI but show as JS errors.
See Also
test-runner— Execute tests and diagnose failurestesting-strategy— Choose testing approachesaccessibility-auditor— Accessibility-specific testing
Rationalizations
| Rationalization | Reality |
| "Manual testing is too slow compared to automated tests" | Automated tests verify logic; dogfooding catches usability and UX issues that scripts miss. |
| "I already know the app works, I built it" | Builders have the curse of knowledge; systematic exploration reveals what users actually encounter. |
| "A few screenshots are enough for a report" | Reproduction evidence must be complete and reproducible to be actionable. |
Red Flags
- Dogfood session skipped due to time pressure
- Issues reported without reproduction steps or evidence
- Only testing happy paths without edge cases or error states
References
references/issue-taxonomy.md- What to look for, severity levels, exploration checklisttemplates/dogfood-report-template.md- Copy into output directory as the report file
Voice & Context
- Default:
professional+blog - Reference:
voice-profilesskill for definitions and auto-detection.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

