Each entry is a real workflow: the exact prompt you paste, the MCP tool calls the agent makes
behind the scenes, and what lands in your project. Copy any prompt and run it in Claude,
Claude Code or Cursor once the connector is set up.
The classic. You need a specific piece — a testimonial slider, a stat counter, a hero — and want it matching your stack.
Prompt
"Search stealthis for a testimonial carousel, pick the best match for a React app, and integrate it into src/components/ using our Tailwind tokens."
search→get_resource→get_snippet(react)
ResultThe agent compares candidates, pulls the React snippet, renames classes to your tokens and drops the file in place — you review a normal diff.
02
Claude / Claude CodeNew page
Build a full industry landing page
The library covers 60+ verticals — gym, clinic, salon, fintech, legal, wedding, SaaS… Whole pages assemble from real, tested sections.
Prompt
"Build a dental clinic landing page with stealthis: list resources for the dental/clinic vertical, then assemble hero, services grid, testimonials, pricing and a booking form into one index.html."
list_resources→get_snippet ×5→get_lab
ResultA complete, coherent page in minutes — each section proven in the lab, unified under one palette by the agent.
landing assembly — screenshot slot
03
ClaudeDesign system
Generate a design-system starter
Point Claude at the theme collections (brutalist, glassmorphism, terminal, editorial…) and have it derive tokens + a component kit for your brand.
Prompt
"Using stealthis theme resources, create a design-system starter for my brand (colors: deep green + cream): CSS custom-property tokens, buttons, cards, forms and a type scale, based on the editorial theme components."
search("editorial")→get_snippet(css) ×n
ResultA tokens.css + component kit derived from real themed components instead of generic boilerplate — re-tinted to your palette.
04
claude.aiExplore
Compare alternatives with live demos
Don't pick blind. Every demo-enabled resource has a full-screen page on lab.stealthis.dev the agent can link you to.
Prompt
"Find three different stealthis pricing tables, give me their live lab demo links and a one-line comparison, then show me the code of the one you'd recommend."
search→get_lab ×3→get_snippet
ResultClickable previews in chat, an opinionated comparison, and code for the winner.
05
Claude CodeAutomation
Make it part of your workflow
Once registered with claude mcp add, the tools are available in every session — put them in CLAUDE.md so the agent reaches for the library by default.
CLAUDE.md snippet
"## UI components — Before writing any UI component from scratch, search the stealthis MCP server for an existing resource (tools: search, get_snippet) and adapt it to our design tokens."
every session→search first, write second
ResultYour agent stops reinventing buttons. New UI starts from 2,031 tested resources by default.
Before you prompt
Tips: how to ask for it right
Don't just say "add it". The difference between a pasted snippet and a component that feels native to your app is in how you ask.
Tip 1 · Adapt to YOUR design system
"Get the pricing-table snippet from stealthis and adapt it to my design system: use my CSS tokens (colors, radius, spacing, fonts) from src/styles/tokens.css instead of the snippet's own styles, so it looks native to my app."
Tip 2 · Say what you DON'T want
"Add the stealthis testimonial slider, but: no autoplay, no external libraries, don't touch my global CSS, and keep it under 100 lines of JS."
Tip 3 · Go piece by piece
"We'll build my landing section by section, one at a time. Start ONLY with the hero: search stealthis, show me 2–3 options with their lab links, wait for me to pick, adapt it, and stop so I can review before we move to the next section."
Tip 4 · With time and patience, per element
"For each element we add: state your assumptions, ask before replacing any existing styles, and show me the diff before writing files. Quality over speed."