Wabi Sabi Imperfection logo

Wabi Sabi Imperfection

Community
Deibler
wabi-sabi-imperfection

Design intentional imperfection that reads as warmth — subtle asymmetry, hand-drawn elements, organic textures, intentional irregularities. Use when adding human warmth to a digital design, distinguishing from competitors with uniform design systems, designing for personal or creative contexts. The skill is making imperfection look intentional and refined rather than sloppy or broken; the line between "designed warmth" and "looks unfinished" is narrow.

Overview

PublisherDeibler
Repositoryuniversal-design-principles
Skill namewabi-sabi-imperfection
Stars
9
Forks
3
Bundled files
1
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Wabi Sabi Imperfection 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/Deibler/universal-design-principles/tree/main/plugins/aesthetics-and-emotion-principles/skills/wabi-sabi-imperfection
  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/Deibler/universal-design-principles.git /tmp/universal-design-principles
mkdir -p .claude/skills
cp -r /tmp/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/wabi-sabi-imperfection .claude/skills/wabi-sabi-imperfection
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wabi Sabi Imperfection 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 Wabi Sabi Imperfection 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 Wabi Sabi Imperfection 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.

Wabi-Sabi — imperfection

Designing intentional imperfection is the half of wabi-sabi that adds warmth through irregularity, asymmetry, and visible craft. Done well, the imperfection reads as deliberate and refined — the work of someone who cared enough to break the grid in a chosen way. Done poorly, it reads as broken or unfinished.

The challenge is calibration. Too little imperfection and the design reverts to standard digital uniformity; too much and it feels chaotic. The most successful applications use small, deliberate imperfections in otherwise-disciplined designs, so the imperfection reads as character rather than as failure.

What "intentional imperfection" looks like

Subtle asymmetry. A layout that's mostly grid-aligned but lets one element sit slightly off. A button with off-center text. A logo positioned slightly above center. The asymmetry is small enough to feel intentional, large enough to be noticed.

Hand-drawn elements. Illustrations or icons that show the artist's hand — visible brushstrokes, varied line weights, irregularities in the form. These contrast with vector-precise elements and add visual texture.

Organic textures. Backgrounds that suggest paper, watercolor, fabric, or other natural materials — rather than flat colors or smooth gradients. The texture reads as material rather than as digital surface.

Variable typography. A typeface that has subtle character variations (humanist serifs are often like this), or hand-set text with intentional kerning irregularities. Contrasts with mathematically-uniform display type.

Variable spacing and rhythm. Layouts where vertical spacing isn't perfectly uniform — some sections breathe more than others, creating a more editorial feel.

Imperfect alignment used deliberately. A pull-quote that breaks the column. A photo that bleeds past its frame. A subhead that hangs into the margin.

Visible craft cues. Marks that suggest process — a sketch underneath a finished illustration, a draft note in the margin, an "in progress" feel in non-final surfaces.

Calibrating imperfection

The right level of imperfection depends on context:

More imperfection welcomed:

  • Personal / creative products (journals, art tools, meditation).
  • Editorial content (magazines, long-form blogs).
  • Brand-identity moments (marketing surfaces, hero illustrations).
  • Hand-craft or artisanal product categories.
  • Newer products experimenting with distinctive aesthetics.

Less imperfection welcomed:

  • Functional UI (buttons, forms, navigation).
  • Data displays.
  • Critical-action interfaces.
  • Enterprise / professional contexts.
  • Accessibility-critical surfaces.

A single product can use different levels of imperfection in different surfaces. The hero illustration on the marketing site can be hand-drawn; the in-app dashboard can be precise. Each register serves its context.

What's the difference between designed imperfection and sloppy?

The difference often comes down to:

Intent. Designed imperfection is chosen; sloppy is accidental. The designer can articulate why each imperfection is there.

Refinement. Designed imperfection is well-crafted within its irregularity. The hand-drawn line is well-drawn even though it's hand-drawn. Sloppy is not crafted at all.

Restraint. Designed imperfection is selectively applied. Some elements are perfect; others are imperfect. Sloppy is uniform low quality.

Coherence. Designed imperfection has a consistent register — the imperfections feel of-a-piece. Sloppy varies randomly.

If the imperfection feels uncertain ("did they mean this?") it's not yet designed; it's still on the way to being something. Refine it until the intent is clear.

Worked examples

A meditation app's hero illustration

