Design agents are only as good as the knowledge you give them.
I mapped the AI design skills space before SKILL.md and DESIGN.md became the standard. The standards proved the read. Now I make design systems agent-ready.
The scarce asset moved.
Design knowledge used to live in scattered repos, CSVs, and blog posts. Then the standards landed. SKILL.md in December 2025. DESIGN.md in April 2026. Now any agent can consume structured design knowledge. The scarce assets are curation and judgment. That is where I work.
skill-kit is a concept-first knowledge graph of design skills. One concept, one file. Frontmatter as schema, wiki-links as edges. Drop a file into your agent's context and it works. The method is public and re-runnable.
Your design system was written for humans.
Agents read it and guess. The gap between your tokens and a file an agent can act on is real work: what to include, what to cut, which rules survive translation. The race to collect knowledge is over. The standards won it for everyone. Closing your gap is a judgment call, not a download. That is the conversation I sell.
Three ways in.
Audit
2 to 3 days. I turn your design system into SKILL.md and DESIGN.md files, tested against the agents your team uses.
Workshop
Half a day, hands-on. Your team leaves with a working SKILL.md draft for your own system.
Talks
How I built a 577-file design knowledge graph in one focused session, and what it means for design teams.
I am Umair Ali Khatri, Head of UX, based in Karachi. 20 years of choosing design over engineering. My whole ops stack runs through Claude. The skill-kit methodology is public and carries its dates.