A design-workflow skill that proposes two or three different software architecture approaches during the design phase.

Reading the current workflow state, checking prerequisites, and coordinating several architecture proposals with different focuses such as minimal changes or clean architecture.

It gives the team structured alternatives to compare before choosing how a feature should be built.

dev:design — Skill for Claude Code by atournayre

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 atournayre/claude-marketplace --skill design

Clone the repo

git clone --depth 1 https://github.com/atournayre/claude-marketplace

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 25 skills, 8 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/atournayre/claude-marketplace/design/github.svg)](https://agentmods.dev/skills/atournayre/claude-marketplace/design)

Your own site

<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/design"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/design/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/design"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 467 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.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.00467
Opus 5	$0.00010	$0.00234
Sonnet 5	$0.00004	$0.00093
Haiku 4.5	$0.00002	$0.00047

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

Security

Grade A, and why

dev:design 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 12d 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.

dev/skills/design/SKILL.md · 75 lines

What it actually says

Configuration de sortie

Instructions à Exécuter

IMPORTANT : Exécute ce workflow étape par étape :

IMPORTANT : Cette skill génère une comparaison d'architectures et nécessite un format de sortie spécifique.

Lis le frontmatter de cette skill. Si un champ output-style est présent, exécute immédiatement :

/output-style <valeur-du-champ>

Note : Une fois que le champ output-style sera supporté nativement par Claude Code, cette instruction pourra être supprimée.

Output-style requis : table-based

Objectif

Phase 3 du workflow de développement : proposer plusieurs approches architecturales et aider l'utilisateur à choisir.

Prérequis

⚠️ Plugin feature-dev requis pour les agents code-architect.

Si non installé :

/plugin install feature-dev@claude-code-plugins

Instructions

1. Lire le contexte

Lire .claude/data/.dev-workflow-state.json pour la feature, les findings et les décisions
Si phases précédentes non complétées, rediriger vers la phase manquante

2. Lancer les agents code-architect

Lancer 2-3 agents code-architect en parallèle avec des focus différents :

Agent 1 : Minimal changes

Agent 2 : Clean architecture

Agent 3 : Pragmatic balance

3. Consolider et comparer

Présenter les approches de manière structurée

4. Demander le choix de l'utilisateur

⚠️ CRITIQUE : Attendre le choix avant de passer à la phase suivante.

5. Documenter l'architecture choisie

Mettre à jour le workflow state

Prochaine étape

✅ Architecture choisie

Prochaine étape : /dev:plan pour générer le plan d'implémentation

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.

12d ago First seen · 75 lines · 19 tokens per session scan A 0b3f6cfcbdc5

Subscribe to this mod's changes

dev:design is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 467 once invoked, about $0.0001 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.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens