webapp-testing
Tests local web apps with Playwright scripts: checks frontend behaviour, captures screenshots and reads browser logs.
Skills, agents, prompts, rules, plugins and MCP servers from Anthropic, OpenAI, Microsoft, GitHub, Cursor and the community. An AI assistant has read them all: ask one question and it picks the best match, with sources.
8,522 components1,469 reviewed28 sources10 kinds
Ask in plain words. The assistant does the reading you would otherwise do across a dozen tabs.
Preview, coming soon: an illustration of the repo assistant, which is not available yet. A repository link is pasted, the assistant reads 214 files, ranks three skills, and adds the best match, test-driven-development, to the repository's .claude/skills folder.
Say what you want your agent to do, in your own words.
The assistant has read every skill, agent and rule in the catalog, so you do not have to.
Matches come ranked, best first, each with the source it came from.
Drop the pick into your own Claude Code setup in Build, and keep every revision.
Every component has a reviewed summary, its kind and where it came from. The assistant weighs them against your question and shows you why one fits best.
Example question: Let my agent test its web app in a real browser
Tests local web apps with Playwright scripts: checks frontend behaviour, captures screenshots and reads browser logs.
MCP config that starts the Playwright server with npx, so Claude can drive a browser.
Playwright end-to-end UI tests in TypeScript for web applications.
Each lesson shows the real thing beside the explanation: the command you would type, the file it changes and what Claude Code does with it.
/hooks opens the Hooks lesson: Run a script every time Claude Code edits a file, before it runs a command, or when it finishes.
The /hooks command lifts out of a terminal and becomes the lesson title. The lesson card then folds into the Hooks tab, and the lessons on hooks are listed below it.
How Claude Code works, in short lessons: context, skills, subagents and hooks. Lessons 1 to 3 are free, no account.
Start lesson 1Search the whole catalog, or just ask. Every answer says where it came from.
Open the catalogDesign your own Claude Code setup with the assistant. Keep every revision and download it as Markdown or a ZIP.
Start a setupPoint it at a repository and it writes back a design and a Claude Code setup made for that code.
It is free and needs no account. A free account then opens the whole catalog, the assistant and your own setups.