Skip to content
Skills Library
Design & UX · Building & coding

graphite

/graphite

Olger Chotza's personal design system "Graphite" — graphite-toned, calm, Apple-simple, with soft color only for meaning. Use for ANY UI or visual work in any stack (web, React, Tailwind, React Native/Expo, SwiftUI, HTML artifacts, emails, slides) — building or editing screens, components, layouts, styling, colors, typography, spacing, icons, motion, empty states, or UI copy, and unslopping AI-looking UI. Load before writing UI code, and run its checklist before calling UI work done.

Repository
graphite ↗
Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
26
Scripts
1
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: tokens/tokens.ts

What it does and when to use it

Olger Chotza's personal design system "Graphite" — graphite-toned, calm, Apple-simple, with soft color only for meaning. Use for ANY UI or visual work in any stack (web, React, Tailwind, React Native/Expo, SwiftUI, HTML artifacts, emails, slides) — building or editing screens, components, layouts, styling, colors, typography, spacing, icons, motion, empty states, or UI copy, and unslopping AI-looking UI. Load before writing UI code, and run its checklist before calling UI work done.

Triggers from the description

s personal design system
Original author description

Olger Chotza's personal design system "Graphite" — graphite-toned, calm, Apple-simple, with soft color only for meaning. Use for ANY UI or visual work in any stack (web, React, Tailwind, React Native/Expo, SwiftUI, HTML artifacts, emails, slides) — building or editing screens, components, layouts, styling, colors, typography, spacing, icons, motion, empty states, or UI copy, and unslopping AI-looking UI. Load before writing UI code, and run its checklist before calling UI work done.

How it works

  1. The 7 rules
  2. Files — read what you need
  3. Workflow
Original SKILL.md headings · 48 lines, 628 words
SKILL.md preview
---
name: graphite
description: Olger Chotza's personal design system "Graphite" — graphite-toned, calm, Apple-simple, with soft color only for meaning. Use for ANY UI or visual work in any stack (web, React, Tailwind, React Native/Expo, SwiftUI, HTML artifacts, emails, slides) — building or editing screens, components, layouts, styling, colors, typography, spacing, icons, motion, empty states, or UI copy, and unslopping AI-looking UI. Load before writing UI code, and run its checklist before calling UI work done.
license: Apache-2.0
metadata:
  version: "2.1.0"
  author: Olger Chotza
  url: https://ochotzas.com
---

# Design System — "Graphite"

Graphite first. The interface is one cool graphite hue — light islands on a soft grey
table, dark ink for everything that matters. **Ink carries emphasis; color only carries meaning**,
and when it appears it's soft — the same lightness and low chroma as the graphite around it.
Feels calm and Apple-simple, but recognizably mine through the graphite palette,
the islands, and Figtree set big and tight.

## The 7 rules

1. **Graphite first, soft color for meaning.** Chrome, text and surfaces are graphite. Color comes only from the soft tokens and always means something: `accent` for links, focus and today/current markers; `success` / `warning` / `danger` (and `accent` for info) for status; `cat-*` only for labels people pick and chart series. No gradients, no brand colors on chrome; a screen stays mostly grey.
2. **Ink is the emphasis.** Primary buttons, selected states, checks, progress — all solid `ink`. Never a colored button (a solid `danger` confirm is the one exception). Emphasis comes from contrast, not color.
3. **Content lives on islands.** Group related content in `surface` islands (radius 22) sitting on the `bg` table. Rows inside an island are split by `line` dividers. Never nest islands, never add shadows to them.
4. **One job per screen.** Exactly one ink-filled primary button. Everything else is a secondary (`surface`) or plain button.
5. **Type does the hierarchy.** Big tight Figtree 700 titles, 500 for row titles, 400 for reading. Max 3 sizes per screen. Secondary info goes to `ink-2`, done/disabled to `ink-3`.
6. **Round and soft.** Capsule buttons, circular checks, rounded islands, pill progress. No sharp corners, no hard borders around islands.
7. **Everything moves on one spring.** iOS-like (stiffness 620, damping 44) — snappy, physical, no visible settle. Gestures hand their release velocity to the spring and every animation can be grabbed mid-flight. Signature effects: push back, drag and fling to dismiss, rolling numbers, blur swap, collapsing title, swipe to delete, shake on error, liquid tabs, zoom open, photo fly-in, armed swipe, lift to reorder, morphing button. Motion only on state change; respect reduced motion.

