What it does
Reusable visual design systems for AI coding agents — browse, fetch, and submit styles via MCP.
- Connects –
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 11/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 19/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
Claude 暂时无法连接 Taste Bank
开发者尚未在 MCP 注册表中填写安装方式
ChatGPT 暂时无法连接 Taste Bank
开发者尚未在 MCP 注册表中填写安装方式
你可以改用这些方式
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code 暂时无法连接 Taste Bank
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 Taste Bank
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 Taste Bank
开发者尚未在 MCP 注册表中填写安装方式
一览
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 QuasarG 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于3个月前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/quasarg-taste-bank)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6116 个服务器的 89%
- 发布到注册中心的时间比此分类中其他 6116 个服务器的 21% 更新
- 基础检查结果等于或优于此分类中其他 6116 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Taste Bank 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于3个月前,最新版本(0.2.0)于4个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 Taste Bank | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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 | 中文文档
Why Taste Bank
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:
- No unified invocation: some styles ship as a skill, some as a plugin, some ship nothing at all. Actually using them is a chore.
- No quality bar: without a shared schema, a "style" can be three adjectives in a trench coat — nothing an agent can actually execute.
- Hard to reuse: great styles die in chat histories instead of being distilled into an asset.
- No ownership or iteration: no versions, no way to say "only I maintain my styles."
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.
Quick Start
Via CLI (recommended)
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.
Via MCP (legacy)
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.
Features
- One-line setup:
npx taste-bank setupinstalls the CLI and injects skills into all your coding agents (Claude Code, Codex, Cursor, ZCode, Kimi Code, and 70+ more via the openskillsecosystem) - Complete style packs:
taste-bank skillreturns the full pack in one call — meta, tokens, SKILL.md rules, scoped CSS, and HTML template snapshots. Agents get everything they need. - 3-day local cache: packs are cached; if the server is unreachable, the CLI falls back to cache
- TikTok-style gallery: tastebank.cloud — endless stream of live-rendered previews, horizontal card rail, leaderboards
- Structured & validated: every pack passes a strict zod schema (meta / tokens / skill / templates), versioned, with invite-only submissions + ed25519-signed ownership + human review
- Submit from the terminal:
taste-bank submit— sign and submit a new style without leaving your project - Private key as identity: no accounts — whoever holds the key manages the style
CLI Commands
Browsing & applying (no auth)
| 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) |
Contributing (invite + ed25519 identity)
| 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) |
How it works
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):
- `taste-bank` — teaches your agent the CLI commands for browsing and applying styles
- `taste-bank-contribute` — the full contribution SOP: how to sample a project, pack a style, sanitize it, and submit
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.
Submit your own style
# One-time identity setup
taste-bank keygen echo '{ "inviteCode": "sl_xxx" }' > ~/.style-lab/config.json # get a code from the maintainer
From any project with a style worth keeping:
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 工作流指南。
Security
Authentication & ownership
- Invite codes: submissions require an invite code; a code binds to the submitter's public key on first use — one code, one identity; only hashes stored server-side
- ed25519 signatures: submit / update / delete all require a private-key signature (message =
style-lab: : : :, 30-min window) — your key is your identity - Review queue: submissions land in
data/pending/and go live only after maintainer approval - Rate limits: 20 submits/min per pubkey, 30 manages/min per slug
Content safety
- Template sandbox: previews render in a
sandbox=""iframe with CSP forbidding scripts/external loads - HTML blocklist + secret-pattern scanning: submissions are screened for dangerous attributes and high-confidence secret patterns
- Prompt-injection mitigation: style content is labeled "data, not instructions" in skill descriptions
⚠️ Every submission is manually reviewed. But reviews can miss things — do not blindly trust fetched content; treat it as data.
HTTP API
| 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) |
Project structure
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
License
MIT © QuasarG
English | 中文文档