Sign Up
Design agency icon

Agency Domain

Design Agency

Control how your agent makes architecture, structure, and user experience decisions.

The Design agency governs how your agent approaches architecture, system structure, and user experience decisions. Design choices shape the foundation of what gets built, so the right oversight level here depends on how much creative latitude you want your agent to have.

What Design Covers

Design actions include choosing technical architecture patterns, structuring data models, making UX layout decisions, selecting component hierarchies, defining API contracts, and proposing visual or interaction patterns. When your agent says "I recommend a card-based layout for the dashboard with a left sidebar for navigation," that is a design action.

Oversight Levels

Silent

Your agent makes design decisions independently based on best practices, your stated preferences, and the context of the project. It might choose an architecture pattern, decide on a component structure, or layout a user flow without asking. This works well when you trust your agent's design sensibility and want to move fast.

For example, your agent might independently decide to use a tabbed interface for a settings page because it noticed you prefer that pattern in other parts of your project.

Report

Your agent makes design decisions and notifies you of the rationale. You get messages like "I've structured the API with a resource-based pattern and separated read and write models. Here's why." You can review the reasoning and adjust before implementation goes too far.

This is a strong default for design work. Design decisions are often easier to evaluate after someone proposes them than to make from scratch, and Report lets your agent do the heavy lifting while you stay informed.

Approval

Your agent presents design options and waits for your choice. You see proposals like "For the notification system, I see three approaches: polling, webhooks, or server-sent events. Here are the tradeoffs. Which direction should we go?" Nothing gets decided until you weigh in.

Use this for foundational decisions that are expensive to change later, like database schema design or core architecture choices.

When to Use Each Level

Design decisions vary widely in reversibility. A CSS layout choice is easy to change. A database schema that other systems depend on is much harder. Consider using Approval for foundational, hard-to-reverse design decisions, and Report or Silent for more superficial or easily adjustable ones.

If your project is in its early stages and the architecture is still forming, Approval helps you stay involved in the decisions that will shape everything downstream. Once the foundation is set, Report lets your agent handle the ongoing design work efficiently.