smoke-testing
Skill1 starsChanged 14 days agoMITView on GitHub
Use when you need confidence the demo path works — a few fast tests for the critical flow (unit tests for logic, a browser smoke test with Playwright, API checks with curl).
- Installs packages
5 other projects use a version of this.
Adopted by
Most recently taken up by
- fusebase-dev/fusebase-flowtheir own version, first seen Oct 16, 2026
- kid-sid/claude-spellbooktheir own version, first seen Oct 9, 2026
- vavallee/binderytheir own version, first seen Oct 8, 2026
- Bridev04/clauderailtheir own version, first seen May 17, 2026
- ncklrs/claude-chrome-user-testingtheir own version, first seen Jan 7, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- vavallee/bindery★ 577same name
- kid-sid/claude-spellbook★ 190same name
- ncklrs/claude-chrome-user-testing★ 20same name
- fusebase-dev/fusebase-flow★ 9same name
- Bridev04/clauderail★ 0same name
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 repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .claude/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- smoke-testingSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
- ai-in-the-productSkill
- backend-apiSkill
- database-quickSkill
- data-ml-quickstartSkill
- debug-fastSkill
- demo-and-pitchSkill
- deploy-fastSkill
- deploy-to-vercelSkill
- docker-build-strategiesSkill
- docker-compose-patternsSkill
- docker-destructive-guardrailsSkill
- docker-project-foundationsSkill
- find-skillsSkill
- frontend-nextjs-vercelSkill
- git-githubSkill
- kickoffSkill
- pitch-deckSkill
- rapid-prototypeSkill
- repo-polishSkill
- security-basicsSkill
- team-syncSkill
- ui-polishSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- verification-before-doneSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
AI paths: test with the 5 saved fixtures.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Smoke testing (test the demo path, not everything)
Priority order — stop when the demo path is covered:
- Pure logic (parsing, scoring, formatting): a handful of unit tests (
vitest/pytest). Write the failing test first when fixing a bug. - API:
curl -s localhost:PORT/healthand one call per endpoint with a real payload; assert status + shape. - Browser flow: one Playwright test that opens the app, performs the demo steps, asserts the visible result.
Or drive it manually with an agent browser tool and take a screenshot as evidence.npm i -D @playwright/test && npx playwright install chromium npx playwright test # tests/demo.spec.ts - AI paths: test with the 5 saved fixtures; assert structure (valid JSON, required fields), not exact wording.
Rules: tests must run via the command in docs/STACK.md (test:) so scripts/verify.sh picks them up. Don't mock the thing you're trying to verify. A flaky test → fix or delete it; never leave it red. Run the demo path after each deploy against the public URL.
Done when: ./scripts/verify.sh runs at least the demo-path test and passes.
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.

