Org Design Principles logo

Org Design Principles

Community
Owl-Listener
org-design-principles

Define org-level design principles that guide decisions.

Overview

PublisherOwl-Listener
Repositorydesign-leadership-skills
Skill nameorg-design-principles
Stars
16
Forks
1
Bundled files
Instructions only
LicenseMIT
Links
  • 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 Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Org Design Principles 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/Owl-Listener/design-leadership-skills/tree/main/design-strategy/skills/org-design-principles
  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/Owl-Listener/design-leadership-skills.git /tmp/design-leadership-skills
mkdir -p .claude/skills
cp -r /tmp/design-leadership-skills/design-strategy/skills/org-design-principles .claude/skills/org-design-principles
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Org Design Principles 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 Org Design Principles 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 Org Design Principles 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.

Org Design Principles

You are an expert at principles that actually arbitrate decisions, not platitudes.

What You Do

You define a small set of principles teams use to make consistent calls without escalating.

A Good Principle

  • Takes a side — implies trade-offs ("clarity over density")
  • Is actionable — you can apply it to a real decision
  • Is memorable — short, distinct, not interchangeable with any team's
  • Is yours — reflects this org's specific bets

Method

  1. Derive from real decisions where you wished for a guide
  2. Phrase as "X over Y" to force a trade-off
  3. Keep it to a handful — more than seven and none stick
  4. Test against past hard calls: would it have helped?

Anti-Patterns

  • "Be user-centred" (everyone says it, it decides nothing)
  • Principles with no opposing cost (then they're not principles)

Best Practices

  • Principles earn their keep when they settle an argument
  • Pair each with an example of it in action
  • Retire ones that never get used

Frequently asked questions

What does the Org Design Principles AI skill do?

Define org-level design principles that guide decisions.

Why use Org Design Principles on TypingMind?

Because you install it once and use it with any model. Org Design Principles 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 Org Design Principles in TypingMind?

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

Which AI models can use Org Design Principles?

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 Org Design Principles?

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

Is the Org Design Principles AI skill free?

Yes. It is published on GitHub by Owl-Listener 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.

View all

Set up your own AI workspace now

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