this interaction got a lot smoother when I toggled visibility via CSS instead of mounting/unmounting the element.
this allowed me to persist video progress, remove mounting flicker, and add starting transitions.
shown:
{ isShown ? "translate-y-0 starting:translate-y-0.5" : "hidden" }
smoother than:
{ isShown && <Element /> }
Found an *actually* useful way to use agent teams for design systems:
- Explorer agents comb docs, production codebases, platform docs for usage/guidelines relevant to a specific skill (e.g. responsive design)
- Main agent helps you write targeted skill.md with real code samples
I made an AI prototyping environment for my team (to build React prototypes with our design system) and this @paper shader onClick easter egg might be my favorite part
@kevinyien I was able to rebuild most of our design system in Claude Design without maxing my credits by:
1. Claude generates style specs based on Figma MCP
2. Use @nathanacurtis Specs CLI to generate structural data
3. Combine these into one spec file per component
4. Upload files to CD
Spicy take:
The older, slower path of developing ideas through canvas-based tools, paired with Claude Code for prototyping, is producing more intentional and better creative outcomes than these insanely over-processed AI workflows.