> For the complete documentation index, see [llms.txt](https://docs.superteamde.fun/superteam-germany-guilds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superteamde.fun/superteam-germany-guilds/build-on-solana/boilerplates-and-starter-kits.md).

# Boilerplates & Starter Kits

Official templates, starter kits, and reference repos for shipping faster on Solana.

If you want to move quickly, start from a maintained template instead of building the first layer from scratch.

## Best Starting Points

* [Solana Developer Templates](https://solana.com/developers/templates) for the official template catalog
* [create-solana-dapp](https://github.com/solana-developers/create-solana-dapp) for one-command project generation
* [Web3.js React Vite Tailwind template](https://solana.com/developers/templates/web3js-react-vite-tailwind) for a general web app base
* [LazorKit Starter](https://solana.com/developers/templates/lazorkit-starter-vite) if embedded wallets or smoother onboarding matter
* [Pinocchio Counter template](https://solana.com/developers/templates/pinocchio-counter) for a minimal native-program example

## Reference Repositories

* [Program Examples](https://github.com/solana-developers/program-examples) for runnable examples across common patterns
* [Program Examples docs](https://solana.com/docs/programs/examples) when you want the same material in docs form

## How To Choose

* use a frontend template if you need a full product quickly
* use a native or Anchor example if the onchain logic is the main challenge
* use the most boring template that gets you shipping fast

For hackathons, optimizing for speed and clarity beats cleverness.


---

# 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://docs.superteamde.fun/superteam-germany-guilds/build-on-solana/boilerplates-and-starter-kits.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.