> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blitzy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Generation Prompts

> Create your initial request for AI-Native code generation

export const WistiaVideo = ({mediaId}) => <div style={{
  position: 'relative',
  paddingTop: '56.25%',
  overflow: 'hidden',
  borderRadius: '8px'
}}>
    <iframe src={`https://fast.wistia.net/embed/iframe/${mediaId}?videoFoam=true`} title="Wistia video player" allowTransparency="true" frameBorder="0" scrolling="no" allowFullScreen style={{
  position: 'absolute',
  top: 0,
  left: 0,
  width: '100%',
  height: '100%'
}} />
  </div>;

<WistiaVideo mediaId="g8rsgs7ih4" />

## Overview

Code generation prompts tell Blitzy what changes to make. The key insight: **you don't need a perfect, detailed specification upfront**. Submit your request, review the Agent Action Plan (AAP), and iteratively add specificity where needed.

<Card title="Browse prompt templates" icon="file-contract" href="/templates">
  Explore ready-to-use templates for common scenarios like features, bug fixes, refactoring, and testing
</Card>

***

## Creating Your Prompt

<Steps>
  <Step title="Draft Your Initial Request">
    Start with the essentials: **Objective** (what you want to accomplish), **Scope** (what's in/out), and **Success Criteria** (how you'll know it's done). Use the [Validation Checklist](/prompt-engineering/validation-checklist) to ensure your initial request covers key areas.
  </Step>

  <Step title="Submit and Review the AAP">
    Submit your request and review the generated Agent Action Plan (AAP). Does it align with your expectations?
  </Step>

  <Step title="Identify Gaps">
    Spot misalignments in the AAP and identify which prompt sections are missing or need refinement.
  </Step>

  <Step title="Add Specificity Tactically">
    Refine your prompt using [Golden Rules](/prompt-engineering/golden-rules) for clarity and [Rules](/templates/rules-overview) for quality dimensions.
  </Step>

  <Step title="Iterate Until Satisfied">
    Re-submit your refined prompt and review the updated AAP. Repeat until you're satisfied with the plan.
  </Step>
</Steps>

***

## Key Sections to Include

When structuring your prompt, consider including these sections:

**Objective Statement** - What you want to accomplish

**System Boundaries** - What's in scope, out of scope, and what must not be modified

**Technical Specifications** - Technology preferences and architectural patterns (optional)

**Figma Attachments** - Attach frame URLs for [design-to-code workflows](/templates/feature-product-development/figma-to-code) (optional)

**Success Criteria** - Measurable outcomes to validate completion

<Note>
  You can attach up to **10 files** per prompt. Supported attachment formats: code files, text files, Markdown, PDF, and Figma frame URLs.
</Note>

<Warning>
  **Spreadsheet files cannot be attached to prompts.** CSV, Excel (`.xls`, `.xlsx`), ODS, and Parquet files are read from your repository during ingestion and code generation, but they are not supported as prompt attachments. To include tabular data in a prompt, convert it to **Markdown** or **PDF** before attaching.
</Warning>