The no-nonsense approach to AI agent development

Link to headingStep 1: Prototype the agent by hand

Start by simulating the agent manually, before writing any code.

Understand the task the way a person would approach it, step by step. Use real inputs, whether they’re screenshots, API responses, or messy CSV data. Feed those into an LLM manually and guide it through the process with prompts that mirror the actual workflow.

As you go, perform any resulting actions yourself. Pay attention to which parts feel repetitive or mechanical. These are strong candidates for automation later.

Expect early results to be rough. When we started building v0.dev in 2023, LLMs struggled to generate reliable HTML. The breakthrough wasn’t from better models, but from narrowing the scope and using structured inputs with Tailwind.

If the model consistently fails to make progress, even with adjustments, the task may not be a good fit for an agent. But if it works, or even comes close, it’s worth continuing.

Link to headingStep 2: Automate the loop

Once your manual simulation shows that the task is viable, begin writing code. This is where you build the skeleton of your agent.

Start by automating how it collects inputs. Use APIs, scrapers, screenshots, or anything else that fits the problem, then model the agent’s process as a loop or a simple state machine. Gather input, perform deterministic computation where possible, call the model when logic or judgment is needed, evaluate the result, and decide whether to continue or exit.

LLMs are non-deterministic. If you can write a normal function to handle a step, do it. Use plain code for parsing, calculating, or sorting. Anything that does not require reasoning.

1
import { streamText, tool } from "ai";
2
import { anthropic } from "@ai-sdk/anthropic";
3
import { z } from "zod";
4

5
async function stockAnalysisAgent(
6
  symbol: string,
7
  startDate: string,
8
  endDate: string
9
) {
10
  return streamText({
11
    model: anthropic("claude-4-sonnet-20250514"),
12
    system: `You are a professional stock analyst AI powered by Claude Sonnet. You MUST perform a comprehensive analysis using BOTH available tools.
13

14
ANALYSIS STRUCTURE:
15
- Technical Analysis: Use price data, P/E ratio, beta, 52-week range, volume patterns
16
- Fundamental Analysis: Use news sentiment, earnings data, market cap, industry trends
17
- Investment Recommendation: Clear BUY/SELL/HOLD with specific price targets and reasoning
18

19
IMPORTANT: You MUST use both tools before providing any analysis. Do not wait or ask - call both tools immediately and concurrently.
20

21
NOTE: The news search uses Finnhub as the primary source (more reliable for stock news) with NewsAPI as fallback.`,
22
    prompt: `Analyze ${symbol.toUpperCase()} stock comprehensively. Use BOTH the getStockData and searchNews tools to gather complete market data, then provide detailed technical and fundamental analysis with a clear investment recommendation.`,
23
    tools: {
24
      getStockData: tool({
25
        description:
26
          "Get real-time stock price, volume, financial metrics, and historical data for a given symbol using Finnhub API",
27
        parameters: z.object({
28
          symbol: z.string().describe("Stock symbol (e.g., NVDA, AAPL, TSLA)"),
29
        }),
30
        execute: async ({ symbol }) => {
31
          return getStockData(symbol, startDate, endDate);
32
        },
33
      }),
34
      searchNews: tool({
35
        description:
36
          "Search for recent news and analysis about a stock or company using Finnhub (primary) and NewsAPI (fallback)",
37
        parameters: z.object({
38
          query: z
39
            .string()
40
            .describe(
41
              'Search query for news (e.g., "NVIDIA", "Apple earnings", "Tesla Model 3")'
42
            ),
43
        }),
44
        execute: async ({ query }) => {
45
          return searchNews(query, startDate, endDate);
46
        },
47
      }),
48
    },
49
    maxSteps: 5,
50
  });
51
}
52

Don't be afraid of plain old programming. Save the LLM for parts that truly need judgment.

Building AI agents might seem like a new thing that calls for new abstractions, but it is just regular programming. Use if statements, loops, or switches, whatever fits. Don’t overthink the structure. For common patterns, see our AI SDK agent docs.

The agent "works" when it reliably produces acceptable results with little to no intervention.

Link to headingStep 3: Optimize for reliability

Now that the agent is running end to end, shift your focus to improving quality. This means making the agent perform well on both specific examples and a wide range of real-world inputs.

Start by tightening the loop. Refine your prompts. Make tool calls more precise. Remove unnecessary retries. Replace model calls with plain deterministic functions wherever you can. If the agent produces incomplete results, use a second model to critique the results of the first model and continue the work.

At this stage, intuition and hands-on testing are your best tools. Iterate until the agent feels solid when running against real examples. Once the core loop is stable, introduce structured evaluations to test performance across a broad range of inputs and edge cases. This helps catch regressions early and ensures quality holds up as the agent evolves.

Link to headingTakeaways

AI agents expand what software can do, but building one doesn't require reinventing how you think about programming. The most reliable agents are built with the same fundamentals: clear logic, good structure, and tight feedback loops.

Before committing to any implementation, test the task manually using real inputs and prompts. If the model can almost get there with help, it’s probably worth building. From there, structure the logic using ordinary code and only rely on the model when necessary. Once the agent is working, focus on making it resilient. Both on individual inputs and across real-world complexity.

To recap, agents are useful when:

• The task is difficult to automate with traditional code

• Prompting the model manually shows signs of success

• You scope the agent narrowly and build on solid software practices

• You optimize both with hands-on intuition and structured evaluation

When built right, AI agents feel like magic. But there’s no sorcery behind it. Just smart systems with reasoning built in.