> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/readme.md).

# Welcome

Everything you need to set up, customize, and run your theme — written for founders, not developers. No code anywhere in these guides unless it's copy-paste.

## Pick your theme

👉 [**Reign**](/sitesbyseth-docs/reign/reign.md) — the flagship. Full streetwear system with the deepest section library.

👉 [**Skeleton**](/sitesbyseth-docs/skeleton/skeleton.md) — minimal and conversion-first. Free-gift tiers, quick view, smart size finder, drop mode.

👉 [**Showcase**](/sitesbyseth-docs/showcase/showcase.md) — cinematic full-screen product stories. Auto cutouts, 3D lookbook, buy-now upsells.

## The fastest path

Every theme's docs follow the same track:

1. **Getting Started** — install to live, page by page, in order.
2. **Theme Settings** — every global setting explained.
3. **Sections** — what each section does and every setting on it.
4. **Advanced** — size charts, free gifts, updates, the deeper stuff.
5. **FAQ** — when something looks wrong, start here.

💡 Most stores are fully set up in under an hour. That's the guarantee: if yours isn't, you get a full refund.

## Support

* 💬 DM [@sitesbyseth](https://www.instagram.com/sitesbyseth/) on Instagram
* 📧 Reply to your order confirmation email
* 📖 Free playbook: [0 TO 6FIG](https://www.sitesbyseth.com/pages/0-to-6fig) — the strategy behind the themes


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.