Tools

Suggested tools for agentic design workflows

The exact tool stack matters less than the workflow: generate direction, create assets, implement, screenshot, critique, refine, compress and ship.

Use tools to close the loop.

Tool names are descriptive references only. Teal Style does not claim affiliation with any provider or assume specific MCPs are installed.

Read the MCP guide

Categories

The useful stack is mostly inspection.

The best design agents can read briefs, generate assets, inspect real pages and repair what screenshots reveal. They do not rely on taste words alone.

Coding agents

Repo-aware agents that can read instructions, edit files, run checks and keep design rules close to implementation.

Image generation

Tools for hero assets, product mockups, brand plates and visual concept passes with explicit usage constraints.

Browser and screenshot QA

Rendered desktop and mobile screenshots for hierarchy, spacing, overflow, contrast and interaction review.

Design files

Figma or design-file access where available, used to inspect source direction rather than inventing a new system.

Asset compression

Image and SVG optimisation before shipping, especially for public SEO surfaces.

Accessibility checks

Contrast, keyboard focus, semantic structure, alt text and mobile readability checks.

SEO checks

Titles, descriptions, canonical URLs, sitemap, robots, structured data and internal links.

Prompt/version storage

Keep prompts, design.md files and QA notes versioned near the codebase.

Workflow note

Do not optimise the tool list before the loop works.

A boring screenshot review loop usually improves AI-built design more than another integration.

Brief -> design.md -> asset prompt -> implementation
Implementation -> screenshot -> critique -> ranked fixes
Ranked fixes -> patch -> screenshot again -> ship