Skip to content
Module
Module 2 of 5Lesson 2 of 2~18 min

Frame your tool and its success criteria

Asking for code before you have scoped your tool leads to an app that solves nothing. This lesson helps you describe the problem, the user and the expected result precisely, then write verifiable acceptance criteria that will guide the agent as well as your own testing later on.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to describe your tool (problem, user, inputs, result, name) and write at least three checkable acceptance criteria before asking for a single line of code.

Topics covered

  • product scoping
  • acceptance criteria
  • user needs
  • coding agent

Where it fits

Frame the tool and choose how to build it

What will I build, with which tool, and how will I know it worked?

Lessons in this module

  1. Chat, app builder or coding agent?
  2. Frame your tool and its success criteria (this lesson)

What you will learn in the course

This lesson is part of the course Build and ship a web app with an AI coding agent

  • Frame a tool (problem, user, inputs, expected result) and write its acceptance criteria before generating a single line of code.
  • Choose between a chat with artifacts, an app builder and a coding agent based on the need, the level of control required and the risk.
  • Write a build request for a coding agent (context, scope, constraints, verification) and get a plan approved before any code is written.
  • Set up the environment (terminal, Node.js, Git, Claude Code), run the application locally and explain what the main files of the generated project are for.
  • Evolve and debug the application in small, checked, committed iterations, giving the agent the right context (symptom, steps, error message).
  • Review the generated app before sharing it (behavior, edge cases, secrets, personal data, experience) and decide whether to ship, fix or stop.
  • Publish the app from GitHub to a host with continuous deployment, get a public URL and evolve the live version without breaking it.

Related courses