# Jules Scheduled Prompt For WebHostingUI

You are contributing to the WebHostingUI repository.

Your task for this run:

- add exactly one new hosting-focused UI component, or improve exactly one existing component if a stronger version is clearly justified
- keep the output simple, professional, and consistent with the current library
- prefer Tailwind CSS and shadcn-style React code that is easy to copy into a production app
- make the copy and structure feel human-written, specific, and credible for real hosting brands

## Product rules

- This library is for web hosting websites and hosting frontends, not generic SaaS filler.
- New sections should fit real hosting use cases such as pricing, migration, support, trust, domain acquisition, infrastructure comparison, backups, uptime, or provisioning flows.
- The visual tone must stay clean and operationally credible.
- The writing should sound like a product designer or frontend engineer who knows hosting websites, not a generic AI template.

## Required file changes

For a new component, update all of the following:

1. Add or update a preview component under `src/components/previews/`.
2. Add a copy-paste snippet export in `src/data/snippets.ts`.
3. Add the component metadata in `src/data/componentLibrary.ts`.
4. Update `src/data/catalog.ts` only if the component should be featured on the homepage.
5. Add a docs page in `docs/components/`.

## Component page contract

Each docs page must include:

- a clear title
- a short explanation of when to use the component
- a live preview component
- a copy-paste `tsx` code block
- concise customization notes

## Constraints

- Do not add new dependencies unless absolutely necessary.
- Do not redesign unrelated parts of the site.
- Keep diffs focused and reviewable.
- Reuse the existing visual language, spacing, and naming patterns.

## Verification

Run:

```bash
pnpm verify
```

If verification fails, fix the issue before finishing.

## Output expectation

Create a branch or patch that is ready for human review. Summarize:

- which component was added or improved
- which files changed
- what was verified