design-org-structure

design-org-structure is a skill for Claude Code from Dragoon0x/everything-design-taste. It costs 25 tokens per session (626 once invoked), scanned A, original, MIT.

A guide to organizing design teams as they grow. It compares centralized, embedded, and hybrid reporting models, along with hiring and team-culture considerations.

In plain words
What is it for?
Use it to plan reporting lines, team structures, hiring approaches, design leadership, and operating practices.
Why use it?
It helps leaders choose how designers should work with product teams while maintaining mentorship, career growth, and design consistency.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the edt plugin — 117 skills, 80 agents shipped together

Good fit Use it to plan reporting lines, team structures, hiring approaches, design leadership, and operating practices.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dragoon0x/everything-design-taste/design-org-structure
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 Dragoon0x/everything-design-taste --skill design-org-structure
Clone the repo
git clone --depth 1 https://github.com/Dragoon0x/everything-design-taste

Made for: Claude Code.

Or install edt, the plugin that ships this one along with the rest of its 117 skills, 80 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.

agentmods badge for design-org-structure

README.md
[![agentmods](https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/design-org-structure/github.svg)](https://agentmods.dev/skills/dragoon0x/everything-design-taste/design-org-structure)
Your own site
<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/design-org-structure"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/design-org-structure/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-org-structure

Your own site · 80×15
<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/design-org-structure"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/design-org-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 626 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.00025 $0.00626
Opus 5 $0.00013 $0.00313
Sonnet 5 $0.00005 $0.00125
Haiku 4.5 $0.00003 $0.00063

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

Security

Grade A, and why

design-org-structure 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 6d 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.

skills/design-org-structure/SKILL.md · 69 lines

How it starts

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

Design Org Structure

Team Models

Centralized

All designers report to a design lead. They're assigned to product teams but their career and craft development lives in the design org.

Pros: Consistent quality, strong design culture, clear career paths Cons: Potential disconnect from product teams, resource allocation friction Best for: Companies where design consistency matters more than speed

Embedded

Each designer reports directly to a product team lead. No central design org.

Pros: Fast, tight product alignment, designers have full context Cons: Quality drift, isolation, no design mentorship, career path unclear Best for: Early-stage startups where speed is everything

Hybrid (most common at scale)

Designers are embedded in product teams but have a dotted line to a central design leader. Regular design org rituals (critique, design system work) keep quality aligned.

Pros: Speed of embedded + quality of centralized Cons: Complex management, potential conflicting priorities Best for: Growth-stage companies (50-500 employees)

Designer-to-Engineer Ratio

Benchmarks

  • Early startup: 1 designer per 8-10 engineers
  • Growth stage: 1 designer per 5-7 engineers
  • Mature product: 1 designer per 3-5 engineers
  • Design-led products: 1 designer per 2-3 engineers

When to Hire

  • Designers are consistently the bottleneck
  • Quality is dropping because designers are spread too thin
  • You're entering a new market/product area
  • Design debt is accumulating faster than you can address it

Roles and Levels

IC Track

  1. Junior Designer — Executes defined tasks, learning the craft
  2. Designer — Owns features end-to-end, works independently
  3. Senior Designer — Drives strategy for product areas, mentors juniors
  4. Staff Designer — Cross-product impact, defines systems and standards
  5. Principal Designer — Company-wide influence, sets design direction

Management Track

  1. Design Lead — Player-coach, manages 3-5 designers
  2. Design Manager — Full-time people management, 5-8 reports
  3. Director of Design — Org strategy, cross-functional leadership
  4. VP of Design — Executive team, company strategy, org building
  5. CDO/Head of Design — Board-level, brand and product vision

Read the full file on GitHub · 69 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. 6d ago First seen · 69 lines · 25 tokens per session scan A ed95274fbcf6

Subscribe to this mod's changes

design-org-structure is a skill published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 626 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-09-03.

Related

Other skills, from other repositories

huashu-keynote-black

OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.

nexu-io/open-design · 43 tokens

accessibility

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

addyosmani/web-quality-skills · 51 tokens

acid-blue-business

A visual presentation style for modern business topics, using electric blue with black, white, and grey, directional layouts, and clear spacing. It is intended for business content rather than traditional data dashboards.

arcsin1/oh-my-ppt · 0 tokens

auteur

Design and build complete web experiences from scratch — award-level product and marketing pages, cinematic scroll-directed sites where the page is directed like a film, and multi-screen products (app, dashboard, admin, settings, onboarding, docs site) built as one design system with every component, state and route…

agiwhitelist/auteur · 191 tokens

component-family-consistency

Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library…

dembrandt/dembrandt-skills · 76 tokens

stitch

Clean, high-contrast enterprise design for data-driven workflows with intuitive drag-and-drop patterns and structured layouts.

bergside/awesome-design-skills · 24 tokens