Sponsor Details
![[Dress Code Inc] logo](/2026/images/sponsor-logo/platinum/dress-code.png){kind=logo}
We are a startup tackling the social challenge of "operational friction" in business processes, guided by our mission to "organize all operations so that anyone can naturally and comfortably execute them."
We are currently developing solutions to address operational challenges across multiple domains, including IT administration, HR and labor affairs, and general affairs. Our goal is to integrate these into a unified compound product.
Going forward, we plan to expand into areas such as recruiting and corporate governance, evolving into an integrated platform that supports the full spectrum of business operations.
・Learn more: https://www.dress-code.com/ja
・Tech Blog: https://zenn.dev/p/dress_code
Enforcing a Design System Contract in a Compound Product
In a compound product that spans multiple domains, even aligned components let token usage and component roles drift before anyone notices.
Writing conventions in docs and fixing them in review still cannot keep up as the codebase grows, and a component catalog cannot inspect that drift.
So we made the design system itself a schema-based contract, and with Schema-Driven UI the same schema can reproduce the same frontend.
Raw values fail typecheck, and cross-layer imports fail dependency lint. Human review is left for judgments machines cannot make. This talk is about protecting frontend implementation with a contract.
Dress Code Inc.
Product Engineer