Patterns and Best Practices
This is a product learning surface, not a general handbook for agentic software work. Patterns name the repeatable work shapes Agent Studio supports. Best practices are concrete operating rules for using Agent Studio well.
Some ideas are broadly useful, but the framing here always returns to Agent Studio: how to shape tasks, connect CLIs, keep evidence, run reviews and set up projects so the product becomes useful in real work.
Patterns
Fire and Review Later
Start bounded Agent Studio tasks asynchronously, then review evidence, diffs and outcomes when the run is finished.
Token-to-Software
Use Agent Studio token reporting to compare agent spend against accepted, reviewable software work.
Structure as Context
Use repository structure, docs, ADRs, prompts and feature boundaries as reusable Agent Studio project context.
Bridge‑in, Evidence‑out
Import selected work into Agent Studio, execute through the configured runner boundary, then return evidence and review state.
Drift Report to Follow-up Task
Use Agent Studio drift findings to turn mismatches between docs, roadmap and runtime behavior into repair tasks.
Voice-to-Task Capture
Capture high-context spoken intent and turn it into bounded Agent Studio tasks instead of forcing perfect specs.
Bounded Agent Slice
Cut Agent Studio work into small slices where the agent can finish, evidence can be checked and the human can decide.
Agent Mode Matching
Use Agent Studio modes to choose different agents for implementation, review, docs, large-context reading and migration.
External CLI on the Side
Keep working in VS Code or a trusted coding-agent CLI while Agent Studio carries tasks, API handoff, evidence and review.
Open patternWorkforce Sensemaking CLI
Run Agent Studio as a visible agent workforce while a same-context CLI helps the human understand, diagram and correct the work.
Open patternPlus-One / Plus-N Developer
Use Agent Studio as one or more additional reviewable developer lanes while the human works in parallel at a higher quality and architecture altitude.
Open patternBest Practices
Separate Development and Stable
Configure Agent Studio work around Development for active work and Stable for review, testing and reference behavior.
Encode the Dev/Stable split in prompts
Tell Agent Studio runners where work happens, where review happens and which checkout must remain untouched.
Automate Stable updates
Use an update mechanism so Agent Studio’s review/reference checkout can follow main without becoming a second work branch.
Use workspace folders with guard rules
Group related repos in an Agent Studio workspace, but require ownership, write scope and project identity for every task.
Use strong linting for frontend projects
Expose linting, formatting and component rules as Agent Studio quality rails before human review.
Angular quality rails
Plan ESLint, template linting, SCSS linting, component splitting and reusable Angular components before the website grows further.
Open guideCut tasks small and closed
Prefer small, self-contained Agent Studio tasks with clear input, output and acceptance surface over broad specification work.
Keep feature slices shaped by developers
Agents can implement slices in Agent Studio, while developers shape feature folders, boundaries and architecture.
Record Evidence with the Task
Keep screenshots, tests, tutorials, diffs and review notes with the Agent Studio task so acceptance is inspectable.
Patterns
Patterns describe reusable shapes that Agent Studio makes visible or easier to operate. They are not generic advice by themselves; they become useful when they help users recognize a recurring Agent Studio workflow and repeat it deliberately.
Best practices
Best practices are more direct. They tell users how to configure Agent Studio, cut tasks, structure repositories and keep agent output reviewable inside the product workflow.
Why the Split Matters
A pattern helps people understand the work model Agent Studio enables. A best practice helps people set up Agent Studio and their repositories tomorrow morning. The distinction keeps both forms useful and product-specific.