Every component was prepared with properties clearly identified and ready to test across all variants, states, and sizes. Boolean properties handled optional elements — icons, labels, trailing actions — keeping variant counts lean while maximising flexibility.

For complex components like Cards and Action Items, we introduced a nesting architecture using Design Component Properties (DCPs). Rather than building dozens of rigid variants, each base component was constructed to be assembled like building blocks — changing a nested DCP to match a specific breakpoint, toggle a header title, or swap a footer CTA required a single property change, not a new component.

Eventually, this is where Figma's Slots feature would just now in 2026 become a reality to avoid all the nesting manual adaption.
Slots define nested areas within a component where any content can be placed without breaking the component's constraints or layout rules. A Card component with defined slot areas for its header, body, and action zone can serve a DAO summary, a governance proposal, a token listing, or an onboarding step — all from a single component, with zero structural changes. Without Slots, the same coverage would have required maintaining a sprawling variant matrix that grew with every new product context. With Slots, the component stays singular and the context becomes the variable.