How to brief your AI like a senior dev.
The gap between AI generating slop and AI shipping production code isn't model choice. It's how you brief. Three patterns that turn your AI into a senior collaborator.
April 26, 2026
If you've watched a senior engineer onboard a junior, you've seen the pattern: they don't dump tasks. They set context, define the shape of done, and only then describe the work.
Most non-devs prompt their AI the opposite way. They describe the work first ("build me an auth page") and assume the AI will figure out the context.
It mostly won't. Or it will hallucinate one.
Three things change everything:
1. State the schema before the feature. Before you ask for a screen, hand your AI the data model. "Here's the users table, here's the projects table, here's the relationship." Now every line of code it writes can reference the real shape of your data.
2. Define done. "Build a sign-up form" is ambiguous. "Build a sign-up form that calls api.auth.signUp with email and password, redirects to /onboarding on success, and renders the prettified error inline on failure" is not. The second one ships.
3. Hand it the rules of the house. Every codebase has unwritten rules — naming, file structure, what's a leaf component, where business logic lives. Write them down. Hand them over. Stop expecting the AI to guess.
The pattern is the same one good engineers use with other engineers. The model doesn't need a smarter brain. It needs the context a senior would already have.