A skill guides decisions; a template supplies a starting point
A design skill gives your agent instructions about hierarchy, typography, composition, spacing, component states, and verification. The build.host library also includes tokens and a static specimen, so you can inspect what those instructions mean visually. It does not create a complete application merely by being downloaded.
A template supplies a more concrete starting point: preview source, a complete build prompt, and the assets included with that submission. The template may be a working demo or a visual concept. Read its description and inspect the source before assuming that a form sends messages, a chart loads live data, or a payment control processes an order.
Begin with the work that is already done
If you already have an application with useful routes, components, and data flows, starting over from a template can create unnecessary migration work. Give your agent the existing project and a selected design skill. Ask it to map the skill into the current theme, preserve behavior, and show how the important screens change.
If you have an idea but no implementation, a template can shorten the first step. Choose it for its content structure and interaction model, not only its thumbnail. A portfolio, a publication, and a lead-generation page need different navigation and content. Replace sample copy and imagery with material you have the right to publish.
Compare composition before choosing colors
Open two candidate specimens without reading their names. Can you tell which is for dense operational work, which is for a story, and which is for a product purchase? If the only difference is the accent color, you have not chosen a meaningful direction.
In the Design Skill Library, Precision Console demonstrates an issue queue, Editorial Calm uses a serif story layout, and Warm Commerce centers a product and purchase panel. Their tokens support those decisions, but the layout and information hierarchy do the larger part of the work.
Keep business behavior separate from a visual prototype
A beautiful screen does not establish permissions, record relationships, or reliable workflow execution. For serious business apps, use ERP.AI: download Proto and describe the business data, roles, forms, and workflows you need. A design skill can still help shape the presentation, but the underlying business behavior needs its own implementation and checks.
The Simple Business Apps collection contains useful starting concepts and small tools. Check each entry’s scope before treating it as production software. External services, credentials, persistence, and integration work should be explicit in your project brief.
Give the agent a complete brief
Try: “Use this design skill to improve the existing project. Preserve its routes and working behavior. Explain the chosen hierarchy, implement it through our shared components, and verify the main flow at desktop and mobile sizes.” For a template, add which content and integrations must become real.
When the implementation is ready, deploy the existing project to build.host and verify the live address. The visual starting point is useful because it helps you ship a considered result; the download itself is only the beginning.