> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/intelligence/quickstart.md).

# Quickstart

<figure><img src="https://3699482212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo2rUkBX2AsQjv8oqk1um%2Fuploads%2Fgit-blob-44dda596431e871df08351d716ec99674c5a7add%2FGroup%203%20(6).png?alt=media" alt=""><figcaption></figcaption></figure>

This guide walks you through opening CRAFTSMAN INTELLIGENCE, starting your first conversation, and understanding how the assistant routes your requests.

***

### Open the Assistant

Click the **CRAFTSMAN INTELLIGENCE** button in the bottom-right corner of the PLAY editor. This opens the chat panel.

***

### Start a Conversation

When you open the chat panel, you'll see two ways to get started:

**Type freely.** Enter any message in the input field describing what you need. CRAFTSMAN INTELLIGENCE will automatically route your request to the right specialty based on your prompt. For example, typing *"Resize the headline to 48px"* will activate the Builder Agent, while *"Review this design and suggest improvements"* will activate Design Recommendations.

**Browse specialties.** The chat panel displays a card for each specialty — Builder Agent, Feature Generation, Asset Generation, Design Recommendations, Creative Strategy, Concept Ideation, Analytics Insights, and Creative Generation. Click any card to see a set of **template prompts** tailored to that tool, then click a template prompt to send it directly — just as if you had typed it yourself. Cards that work on your open project (Builder Agent, Feature Generation, and Design Recommendations) only appear when you have a PLAY project open.

{% hint style="info" %}
Template prompts are a great way to explore what each specialty can do without needing to write a prompt from scratch.
{% endhint %}

***

### How Specialties Work

CRAFTSMAN INTELLIGENCE operates through **specialties** — focused skill sets that each handle a different part of the playable ad workflow. When you send a message, the assistant identifies which specialty is best suited to help and responds accordingly.

Some specialties provide **advice and analysis**, like design feedback or performance insights. Others **take action directly in your project**, like editing layers, animations, or interactions on your behalf.

In every case, you stay in control. The assistant explains what it's doing, and you can guide it with follow-up messages to refine the result.

The specialties are:

* **Design Recommendations** — Actionable feedback on layout, color, typography, CTAs, and brand compliance.
* **Builder Agent** — Direct project editing through conversation.
* **Creative Strategy** — Data-backed guidance on trends, competitors, and what to build next.
* **Analytics Insights** — Performance analysis, drop-off diagnosis, and variant comparison.
* **Concept Ideation** — Original playable ad concepts with scene-by-scene storyboards.
* **Feature Generation** — Custom features built with a Code Layer, beyond what the built-in layers can do.
* **Asset Generation** — Images, music, sound effects, and voiceover generated from a description.
* **Creative Generation** — Whole playables and animated banners built from a brief, a video ad, a Photoshop file, or a template.

***

### Next Steps

* Dive into any specialty [guide](/intelligence/specialties/creative-generation.md) to learn what each tool can do.


---

# 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://help.craftsmanplus.com/intelligence/quickstart.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.
