The guilt, examined
Designers and developers feel a specific shame about copying: 'real' practitioners originate, and copying is for beginners. The guilt is a category error. Painters copy the old masters for years before a brushstroke of their own appears; musicians learn standards before they write originals; the web's best design systems are explicit remixes of the systems that preceded them. Copying is not the opposite of originality — it is the prerequisite for it.
- Copy with intent: the useful copy is not the drag-and-drop of a whole page but the deliberate rebuild of a single pattern — type the code, change the tokens, break it, fix it. Typing is the part that teaches.
- Copy the decision, not the pixels: 'why is this card's shadow this soft?' is the question; the answer (elevation scale, rung 2) is what transfers. Pixels without the decision behind them are a costume.
- Credit is part of the craft: a note in the code or the README ('pattern adapted from X') is not weakness — it is how provenance spreads, and provenance is how the pattern improves.
- The guilt returns as growth: when copying feels wrong, it is because you can now see what to change — that is the moment the copy becomes yours. Steal until you can improve, then improve.
Why this site exists
Motif is built on the premise that copying is fast and knowing why is faster — every component ships with the 'why' exposed, because a pattern with its reasoning attached is teachable and a pattern without it is a trap. The library is not a wall against copying; it is an invitation to copy well. The guilt is the only thing this site is designed to remove.