How to Transition a Detailed Design System to Claude for Custom Site Builds After Setup

Emily M. · 2026-09-14T10:07:05.150Z

Just watched Adam's demo video and I really like the granularity of control available. I'm wondering if after finishing setting up the design system with that tight degree of control, how can I hand all of that context over to Claude and build from there, e.g. once the initial site is done, the client wants to add something custom and that there is no component for?

4 comments

· Sorted by Oldest

Emily M.
·
·
I'm also wondering about contrast. It looked like Adam was able to change the eyebrow text to have too little contrast with the background. It would be great to have a contrast-checker built in that advises you away from that
Matt J.
·
·
Emily M. really good feedback! We're working on answering this exact thing with a couple of announcements coming very soon! As for contrast - a significant amount of time and research went into contrast and accessibility - I wasn't able to quickly go to the part in the video where this eyebrow text happened - I'd love to pinpoint it - maybe its a bug - or maybe it passes our checks, but to your point doesn't "feel" like it should. Would love to get to the bottom of that one either way if you can help me out there that would be greatly appreciated!
Emily M.
·
·
It's around 11:28 when he's playing around with colour schemes, the eyebrow text on the section directly below the hero doesn't look high contrast enough to me, which may be wrong. It looks like you could make the eyebrow any of the available colours though, which is why I thought there should be some sort of warning away from choosing a lighter colour.
Matt J.
·
·
yeah, really good point and I do think our intention is to build in more guardrails. Which kind of brings up something with your feedback - the two pieces are at a bit of conflict with each other conceptually right because the first piece was like "Like the control, can I have absolute freedom" and then your second one is like "can the system check contrast and/enforce it" and yeah the check could be there without enforcement, or limiting you as a designer so I get that but yeah conceptually its like "Less rails, but also still make it default great" and that'll be a hard line for us to walk as we build out features. Where to limit to protect default great, and where do we allow full freedom? That's the friction point you know? Always appreciate your feedback - always pushing us!

Emily M.
·
·
I'm also wondering about contrast. It looked like Adam was able to change the eyebrow text to have too little contrast with the background. It would be great to have a contrast-checker built in that advises you away from that
Matt J.
·
·
Emily M. really good feedback! We're working on answering this exact thing with a couple of announcements coming very soon! As for contrast - a significant amount of time and research went into contrast and accessibility - I wasn't able to quickly go to the part in the video where this eyebrow text happened - I'd love to pinpoint it - maybe its a bug - or maybe it passes our checks, but to your point doesn't "feel" like it should. Would love to get to the bottom of that one either way if you can help me out there that would be greatly appreciated!
Emily M.
·
·
It's around 11:28 when he's playing around with colour schemes, the eyebrow text on the section directly below the hero doesn't look high contrast enough to me, which may be wrong. It looks like you could make the eyebrow any of the available colours though, which is why I thought there should be some sort of warning away from choosing a lighter colour.
Matt J.
·
·
yeah, really good point and I do think our intention is to build in more guardrails. Which kind of brings up something with your feedback - the two pieces are at a bit of conflict with each other conceptually right because the first piece was like "Like the control, can I have absolute freedom" and then your second one is like "can the system check contrast and/enforce it" and yeah the check could be there without enforcement, or limiting you as a designer so I get that but yeah conceptually its like "Less rails, but also still make it default great" and that'll be a hard line for us to walk as we build out features. Where to limit to protect default great, and where do we allow full freedom? That's the friction point you know? Always appreciate your feedback - always pushing us!