design-system

design-system is a skill for Claude Code from arianlopezc/Trabuco. It costs 44 tokens per session (770 once invoked), scanned A, original, MIT.

A design workflow for splitting a system into separate Trabuco services. It turns requirements for platforms or multiple cooperating services into independently configured services and their communication patterns.

In plain words
What is it for?
Use it to plan marketplaces, platforms, microservices, and event-driven systems where services own different data and communicate through REST or events.
Why use it?
It helps define service boundaries when a system has several deployable parts, instead of treating the whole platform as one application.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Part of the trabuco plugin — 10 skills, 24 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it to plan marketplaces, platforms, microservices, and event-driven systems where services own different data and communicate through REST or events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arianlopezc/trabuco/design-system
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add arianlopezc/Trabuco --skill design-system
Clone the repo
git clone --depth 1 https://github.com/arianlopezc/Trabuco

Made for: Claude Code.

Or install trabuco, the plugin that ships this one along with the rest of its 10 skills, 24 agents, 2 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/arianlopezc/trabuco/design-system/github.svg)](https://agentmods.dev/skills/arianlopezc/trabuco/design-system)
Your own site
<a href="https://agentmods.dev/skills/arianlopezc/trabuco/design-system"><img src="https://agentmods.dev/badge/skills/arianlopezc/trabuco/design-system/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-system

Your own site · 80×15
<a href="https://agentmods.dev/skills/arianlopezc/trabuco/design-system"><img src="https://agentmods.dev/badge/skills/arianlopezc/trabuco/design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 770 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00770
Opus 5 $0.00022 $0.00385
Sonnet 5 $0.00009 $0.00154
Haiku 4.5 $0.00004 $0.00077

Measured 8d ago against content hash 0dd2f171bb4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

design-system scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/skills/design-system/SKILL.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design a multi-service Trabuco system

Turn high-level system requirements into a workspace of independent Trabuco services, each with its own module selection.

When to pick this skill over /trabuco:new-project

  • User says "system", "platform", "marketplace", "multiple services", "event-driven architecture across teams", "CQRS with separate read/write services", or similar.
  • The workload naturally splits — different services own different entities, communicate via events, can be deployed independently.

If only ONE service will own the domain, use /trabuco:new-project instead.

Flow

  1. Delegate to the specialist: for the decomposition itself, invoke the trabuco-architect subagent if it's available — it loads the design_microservices MCP prompt which encodes Trabuco's boundaries doctrine.

  2. If running skill directly: call mcp__trabuco__design_system with the user's requirements. It returns a proposed decomposition (services, their modules, inter-service communication patterns).

  3. Review with the user: present each service with:

    • Its purpose (one sentence)
    • Its module selection (from Trabuco's catalog)
    • How it communicates with siblings (REST? Events? A2A?)
    • What it owns (entities, events)

    Surface decomposition tensions honestly: if two services would share entities heavily, flag it and ask the user whether to merge them.

  4. Iterate if needed: user may want to split a service further or merge two. Re-call design_system with adjusted requirements, or manually adjust the proposed config.

  5. Generate the workspace: once locked, call mcp__trabuco__generate_workspace with the approved design. This creates a workspace root + per-service directories, each a full Trabuco project.

  6. Next steps: tell the user how to build the workspace (typically mvn clean install at the workspace root, or per-service), and how the A2A agent cards discover each other if AIAgent modules are involved. Auth across services: every service whose module list includes API or AIAgent gets dormant OIDC Resource Server scaffolding. For consistent cross-service identity, point all services at the same OIDC_ISSUER_URI (one IdP, multiple resource servers) and flip trabuco.auth.enabled=true when ready. The same IdentityClaims shape lives in each service's Model module so token claims propagate cleanly via headers / event payloads. Full guide: docs/auth.md.

Read the full file on GitHub · 45 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 45 lines · 44 tokens per session scan A 0dd2f171bb4b

Subscribe to this mod's changes

design-system is a skill published in the GitHub repository arianlopezc/Trabuco (0 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 770 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

migrate-segw-to-rap

Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…

arc-mcp/arc-1 · 106 tokens

telnyx-messaging-hosted-curl

Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.

team-telnyx/ai · 45 tokens