Skip to content
Back to search

tactile-design

Tactile, layered, quiet product UI: a design-engineering skill for agents. Decisions, tokens, buttons, surfaces, motion and mobile, for any typeface and colours.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kosta4a--tactile-design/badge.svg)](/listings/kosta4a--tactile-design)

HTML

<a href="/listings/kosta4a--tactile-design"><img src="/api/listings/kosta4a--tactile-design/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code

Copy or symlink the skill folder into your skills directory.

# copy
cp -R skills/tactile-design ~/.claude/skills/

# or symlink, so a git pull updates it
ln -s "$(pwd)/skills/tactile-design" ~/.claude/skills/tactile-design

For a single project, use `.claude/skills/` inside that project instead of `~/.claude/skills/`.

With the [skills CLI](https://github.com/vercel-labs/skills):

npx skills add kosta4a/tactile-design

Claude loads the skill when a task matches its description (building or reviewing product UI). You can also ask for it by name: "Use tactile-design to build the settings page" or "Review this modal against tactile-design".

Other agents

The skill is plain Markdown. Point your agent at `skills/tactile-design/SKILL.md` and let it open the reference files as needed.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 96 lines
  1. # tactile-design
  2. A design-engineering skill for agents and people. It teaches how to build **tactile, layered, quiet** product interfaces, and how to make the decisions behind them.
  3. Tactile: controls look like objects. White buttons sit on the page with a fine ring and a crisp drop, and squeeze slightly when pressed. Fields sink in as wells. The one action that matters is solid black.
  4. Layered: every surface knows what it sits on, and takes its fill, edge and drop from it, so a control feels equally pressable on a page, a card, a table row or a sheet. In light mode a raised surface is white with a ring and a crisp drop. In dark mode it is a step or two lighter, with one solid 0.5px outline and a tight black drop. Sizes never change between themes.
  5. Quiet: one type weight, a neutral palette, 0.5px lines, very little colour. Hierarchy comes from contrast steps, not from bold text or bright hues. Motion is short and always has a reason.
  6. The skill is distilled from building a production dashboard through hundreds of rounds of pixel-level design review. It records the rules and the thinking behind them, so an agent can apply them to a new screen instead of copying an old one.
  7. ## What it covers
  8. - **Decision order**: what to settle first (hierarchy and the next step), then how much data, placement, component, surface, type, colour, motion, phone, and the final review.
  9. - **Buttons and controls**: primary, secondary, utility pills, icon buttons, ghost and destructive tiers; fields, toggles, switches, choice rows, badges; press, hover, focus, disabled, loading and copy states.
  10. - **Surfaces and layering**: ground, panel, raised, well and overlay; shadow recipes for light and dark; modals, bottom sheets, menus, popovers, toasts, cards and tables.
  11. - **Layout and hierarchy**: column widths, spacing rhythm, proportion rules, where actions go, how much data to show, empty and loading states, copy.
  12. - **Motion**: whether to animate at all, curves, durations, springs, patterns with exact values, interruption, reduced motion.
  13. - **Mobile**: touch targets, type floor, stacking, dialogs as sheets, sheet drag physics, native-feeling touch.
  14. - **Tokens**: a role-based token system (12-step neutral, hue scales, hairlines, shadows, radii, durations, easings, spacing) with a template for remapping to your own typeface and colours.
  15. ## Layout
  16. ```
  17. tactile-design/
  18. ├── README.md
  19. ├── LICENSE
  20. └── skills/
  21. └── tactile-design/
  22. ├── SKILL.md # posture, decision order, rules at a glance, never-ship list
  23. └── references/
  24. ├── tokens.md # role-based tokens, default values, remapping template
  25. ├── buttons-and-controls.md
  26. ├── surfaces-and-layering.md
  27. ├── layout-and-hierarchy.md
  28. ├── motion.md
  29. ├── mobile.md
  30. └── decisions.md # recurring decisions and how they were made
  31. ```
  32. ## Install
  33. ### Claude Code
  34. Copy or symlink the skill folder into your skills directory.
  35. ```sh
  36. # copy
  37. cp -R skills/tactile-design ~/.claude/skills/
  38. # or symlink, so a git pull updates it
  39. ln -s "$(pwd)/skills/tactile-design" ~/.claude/skills/tactile-design
  40. ```
  41. For a single project, use `.claude/skills/` inside that project instead of `~/.claude/skills/`.
  42. With the [skills CLI](https://github.com/vercel-labs/skills):
  43. ```sh
  44. npx skills add kosta4a/tactile-design
  45. ```
  46. Claude loads the skill when a task matches its description (building or reviewing product UI). You can also ask for it by name: "Use tactile-design to build the settings page" or "Review this modal against tactile-design".
  47. ### Other agents
  48. The skill is plain Markdown. Point your agent at `skills/tactile-design/SKILL.md` and let it open the reference files as needed.
  49. ## Adapt it to your brand
  50. The skill names **roles and ratios**, not hex codes. The concrete values (a warm 12-step neutral, Inter, a 13px base) are only the defaults. To use your own:
  51. 1. **Neutral.** Pick any 12-step neutral scale (gray, slate, mauve, olive, sand, or your own) for light and dark, once, at setup. Pairing it with your brand hue is fine (slate with blue, mauve with purple). Map it to `--ink-1` ... `--ink-12`. Steps 1–2 are grounds, 3–5 fills, 6–8 lines, 9–10 faint text, 11 secondary text, 12 strong text. Then run the contrast gates in `tokens.md`.
  52. 2. **Brand colours.** Turn each into a 12-step light scale and a 12-step dark scale (the Radix custom palette generator does this). Use step 3 as a tint, 6 as an edge, 9 as a solid, 11 as text, and the scale's contrast colour for text on step 9. Status colours (success, danger, warning, info) keep their meaning; a brand hue close to one becomes that status's scale. Never mix brand hue into the neutral steps.
  53. 3. **Typeface.** Pick one sans for everything and one mono for machine values (IDs, code, keys). Then follow "Typeface fit" in `tokens.md`: `font-size-adjust` matches its size to Inter's, a side-by-side test picks the one weight, and tracking and font features are checked.
  54. 4. **Shadow ink.** Set `--shadow-ink` to your light ink-12. Every light-mode shadow reads it; dark shadows stay black.
  55. 5. **Radius.** Set `--radius-control` to match your icon set (4–8px). The rest of the radius ladder follows from it.
  56. 6. **Keep the ratios.** Control heights, the 0.5px hairline, the shadow ladder, durations and the spacing rhythm carry over unchanged.
  57. `references/tokens.md` has a complete CSS custom-property template with light and dark values, the surface step-shift classes and a Tailwind v4 mapping.
  58. ## Credits
  59. - Distilled from designing and building a production dashboard, including the designer's own review notes and the reasons recorded next to each decision.
  60. - Motion principles, and mobile native-feel and sheet drag conventions, follow the teaching of **Emil Kowalski**. The skill paraphrases his ideas and credits them where they apply. His course is at [animations.dev](https://animations.dev). Any mistakes in the paraphrase are ours.
  61. - The colour model uses the 12-step scale structure of [Radix Colors](https://www.radix-ui.com/colors). The default neutral is Radix's sand scale.
  62. - Touch-target and sheet conventions follow Apple's Human Interface Guidelines.
  63. ## Contributions
  64. This repository doesn't take pull requests or issues. Fork it and adapt it freely under the license.
  65. ## License
  66. MIT. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.