Why every component ships as a prompt

A component in a registry is not a package. It is a suggestion that has to survive contact with someone else's Tailwind config, someone else's tokens, and someone else's folder conventions.

When you copy raw source you inherit all of that friction. The colours are hard-coded to the author's palette, the import paths assume their aliases, and the demo pulls in data you don't have.

A prompt carries the same source plus the context needed to adapt it: where the files go, which helper it expects, which parts are safe to change. The tool on the other end does the adaptation, because that part was always mechanical.

This is also why the prompt is generated rather than written. It is derived from the same source the preview renders, so it cannot drift from the component it describes.