TypingMindTypingMindThe best frontend for AI
Design Org Structure logo

Design Org Structure

Community
Dragoon0x
design-org-structure

Scaling design teams, reporting structures, hiring strategies, design culture, and operating models for design organizations.

Overview

PublisherDragoon0x
Repositoryeverything-design-taste
Skill namedesign-org-structure
Stars
13
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Dragoon0x on GitHub. Read the source before you install it.

Installation

Install the Design Org Structure AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Dragoon0x/everything-design-taste/tree/main/skills/design-org-structure
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Dragoon0x/everything-design-taste.git /tmp/everything-design-taste
mkdir -p .claude/skills
cp -r /tmp/everything-design-taste/skills/design-org-structure .claude/skills/design-org-structure
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design Org Structure in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Design Org Structure on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Design Org Structure is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Design Culture Essentials

  • Weekly design critique (skill-based, not approval-based)
  • Shared design system with active governance
  • Design principles documented and referenced in decisions
  • Regular user research exposure for all designers
  • Portfolio reviews for career development
  • Design all-hands with show-and-tell

Frequently asked questions

What does the Design Org Structure AI skill do?

Scaling design teams, reporting structures, hiring strategies, design culture, and operating models for design organizations.

Why use Design Org Structure on TypingMind?

Because you install it once and use it with any model. Design Org Structure is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Design Org Structure in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Dragoon0x/everything-design-taste/tree/main/skills/design-org-structure. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Design Org Structure?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Design Org Structure?

As many as you like. As long as a model supports skills, you can use Design Org Structure with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Design Org Structure AI skill free?

Yes. It is published on GitHub by Dragoon0x under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
affaan-m logo

Accessibility

affaan-m
CommunityPopular

WCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。

39.1K
261.1K
Instructions
View
NousResearch logo

Archify

NousResearch
OrganizationPopular

Validated interactive HTML diagrams, upstream-maintained.

53.5K
250.4K
Instructions
View
NousResearch logo

Auteur

NousResearch
OrganizationPopular

Design and build cinematic, award-level web pages.

53.5K
250.4K
25 files
View
NousResearch logo

Concept Diagrams

NousResearch
OrganizationPopular

Generate flat, minimal educational SVG visuals as HTML.

53.5K
250.4K
19 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