What is the ihlamury design-skills pack?
Design Skills by ihlamury is a repository of 87 skills, each extracted from a well-known product such as Linear, Stripe or Apple. Every skill lists semantic colours, typography, spacing, borders, components and interactive states, written as MUST, SHOULD and NEVER rules, so an agent builds consistent interfaces.
The repository is titled UI Skills and holds 87 design skills. The README calls them opinionated UI constraints extracted from leading companies, meant to help AI agents build pixel-accurate, consistent interfaces.
Each skill sits in its own folder under skills, with a SKILL.md and a metadata file. The skills are grouped by sector in the README, from developer tools and fintech to publishing and consumer apps.
What changes in your agent's output
- Colours come from named semantic tokens, such as one exact dark surface value, instead of arbitrary greys.
- Type follows a stated font family and size set, for example Inter for the Linear skill.
- Spacing sticks to a 4px or 8px grid, and border radius and width follow a defined scale.
- Buttons, inputs and cards copy a documented spec, including hover, focus and disabled states.
- Rules are tagged MUST, SHOULD or NEVER, so the agent knows which are hard limits.
Who it is for
Best for
- Teams that want a dashboard, pricing page or settings screen to feel like a named product's style.
- Prototypers who need a fast, consistent starting palette and type scale for an AI-built interface.
- Designers who want to read how a known product's tokens are structured.
Not for
- Original brand work. These rule sets copy the look of existing products, so your own brand needs its own tokens.
- Anyone who needs fresh data. The skills were generated from extractions, and the repository was last updated in February 2026.
- Teams that want to run the extraction pipeline without paid keys, since it needs Codia and ScreenshotOne credentials.
Use it with UiChemy
Once an interface is designed, UiChemy can bring it to WordPress. Figma to WordPress converts a file, and Composer edits the result in Elementor or Gutenberg. Click Get Started on uichemy.com.
How to install Design Skills by ihlamury: 87 Brand-Style UI Rule Sets for AI Agents
git clone https://github.com/ihlamury/design-skills.gitThe README names Claude Code, Cursor, Copilot and Claude.ai uploads, and says any agent can use a pasted SKILL.md. Skills are style extractions, not official brand guides.Clone the repository
Run the clone command above. The README lists this as the manual install route.
Copy one skill
Copy a skill folder, such as skills/linear, into your agent's skills directory. The README example copies it into the Claude skills folder.
Or paste the file
For agents without a skills folder, copy the contents of a SKILL.md into your prompt, or save it into .cursor/skills and reference it by name.
Name the skill in your prompt
Ask for a screen and name the style, for example a pricing page using the Stripe skill.
Check that it loaded
Ask for a settings page in the style of one skill. Check that colours match the skill's tokens, spacing sits on its grid, and components include hover and focus states.
Key features
- 87 product skillsOne skill per product, from Linear, Stripe, Figma and Notion to Shopify, Spotify and Apple.
- Sector groupingThe README sorts skills into groups such as developer tools, productivity, fintech, analytics, e-commerce and design community.
- Semantic colour tokensEach skill lists surface, text and border colours as named tokens rather than loose hex values.
- Typography specsFont families, sizes, weights and text styles are stated for each product.
- Spacing gridSkills specify a 4px or 8px grid and the spacing scale that sits on it.
- Border scalesRadius and width scales are documented per skill.
- Component specificationsButton, input and card specs, plus layout and viewport patterns.
- Interactive statesHover, focus and disabled treatments are written down for components.
- Animation guidanceTiming and performance notes are included in each skill.
- Constraint hierarchyMUST, SHOULD and NEVER labels separate required rules from preferences and bans.
Frequently asked questions
What is ihlamury design-skills?
It is a repository of 87 agent skills that capture how well-known products look. Each includes colour tokens, type, spacing, borders, components, interactive states and animation notes, written as MUST, SHOULD and NEVER constraints for an AI agent to follow.
How do I install the design skills?
Clone the repository and copy the skill folder you want into your agent's skills directory. The README also allows downloading a single SKILL.md, or pasting its contents into a prompt when your agent has no skills folder.
Which products are covered?
The README groups them by sector, including Linear, Figma, GitHub and Vercel for developer tools, Stripe and Mercury for fintech, Shopify for commerce, Notion for productivity and Apple for consumer design. It lists the full set of 87 in a table.
Does it work with Cursor, Copilot and other agents?
The README gives usage notes for Claude Code, Cursor, Copilot and Claude.ai project knowledge, and says any AI agent can use a SKILL.md pasted into a prompt. Install steps differ slightly by tool, so follow the section for yours.
How are the skills made?
The repository includes an extraction pipeline that analyses a website and generates a skill from the result. It needs Python 3.8 or later, a Codia API key and a ScreenshotOne key. You can also contribute a skill by pull request.
Can I use these for my own brand?
They describe other products' looks, so use them for reference or a starting style. For your own tokens see design-tokens, and for building a full system see design-system or color-system.
How current are the skills?
The repository's most recent commit is from February 2026. Product designs change, so compare a skill's values with the live product before treating them as exact, particularly colours and type.
What do MUST, SHOULD and NEVER mean here?
The README defines MUST as an absolute requirement, SHOULD as a strong recommendation and NEVER as an explicit prohibition. The labels let an agent separate hard rules from preferences when two rules appear to conflict.


