Templates

Start from a curated template — fork it, make it yours, and share.

Choose by the problem, not the appearance

Each template demonstrates a specific interface problem: presenting a launch, comparing plans, collecting a response, documenting a system, or explaining service health. Open the detail page to understand its structure and limitations before you fork it.

Treat every template as reviewed starter code

Replace fictional content, verify accessibility, and test empty, error, and narrow-screen states. Templates deliberately avoid production credentials and back-end behavior; connect those parts securely in your own application.