## Files — read what you need

| File | Read when |
|---|---|
| `tokens/tokens.css` | Web/CSS/Tailwind — import or copy. Never invent values. |
| `tokens/tokens.ts` | JS/TS, React Native, Expo — same tokens typed. |
| `foundations.md` | Color, type, spacing, radius, layout, icons — full specs. |
| `components.md` | Islands, rows, buttons, checks, inputs, progress, nav, sheets, states. |
| `motion.md` | Any animation, transition, gesture — specs for the spring, gesture physics + 13 signature effects. |
| `examples/motion.html` | Working code for every motion effect. Copy from here. |
| `voice.md` | Any UI text. |
| `stacks.md` | Tailwind, React Native, SwiftUI mapping (SwiftUI: native components first). |
| `fonts/` | Figtree TTFs for native apps (iOS, macOS, Android). |
| `anti-patterns.md` | **Always skim** — what agents typically get wrong. |
| `unslop.md` | Cleaning up an existing AI-looking screen: audit list + fix passes. |
| `examples/showcase.html` | Reference implementation. Copy patterns from here. |
| `examples/desktop.html` | Desktop shell: sidebar, main chart, ranked list, table, chips. |
| `examples/unslop.html` | Before/after dashboard: stat rows, one main chart, the unslop passes. |
| `checklist.md` | **Run before declaring UI work finished.** |

## Workflow

1. Read this file + `anti-patterns.md`; read others as needed.
2. Tokens only. If something's missing, use the nearest token — don't add new ones without asking.
3. Build the simplest version that does the job.
4. Run `checklist.md`, fix misses, report the result in one line.
5. If the project already has its own design system, follow the project and mention conflicts.
6. Restyling an existing screen that looks AI-made? Run `unslop.md` first.
Files in this package (26)
  • .gitignore 1 KB
  • CHANGELOG.md 3 KB
  • LICENSE 11 KB
  • NOTICE 1 KB
  • README.md 4 KB
  • SKILL.md 4 KB
  • anti-patterns.md 4 KB
  • checklist.md 3 KB
  • components.md 12 KB
  • foundations.md 10 KB
  • motion.md 16 KB
  • package.json 1 KB
  • stacks.md 7 KB
  • unslop.md 8 KB
  • voice.md 2 KB
  • examples/desktop.html 19 KB
  • examples/motion.html 62 KB
  • examples/showcase.html 65 KB
  • examples/unslop.html 22 KB
  • fonts/Figtree-Bold.ttf 56 KB
  • fonts/Figtree-Medium.ttf 56 KB
  • fonts/Figtree-Regular.ttf 56 KB
  • fonts/Figtree-SemiBold.ttf 56 KB
  • fonts/OFL.txt 4 KB
  • tokens/tokens.css 7 KB
  • tokens/tokens.ts 4 KB

Versions

RepositoryScoreLicence
This page · ochotzas/graphite100Apache-2.0
pleaseai/claude-code-plugins100MIT

Database snapshot: 13.11.2026 · package version 05c52b1fc6f5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 84update-graphite-stack
    Update Graphite PR stacks by addressing review comments and syncing PRs. Use when user says "update my graphite stack", "address the review comments on my stack", "sync my PR stack after these changes", "submit my entire stack to Graphite", or "I need to update all the PRs in my stack".
  • 91refactoring-ui
    Comprehensive UI design guidance based on Refactoring UI principles covering design personality, color theory, layout strategy, visual hierarchy, typography, spacing, mobile-first responsive design, and writing copy that doesn't read like AI wrote it. Use this skill whenever the…
  • 100tailwind-ui-refactor
    Refactoring UI design patterns for Tailwind CSS applications. This skill should be used when writing, reviewing, or refactoring HTML with Tailwind utility classes to improve visual hierarchy, spacing, typography, color, depth, and polish. Triggers on tasks involving UI cleanup,…
  • 95brand-visual-generator
    When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand…
  • 95brand-visual-generator
    When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand…
  • 90practica-brand-design
    Practica brand design system with colors, typography, spacing, and component patterns. Use when building or styling any UI for Practica — pages, components, layouts, blog posts, or landing pages. Ensures visual consistency with the established minimal, clean design language.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.