# Prompt Basics

{% hint style="info" %}
For live examples and templates, see [Prompt Examples & Usecases](/prompting/prompt-basics/prompt-examples-and-use-cases.md).
{% endhint %}

***

### 1. Context & Objectives

{% stepper %}
{% step %}
**Define Audience & Goals**

* Describe the target persona (e.g. “tech-savvy professionals,” “young creatives”).
* State the primary goal (e.g. “showcase portfolio,” “drive sign-ups,” “educate users”).
* Optionally include success metrics (“increase click-through by 20%”).
  {% endstep %}

{% step %}
**Align on Brand & Tone**

* Describe the target persona (e.g. “tech-savvy professionals,” “young creatives”).
* State the primary goal (e.g. “showcase portfolio,” “drive sign-ups,” “educate users”).
* Optionally include success metrics (“increase click-through by 20%”).
  {% endstep %}

{% step %}
**Provide Examples & Inspiration**

* Link to existing sites, components, or mood boards.
* Share screenshots or describe visual references (“in the style of X”).
* Outline layouts or flows you admire (e.g. “two-column hero with side nav”).
  {% endstep %}
  {% endstepper %}

***

### 2. Design & Technical Specifications

{% stepper %}
{% step %}
**Be Precise in Layout & Style**

* Specify structural elements (header, footer, sidebar, grid).
* Call out spacing, typography, color usage.
  {% endstep %}

{% step %}
**Detail Interactions & Behavior**

* Define hover, focus, or animation effects.
* Include links / URLs to which the elements or cards should be linked to (e.g. “link the Banner CTA “Shop Now” to `[URL]`”).
  {% endstep %}

{% step %}
**Outline Content & Data Needs**

* Provide placeholder text, sample images, or data schemas.
* Specify pagination, filtering, or sorting requirements.
  {% endstep %}

{% step %}
**Set Technical & Performance Constraints**

* Define responsiveness targets (mobile, tablet, desktop breakpoints).
  {% endstep %}
  {% endstepper %}

***

### 3. Workflow, Iteration & Feedback

{% stepper %}
{% step %}
**Encourage Creative Latitude**

* Allow the AI to suggest variations (“feel free to propose alternative layouts”).
* Use open-ended prompts for brainstorming (“generate three hero concepts”).
  {% endstep %}

{% step %}
**Structure Revision Cycles**

* After initial output, ask targeted follow-ups (“reduce header height by 20px”).
* Use **Select to Edit** for pinpoint changes on specific elements.
* Save iterations as Remix or duplicate projects to track progress.
  {% endstep %}

{% step %}
**Clarify When to Ask Questions**

* Prompt the AI to request missing details (“What’s the primary call-to-action?”).
* Provide additional context only when needed to avoid lengthy back-and-forth.
  {% endstep %}
  {% endstepper %}

***

### 4. Advanced Tips

* **Chain Prompts**: break complex tasks into sequenced prompts (scaffold → style → validate → document).
* **Leverage Brand Styles**: prefix prompts with `[YourBrandStyle]` to auto-apply theme settings.
* **Use Examples Inline**: include screenshot references to guide output.
* **Control Scope**: specify “only modify the banner”

***

By combining clear context, precise specs, and structured iteration, you’ll streamline your Maker workflow and achieve on-target results every time.

***


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.maker.co/prompting/prompt-basics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.