Original Summary

I’ve been building Skrewww , an open-source React and TypeScript design system that started as a Figma ↔ React parity project. The problem I kept running into was that design systems usually work well for either designers or developers, but AI coding agents often have to guess component APIs, props, maturity, installability, and usage rules from scattered documentation. So I started treating the design system as a structured product rather than just a component library. Right now Skrewww includes: a Figma design system paired with React components a shadcn-compatible registry machine-readable contracts for coding agents a local CLI called Skrewww Guard that validates a small set of canonical claims offline a reference app used to test real component composition explicit Stable/Beta maturity instead of pretending everything is production-ready One thing I learned while building it: consistency between Figma, React, docs and AI-readable metadata does not automatically mean the system is correct. You still need an authoritative source and independent consumer testing. I’m currently improving performance, distribution, and the AI workflow around the system. Project: https://skrewww.com GitHub: https://github.com/usmanfarooqi88/skrewwwDS I’d especially like feedback from people building component libraries or developer tools: Would machine-readable component contracts actually help your AI coding workflow, or do you think normal TypeScript + docs are already enough?   submitted by   /u/usman-farooqi [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/25 03:41:41