vibecode.sh
Blocks

Goal

Define the objective and desired outcome for the AI

Goal

The Goal block states what you want to achieve. It defines the desired outcome clearly and specifically, giving the AI a target to aim for. Without a clear goal, the AI may produce technically correct but ultimately unhelpful responses.

When to Use

Every prompt should have a clear goal. Use Goal blocks to:

  • Define deliverables: What exactly should the AI produce?
  • Set success criteria: How will you know if the response is good?
  • Establish scope: What is and is not part of this task?
  • Prioritize outcomes: What matters most if trade-offs are needed?

How to Use

  1. Add a Goal block to your prompt canvas
  2. State the desired outcome in clear, specific terms
  3. Include success criteria if helpful
  4. Connect it logically with your Role and Context blocks

Examples

Clear Development Goal

Create a React hook called useDebounce that:
- Accepts a value and delay in milliseconds
- Returns the debounced value
- Properly cleans up timeouts on unmount
- Includes TypeScript generics for type safety
- Works with React 18 strict mode

Content Creation Goal

Write a product description for our new project management tool.

The description should:
- Be exactly 150-200 words
- Highlight the three main features: real-time collaboration,
  AI task prioritization, and automated reporting
- Appeal to engineering managers at mid-size companies
- Include a clear call-to-action

Analysis Goal

Review the provided API endpoint code and identify:
1. Security vulnerabilities (prioritize these)
2. Performance bottlenecks
3. Code maintainability issues

For each issue found, provide:
- Severity rating (high/medium/low)
- Specific location in the code
- Recommended fix with code example

Research Goal

Compare the top 3 headless CMS options for our use case.

Evaluate based on:
- Pricing for 100k API calls/month
- React/Next.js integration quality
- Content modeling flexibility
- Self-hosting options

Output: A comparison table followed by a recommendation with reasoning.

Tips

  • Be specific about format: "A list" vs "A numbered list with descriptions"
  • Include measurable criteria: Word counts, number of items, specific sections
  • State what success looks like: "The user should be able to copy-paste this directly into their codebase"
  • Mention what to avoid: "Do not include deprecated methods"
  • Prioritize when needed: "Focus on security first, then performance"
  • One goal per block: If you have multiple distinct goals, consider multiple prompts or clear sub-goals

On this page