Week 22ARCHIVED · MAY 25–31

Classlist

Spaced repetition for your design system documentation.

On the web

About this project

Pitch

Design system docs go stale the instant they're written. A team renames a token, a component absorbs a new variant, a deprecation notice never gets a follow-up — and within six months, the docs site is somewhere between misleading and dangerous. Classlist fixes the underlying problem: docs and code are never the same artifact.

Classlist parses your component library at build time, extracts the actual props, defaults, slots, and a11y annotations from your code, and surfaces them as a docs page that updates with every PR. When a designer asks "is this prop still there?" the answer is in the docs, not the Slack thread.

We integrate with Storybook, Vite, Next.js, and any framework that emits TypeScript types. You write zero markdown. You write zero MDX. You ship your component and the docs update on the next deploy. The team meeting where you talk about "doc debt" stops being a recurring event.

Inside the product

Screenshots

The team

2 builders
  • Tomas Ships@tomas_ships

    Founder · Design Systems

    Maintained design systems at three companies. Built Classlist after rewriting the same doc page for the 12th time.

  • Sofia Open@sofia_oss

    Engineering

    Open source maintainer. Wires Classlist into your Storybook so docs and code share a single source of truth.

Discussion

0 comments

Sign in to join the discussion.

No takes yet. Be the first to weigh in.

More in SaaS

See all →