A meditation app's hero illustration is a hand-drawn ink wash of a mountain landscape — visible brushstrokes, subtle imperfections in the lines, watercolor-like color pooling. The illustration sits within a precisely-aligned page layout (typography is set, navigation is precise).

The contrast is the point: the illustration brings warmth and reflection; the surrounding UI provides functional clarity. Both elements serve the product.

A handwritten signature in a confirmation email

A confirmation email signs off with a handwritten signature (an SVG of an actual signature) rather than a typed name. The handwritten element reads as personal — the rest of the email is professionally formatted. The signature does small but real work in establishing brand warmth.

A note app that uses a serif with humanist character

A note-taking app uses a humanist serif (something like Charter, Source Serif, or IBM Plex Serif) for body text. The typeface has subtle character variation — slightly varied stroke widths, organic curves, a sense of having been written rather than computed. Compared to a geometric sans-serif, it feels more personal.

This is wabi-sabi at the typography level. The imperfection is in the typeface design, applied uniformly within the product.

Tilted cards that cross into sloppy

A product designs cards that are tilted at random angles for "warmth." Each card sits at a slight rotation. The intent is to feel hand-arranged. The result feels broken — users wonder if the layout has rendered incorrectly.

The fix: either align all the cards (commit to precision) or use larger, more deliberate rotations (commit to the imperfection register clearly). The middle ground reads as bug.

Hand-drawn icons among vector ones

A product mixes hand-drawn icons (for category headings) with vector-precise icons (for actions). The two sets have different intent: the hand-drawn ones feel personal and warm; the vector ones feel functional and precise. The mix communicates hierarchy: "this is a heading you'll engage with thoughtfully" vs. "this is an action you'll take quickly."

When done well, the mix is coherent: each icon set is well-crafted within its register; the use of each is consistent.

Anti-patterns

Reflexive sloppy. Adding imperfection without intent. A jumbled layout that's not organized either by precision or by deliberate asymmetry.

Imperfection in functional UI. A submit button that's slightly tilted or has hand-drawn text. Functional UI benefits from precision; imperfection here reads as broken.

Inconsistent register. Some surfaces wabi-sabi, others highly precise, with no logic to which is which. Users get confused.

Imperfection that hurts accessibility. Hand-drawn typography that's hard to read; asymmetric layouts that confuse screen readers; organic textures that reduce contrast for low-vision users.

Imperfection without restraint. Wabi-sabi imperfection is supposed to coexist with overall restraint. Combined with maximalism, it just adds to the chaos.

Cultural surface adoption. Calling something "wabi-sabi" because it has tilted elements, without engaging with the deeper aesthetic philosophy. The work feels shallow.

Heuristic checklist

When designing imperfect elements, ask: Is this imperfection intentional, or accidental? Be able to articulate the intent. Is it refined within its irregularity? Hand-drawn should still be well-drawn. Is the register appropriate for the context? Personal / creative welcomes more; functional / data resists. Will it scale across the product or just this surface? Hand-crafted elements have maintenance costs. Does it hurt accessibility? If yes, reconsider. Is the design overall restrained, so the imperfection has room to breathe? Imperfection plus richness equals chaos.

Related sub-skills

  • wabi-sabi — parent principle on the aesthetic of imperfection and restraint.
  • wabi-sabi-restraint — sibling skill on the absence-of-decoration half.
  • aesthetic-usability-effect — warmth contributes to perceived usability.
  • archetypes — Caregiver, Creator, and Sage archetypes align with wabi-sabi register.

See also

  • references/imperfection-techniques.md — practical techniques for adding deliberate imperfection.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Wabi Sabi Imperfection AI skill do?

Design intentional imperfection that reads as warmth — subtle asymmetry, hand-drawn elements, organic textures, intentional irregularities. Use when adding human warmth to a digital design, distinguishing from competitors with uniform design systems, designing for personal or creative contexts. The skill is making imperfection look intentional and refined rather than sloppy or broken; the line between "designed warmth" and "looks unfinished" is narrow.

Why use Wabi Sabi Imperfection on TypingMind?

Because you install it once and use it with any model. Wabi Sabi Imperfection 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 Wabi Sabi Imperfection in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Deibler/universal-design-principles/tree/main/plugins/aesthetics-and-emotion-principles/skills/wabi-sabi-imperfection. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Wabi Sabi Imperfection?

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 Wabi Sabi Imperfection?

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

Is the Wabi Sabi Imperfection AI skill free?

It is published on GitHub by Deibler. Check the repository for licensing terms. 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 👇