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

# 2. Project creation and publishing

## Two starting points

**Spawn a Project** begins with an idea. Spawn AI helps develop names, tickers, character directions, artwork and story material. The creator reviews the result and moves toward a public page, optional website tools and a linked token launch.

**Deploy a Token** begins with a prepared identity. A creator can enter the token information directly without completing the wider project-building flow. These entry points serve different levels of preparation while leading to the same need for transaction review and confirmation.

## AI assistance and creator responsibility

AI output provides material to work with. It does not establish originality, intellectual-property rights, factual accuracy or a project's prospects. Names, artwork and descriptions should be reviewed before publication. Creators remain responsible for their claims and for having the rights needed to use their materials.

The platform's creative tools are most useful when a creator gives the project a clear direction and edits the result into a consistent identity. A recognizable image, a concise explanation and reliable links help a visitor understand what the project represents.

## Public presence

Spawn Page gives a project a public home. Spawn Studio supports a fuller website experience, while supporting kit and social tools help prepare material for sharing. Project management tools allow creators to return to their work rather than treating creation as a single session.

A hosted project page and an on-chain token are separate resources. Saving or publishing a page does not itself deploy a token. Likewise, an on-chain launch does not make every accompanying statement true or every external link trustworthy.

## Access and mobile use

Wallet-based tools and account-based tools have different access requirements. A wallet connection identifies the wallet available to approve an action; it is not blanket authorization for later transactions. Some workflows, including the documented NFT creation flow, also require a SPAWN account.

The interface is designed for desktop and mobile use, including supported wallet browsers. Browser context and wallet compatibility can affect connection behavior. Users should confirm which wallet is connected before approving a signature or transaction.

## After publishing

Creators should share the confirmed project URL and full token mint, keep public links current and explain which benefits or milestones are already available. The public [creator launch checklist](https://github.com/spawnmeme/spawnmeme/blob/main/docs/launch-checklist.md) turns this process into practical preparation steps.

***

[Previous: 1. Vision and product model](/spawnmeme-docs/whitepaper/01-vision.md) · [Next: 3. Architecture and transaction boundaries](/spawnmeme-docs/whitepaper/03-architecture.md)


---

# 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://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/02-creation.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.