#113 by GitHub stars
elayadesign/ai-design-skills
Design inside Figma the way this designer does: real variables, text styles, auto layout and components, on a fixed visual system (Tailwind type and radius scale, spacing tokens, two-layer color tokens, button and state rules). Use this skill whenever you create, edit or review anything in a Figma f
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/figma-designer/SKILL.md
Week of Nov 2, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 456d9e0d3e2d
No earlier version was observed for comparison.
skills/landing-page-design/SKILL.md
Week of Nov 2, 2026 · +54 / −6 lines
Before Instructions only → After Instructions only
ded7efc9d5c0 → 456d9e0d3e2d
- 194 ### Button type
- 195
- 196 - Main buttons: `text-base` (16px), semibold.
- 197 - Smaller header buttons: `text-sm` (14px), semibold.
+ 194 ### Text styles
+ 195
+ 196 Every piece of text uses one of these named styles. Never style text with a loose size and weight. Use the names exactly as written, including capitalization.
+ 197
+ 198 | Style | Scale step | Size / line height | Weight |
+ 199 |---|---|---|---|
+ 200 | Heading 1 | `text-6xl` | 60 / 60 | Semibold |
+ 201 | Heading 2 | `text-5xl` | 48 / 48 | Semibold |
+ 202 | Heading 3 | `text-4xl` | 36 / 40 | Semibold |
+ 203 | Heading 4 | `text-3xl` | 30 / 36 | Semibold |
+ 204 | Heading 5 | `text-2xl` | 24 / 32 | Semibold |
+ 205 | Heading 6 | `text-xl` | 20 / 28 | Semibold |
+ 206 | Title 1 | `text-xl` | 20 / 28 | Medium |
+ 207 | Title 2 | `text-lg` | 18 / 28 | Medium |
+ 208 | Title 3 | `text-base` | 16 / 24 | Medium |
+ 209 | Title 4 | `text-sm` | 14 / 20 | Medium |
+ 210 | Title 5 | `text-xs` | 12 / 16 | Medium |
+ 211 | Body 1 | `text-base` | 16 / 24 | Semibold |
+ 212 | Body 2 | `text-base` | 16 / 24 | Medium |
+ 213 | Body 3 | `text-base` | 16 / 24 | Regular |
+ 214 | Body 4 | `text-sm` | 14 / 20 | Semibold |
+ 215 | Body 5 | `text-sm` | 14 / 20 | Medium |
+ 216 | Body 6 | `text-sm` | 14 / 20 | Regular |
+ 217 | Button-lg | `text-lg` | 18 / 28 | Semibold |
+ 218 | Button-md | `text-base` | 16 / 24 | Semibold |
+ 219 | Button-sm | `text-sm` | 14 / 20 | Semibold |
+ 220 | Button-Xsm | `text-xs` | 12 / 16 | Semibold |
+ 221 | Caption 1 | `text-sm` | 14 / 20 | Medium |
+ 222 | Caption 2 | `text-sm` | 14 / 20 | Regular |
+ 223 | Caption 3 | `text-xs` | 12 / 16 | Semibold |
+ 224 | Caption 4 | `text-xs` | 12 / 16 | Medium |
+ 225 | Caption 5 | `text-xs` | 12 / 16 | Regular |
+ 226
+ 227 How the groups work:
+ 228
+ 229 - **Heading** for page and section headings, largest to smallest. Heading 1 is the hero.
+ 230 - **Title** for card titles, list item titles, labels that lead a block, and nav items.
+ 231 - **Body** for running text. Within each size, 1 is the strongest weight and the last is regular.
+ 232 - **Button** for text inside buttons only. Main buttons use Button-md, small header buttons use Button-sm.
+ 233 - **Caption** for metadata, helper text, badges, timestamps, and fine print.
+ 234
+ 235 The sizes come from the type scale above, so a style never introduces an off scale value. If a project needs a new style, add the next number in its group (for example Body 7) built from a scale step, rather than inventing a new name.
+ 236
+ 237 In code, define each style once as a reusable class or token with the same name in kebab case (`heading-1`, `body-4`, `button-md`, `caption-2`) and apply that, instead of repeating size and weight utilities on every element.
- 302 - **Numbers.** Avoid suspiciously round figures. Pricing should look like real pricing, metrics should carry a decimal or an odd final digit, and dates across a list should vary.
+ 342 - **Never invent facts.** On a real product's page, prices, guarantees, statistics, customer counts, testimonials, and logos must come from the user or a real source. When a fact is missing, use a clearly marked placeholder such as `{{price}}` or `{{testimonial}}` instead of making one up.
+ 343 - **Sample numbers.** In fictional demos and prototypes (where the invented names and brands above are fine), avoid suspiciously round figures. Pricing should look like real pricing, metrics should carry a decimal or an odd final digit, and dates across a list should vary.
+ 375 - A check at 390px wide: no horizontal overflow, buttons keep their text inside, and the primary action is visible in the first screen
- 344 - Size `text-4xl` to `text-6xl` depending on line count, following the B1 type scale.
+ 386 - Use Heading 3 to Heading 1 from the B1 text styles, depending on line count.
+ 394 - Under `prefers-reduced-motion`, show the final text at full color right away, with no word by word animation.
+ 428 - [ ] Every text element uses a named text style (Heading, Title, Body, Button, Caption)
+ 436 - [ ] No invented prices, stats, or testimonials; missing facts use marked placeholders
+ 437 - [ ] Checked at 390px with no overflow
+ 448
+ 449 The no invented facts rule and reduced motion support for the tagline reveal were suggested by [@allen-baler](https://github.com/allen-baler) in [#1](https://github.com/elayadesign/ai-design-skills/pull/1).
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → ded7efc9d5c0
No earlier version was observed for comparison.
Heat
8.3- Star growth, last 7 daysAhead of 99% of tracked repositories
- Star growth, last 24 hoursAhead of 99% of tracked repositories
- Rank movement, last 7 daysAhead of 91% of tracked repositories
- Commits, last 30 daysAhead of 80% of tracked repositories
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekAhead of 0% of tracked repositories
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
Individual skills in this repository
- figma-designer
skills/figma-designer - landing-page-design
skills/landing-page-design
How it works
figma-designer
When your agent uses it
Design inside Figma the way this designer does: real variables, text styles, auto layout and components, on a fixed visual system (Tailwind type and radius scale, spacing tokens, two-layer color tokens, button and state rules). Use this skill whenever you create, edit or review anything in a Figma file through the Figma MCP: screens, landing pages, components, mockups, design systems, tokens, or any UI. Use it even when the user doesn't name the skill and only says things like 'design a page in Figma', 'make a button component', 'mock this up' or shares a figma.com link. Load it before writing any use_figma code.
What it loads into context
Frontmatter
150 tokensAlways available to the agent
SKILL.md
6,194 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Workflow
- Typography
- Spacing
- Corner radius
- Color
- Contrast and accessibility
- Layout
- Icons
- Components and states
- Motion (prototype only)
- Content
- Landing pages
- File hygiene
- Checklist (run before reporting)
- Token reference
Files
SKILL.mdcore22,079 bytes
Read SKILL.md
# Figma Designer
These are the designer's own rules for working in Figma. They sit on top of the official Figma skills and don't replace them.
- **Load `figma-use` before any `use_figma` call.** It holds the Plugin API rules (color ranges, font loading, layout sizing). This skill only adds design rules.
- For full screens and pages, also load `figma-generate-design`. For component libraries and tokens, also load `figma-generate-library`.
- Exact token names and values are in [Token reference](#token-reference) at the end of this file. Read it before you create or bind any variable or text style.
## Workflow
1. **Check the file first.** List local variable collections and text styles, and search the file's libraries (`search_design_system`) for variables, styles and components. Reuse what exists before creating anything.
2. **Set up foundations if missing.** Create everything below before you build any screen:
- the `spacing` and `radius` variables
- the two color layers (`Core Colors`, then `Color System` with Light and Dark modes)View the complete source on GitHublanding-page-design
When your agent uses it
Complete system for building high converting landing pages: intake questions, page structure, layout selection, conversion copywriting, SEO, plus strict visual rules for typography, spacing, corner radius, backgrounds, hero layout, icons, and motion. Use this skill whenever building, editing, styling, reviewing, or writing copy for ANY landing page, marketing site, web UI, page section, component, or prototype, even when the user does not mention design, conversion, tokens, or a design system. Always consult it before choosing page sections, headlines, CTAs, fonts, font sizes, spacing values, border radii, background colors, icons, or transitions.
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
5,618 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Scope
- A1. Intake
- A2. Page structure
- A3. Layout selection
- A4. Conversion rules
- A5. Copywriting
- A6. Build order
- A7. SEO and AEO
- A8. Pitfalls
- B1. Typography
- B2. Spacing
- B3. Corner radius
- B4. Borders and backgrounds
- B5. Hero section
- B6. Icons
- B7. Motion
- B8. Content realism
- B9. States
- B10. Ship requirements
- B11. Tagline reveal section (mandatory)
- Credits
Files
SKILL.mdcore22,115 bytes
Read SKILL.md
# Landing Page Design
A landing page is not a homepage. A homepage serves multiple intents. A landing page wins one intent:
**one offer → one audience → one primary action.**
This skill has two halves. **Part A** decides what the page says and how it is structured. **Part B** is the non negotiable visual system. Work through A before touching B.
## Scope
Apply to all web UI work: landing pages, marketing sites, components, dashboards, prototypes, and design reviews. When a rule here conflicts with a framework default, this file wins. When the user's explicit prompt conflicts with a rule, the user wins.
**Companion skill.** For upgrading an *existing* site rather than building a new one, use `redesign-existing-projects` ([github.com/elayadesign/redesign-skill](https://github.com/elayadesign/redesign-skill)). It diagnoses generic patterns and defers to this file for every concrete value.
View the complete source on GitHubSkills included
- figma-designer
- landing-page-design
Repository facts
- License
- MIT
- Created
- Jul 29, 2026
- Last pushed
- Nov 1, 2026
- Forks
- 1,076
- Open issues
- 2
- Project activity
- Active
Rank over the last 12 weeks
Now #113 · best #113 · up 300 in 30 days
- #123 on Oct 30
- #120 on Oct 31
- #118 on Nov 1
- #117 from Nov 2 to Nov 3
- #115 on Nov 4
- #113 since Nov 5
79 earlier periods
- #853 on Aug 2
- #770 on Aug 7
- #760 on Aug 8
- #745 on Aug 9
- #771 on Aug 10
- #770 on Aug 11
- #768 on Aug 12
- #770 on Aug 13
- #638 on Aug 14
- #603 on Aug 15
- #614 on Aug 16
- #612 on Aug 17
- #611 on Aug 18
- #566 on Aug 19
- #516 on Aug 20
- #508 on Aug 21
- #491 on Aug 22
- #513 on Aug 23
- #500 on Aug 24
- #495 on Aug 25
- #479 on Aug 26
- #485 on Aug 27
- #479 on Aug 28
- #458 on Aug 29
- #441 on Aug 30
- #456 on Aug 31
- #458 on Sep 1
- #449 on Sep 2
- #454 on Sep 3
- #442 on Sep 4
- #433 on Sep 5
- #412 on Sep 6
- #416 from Sep 7 to Sep 8
- #414 from Sep 9 to Sep 10
- #415 on Sep 11
- #413 on Sep 12
- #411 on Sep 13
- #402 on Sep 14
- #403 on Sep 15
- #405 on Sep 16
- #402 on Sep 17
- #404 on Sep 18
- #396 on Sep 19
- #405 on Sep 20
- #399 on Sep 21
- #405 on Sep 22
- #396 on Sep 23
- #393 on Sep 24
- #391 on Sep 25
- #386 on Sep 26
- #398 on Sep 27
- #402 on Sep 28
- #413 on Sep 29
- #408 from Sep 30 to Oct 1
- #409 on Oct 2
- #398 on Oct 3
- #397 on Oct 4
- #405 on Oct 5
- #409 on Oct 6
- #413 on Oct 7
- #423 on Oct 8
- #412 on Oct 9
- #396 on Oct 10
- #392 on Oct 11
- #401 on Oct 12
- #391 on Oct 13
- #388 on Oct 14
- #386 on Oct 15
- #392 on Oct 16
- #383 on Oct 17
- #389 on Oct 18
- #390 on Oct 19
- #392 on Oct 20
- #391 from Oct 21 to Oct 22
- #389 on Oct 23
- #328 on Oct 24
- #309 on Oct 25
- #133 on Oct 28
- #126 on Oct 29
Before you install
Instructions onlyAutomated signals, not a guarantee
Checked Nov 4, 2026
- No broad tool permissions
- No dangerous shell commands
- 3 network referencesin 1 file: landing-page-design/SKILL.md:18
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
Show all 3 signals by file
skills/landing-page-design/SKILL.md
- Network accessline 18
**Companion skill.** For upgrading an *existing* site rather than building a new one, use `redesign-existing-projects` ([github.com/elayadesign/redesign-skill](https://github.com/elayadesign/redesign-skill)). It diagnoses generic patterns a - Network accessline 449
The no invented facts rule and reduced motion support for the tagline reveal were suggested by [@allen-baler](https://github.com/allen-baler) in [#1](https://github.com/elayadesign/ai-design-skills/pull/1). - Network accessline 451
Parts of this skill were adapted from [taste-skill](https://github.com/Leonxlnx/taste-skill) by Leon Lin ([@LexnLin](https://x.com/LexnLin)), MIT licensed. Its redesign audit structure, content realism checks, and motion and navigation idea
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Signal confidence: 3 facts
- Network access in prose of the SKILL.mdlanding-page-design/SKILL.md:18Low confidence
- Network access in prose of the SKILL.mdlanding-page-design/SKILL.md:449Low confidence
- Network access in prose of the SKILL.mdlanding-page-design/SKILL.md:451Low confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Compatible | Standard SKILL.md skills/figma-designer/SKILL.md | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/figma-designer/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/figma-designer/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/figma-designer/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/figma-designer/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/figma-designer/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
Explore alternatives and comparisons
Add this badge to your README
It updates every night and links to this page.
[](https://hotskills.dev/skill/elayadesign-ai-design-skills/)