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.Browse prompt templates
Explore ready-to-use templates for common scenarios like features, bug fixes, refactoring, and testing
Creating Your Prompt
1
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 to ensure your initial request covers key areas.
2
Submit and Review the AAP
Submit your request and review the generated Agent Action Plan (AAP). Does it align with your expectations?
3
Identify Gaps
Spot misalignments in the AAP and identify which prompt sections are missing or need refinement.
4
Add Specificity Tactically
Refine your prompt using Golden Rules for clarity and Rules for quality dimensions.
5
Iterate Until Satisfied
Re-submit your refined prompt and review the updated AAP. Repeat until you’re satisfied with the plan.
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 (optional) Success Criteria - Measurable outcomes to validate completionYou can attach up to 10 files per prompt. Supported attachment formats: code files, text files, Markdown, PDF, and Figma frame URLs.