Agent Design
The largest agent's design resources. By Agent. For Agent.
https://agents-design.com/skills
I built a directory of 100+ design skills for Cursor / Claude / Codex — taste, motion, typography, anti-slop UI.
What’s in it:
• Anti-slop / taste skills (Hallmark, Impeccable, Taste Skill…)
• Motion (GSAP, spring, scroll storytelling)
• Visual systems (type, color, shadows, layout)
Browse, pick a skill, drop it in your agent.
Hey IH 👋
Just launched agents.design — a curated gallery of UI templates, DESIGN.md specs, and prompts built specifically for AI coding agents.
## What it is
[agents-design.com](https://agents-design.com)
- Browse templates by page type, industry, mood, visual style
- Copy an agent-ready prompt (or download template + DESIGN.md)
- Paste into your coding agent and ship something that doesn't look templated
Works with: Cursor · Claude Code · Codex · v0 · Bolt · Lovable
## Business model (early)
- Free browsing / free designs to try the workflow
- Pro unlocks unlimited premium templates, components, full DESIGN.md + prompts, request templates, and ongoing drops
Still early — catalog is growing regularly (goal is everyday additions).
## What I'd love feedback on
1. Is the "copy prompt → paste into agent" flow obvious enough?
2. Which page types should we prioritize next (waitlist, docs, dashboard, pricing, mobile…)?
3. Would you pay for this vs. just dumping screenshots into chat?
Happy to share more on how we're producing the catalog / DESIGN.md pipeline if useful.
Site → https://agents-design.com
-
1
The interesting challenge isn't improving two landing pages—it's deciding which product has the stronger long-term strategic advantage before splitting attention between both. I'd keep validating whether one product consistently earns stronger user pull, because focus is often a bigger growth lever than incremental landing page improvements.
1 Comment
100+ skills is real coverage, but “browse, pick, drop it in” risks turning taste into another dependency list. I’d promote a smaller set into workflow-tested bundles with one before/after artifact and a clear compatibility note. What earns a skill its place here: a working demo, repeat use, or curation judgment?