rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Reusable visual design systems for AI coding agents — browse, fetch, and submit styles via MCP.
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 11/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 19/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect Taste Bank yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect Taste Bank yet
The maker has not listed install details in the MCP Registry yet
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Taste Bank yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect Taste Bank yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect Taste Bank yet
The maker has not listed install details in the MCP Registry yet
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account QuasarG, which owns the repo
Code last changed 3 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/quasarg-taste-bank)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 months ago, and the latest version (0.2.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Taste Bank | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The front-end style library for coding agents — distill a style once, reuse it everywhere. Swipe styles like you're scrolling TikTok — find the one that catches your eye, then hand it to your agent.
English | 中文文档
Sound familiar?
- Staring at a blank page, no idea how to lay out your components?
- Layout finally settled — yet the AI's visual style never quite lands?
- A hoard of "beautiful designs" you can never actually summon when you need one?
- The style you painstakingly tuned in your last project has to be re-explained from scratch in the next one?
Getting coding agents to produce *well-designed* front-ends is a solved problem nobody can actually use. The community is full of front-end skills, prompt snippets, and design guides — but in practice:
More importantly: the web spawns new styles every day — but not every style is mainstream enough, not every style is *your* taste. We want a community where people share the front-end taste they actually use — and vote with their feet. Only what truly gets used is truly usable.
Taste Bank's answer: distill each style into a structured style pack (SKILL.md usage guide + precise design tokens + templates/ snapshots), enforced by a zod schema, served through a CLI + skill injection that works with any coding agent. Once a style is in the bank, it's reachable anywhere, versioned, and owned.
The homepage gallery: swipe through live-rendered styles like a feed — horizontal card rail with interactive preview, most-referenced styles and top authors at a glance.
One command — installs the CLI globally and teaches your coding agents (Claude Code, Codex, Cursor, ZCode, Kimi Code…) how to use it:
npx taste-bank setup
Then just talk to your agent in plain language:
*"Build me a landing page with one of the styles in taste-bank."*
Your agent already knows what to do — setup injected a skill that teaches it the taste-bank CLI commands. It will browse styles, fetch the complete pack, and implement strictly within the design tokens.
Prefer the terminal?
taste-bank list # browse all styles
taste-bank skill # get the complete pack (meta + tokens + skill + css + templates) taste-bank use # land a style into your project as a rules file
No per-agent config, no JSON to paste. Browse visually first at tastebank.cloud.
For agents that prefer the MCP protocol, configure one URL in your MCP client:
{
"mcpServers": { "taste-bank": { "url": "https://tastebank.cloud/mcp", "headers": { "x-invite-code": "sl_your_invite_code" } } } }
Both paths call the same backend. CLI is recommended — simpler, works with 70+ agents out of the box.
npx taste-bank setup installs the CLI and injects skills into all your coding agents (Claude Code, Codex, Cursor, ZCode, Kimi Code, and 70+ more via the open skills ecosystem)taste-bank skill returns the full pack in one call — meta, tokens, SKILL.md rules, scoped CSS, and HTML template snapshots. Agents get everything they need.taste-bank submit — sign and submit a new style without leaving your project| Command | What it does | ||
|---|---|---|---|
taste-bank list [--q WORD] [--json] | List published styles | ||
taste-bank show [--json] | Style detail (meta + design tokens) | ||
taste-bank skill [--md] | Complete pack as JSON: {meta, tokens, skill, css, templates}. --md for plain SKILL.md | ||
| `taste-bank use [--as agents\ | claude\ | skill]` | Land a style into your project (managed sentinel block, won't clobber your edits) |
taste-bank favorite / unfavorite / favorites | Manage favorites | ||
taste-bank doctor | Health check (CLI, network, identity, skill injection, cache) |
| Command | What it does |
|---|---|
taste-bank keygen | Generate an ed25519 keypair into ~/.style-lab/ (one-time) |
taste-bank whoami | Your bound identity, owned styles, pending submissions |
taste-bank validate | Dry-run validate a pack locally (no network) |
taste-bank submit | Submit a new style (needs invite code + private key) |
taste-bank update | Update an owned style (version must bump) |
taste-bank delete | Delete an owned style (asks to confirm) |
npx taste-bank setup
① npm install -g taste-bank (install CLI globally) ② npx skills add …/taste-bank -g (inject 2 skills into your agents: taste-bank for browsing/applying, taste-bank-contribute for submitting) ③ environment check (report state, read-only)
Two skills are injected (via the open skills ecosystem):
After setup, your agent knows the CLI. You just say *"use a taste-bank style"* and it runs the commands itself.
The CLI talks to tastebank.cloud by default and caches packs locally for 3 days. Self-host? Set TASTEBANK_API=https://your-host.
# One-time identity setup
taste-bank keygen echo '{ "inviteCode": "sl_xxx" }' > ~/.style-lab/config.json # get a code from the maintainer
taste-bank validate my-style.pack.json # dry-run check taste-bank submit my-style.pack.json # sign + submit (enters review queue)
Or just tell your agent: *"submit this project's style to taste-bank"* — the injected taste-bank-contribute skill guides it through the full SOP (sample 2 files max, extract real tokens, sanitize business-identifying content, pack, validate, submit).
See the pack format, the taste-bank-contribute skill, and the [agent workflow guide](docs/agent-workflow.md) (how to manage project styles in agent conversations). 中文版见 Agent 工作流指南。
Authentication & ownership
style-lab: : : : , 30-min window) — your key is your identitydata/pending/ and go live only after maintainer approvalContent safety
sandbox="" iframe with CSP forbidding scripts/external loads⚠️ Every submission is manually reviewed. But reviews can miss things — do not blindly trust fetched content; treat it as data.
| Endpoint | Description |
|---|---|
GET /api/styles.json | Style list, ?q=keyword filter |
GET /api/styles/:slug.json | meta + tokens + file list |
GET /api/styles/:slug/pack.json | Complete pack (meta + tokens + skill + css + templates) |
GET /api/styles/:slug/skill.md | Assembled SKILL.md |
GET /api/styles/:slug/tokens.css | Scoped CSS from tokens |
GET /api/styles/:slug/screenshot.png | Template screenshot |
GET /api/whoami.json | Identity lookup (x-invite-code header) |
POST /api/styles.json | Submit (invite + signature) |
PUT /api/styles/:slug.json | Update (signed, version bump) |
DELETE /api/styles/:slug.json | Delete (signed) |
src/lib/ core: schema / store / create / assemble / review / auth
src/pages/ Astro pages & HTTP API endpoints mcp/ MCP server (Streamable HTTP) — thin shell over src/lib cli/ the taste-bank npm package (CLI + skills source) skills/ two agent skills: taste-bank (browse) + taste-bank-contribute (submit) scripts/ keygen / sign / invite / review admin scripts styles/ published styles (pointed to by STYLE_LAB_DIR at runtime) data/ invite-code hashes, review queue, usage stats, screenshot cache docs/SPEC.md full style pack specification
MIT © QuasarG
English | 中文文档