Browse 14,200+ creator-published prompts. Add to your library in one click. Use them on any AI tool.
A comprehensive evaluation tool that forces the AI to act as a professional brand strategist, domain investor, and SEO expert
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. origin: ECC
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma). origin: ECC
Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo. origin: ECC
Automated visual QA, UI interaction testing, and accessibility/performance auditing of live web pages, driven through a browser-automation MCP (Playwright, Puppeteer, chrome-devtools-mcp, Claude in Chrome, Browserbase, browser-use, etc.). Use this skill whenever the user wants to QA, smoke-test, visually verify, regression-test, or sanity-check a deployed / preview / staging site or a local dev server — including after shipping a feature, before a release, when reviewing frontend PRs, or when checking forms, links, auth flows, responsive layouts, console/network errors, Core Web Vitals, or WCAG accessibility. Also use it for any browser-automation task that first needs a browser MCP to be present. Trigger even when the user does not say "QA" explicitly — e.g. "can you check my site works", "test the signup flow", "screenshot these pages at mobile + desktop", "is the layout broken on mobile", "why is this page slow".
Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. origin: ECC
Co-author a document through a structured 3-stage workflow (context gathering, refinement, reader testing). argument-hint: describe what to write — doc type, audience, goal — or leave blank to load the workflow first
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices"