# Give your coding agent a design system (https://divplate.com/docs/design-system-for-ai-agents)



Ask an agent for a landing page and you often get the same one: a centred headline, three cards, a gradient. The code can work fine. What is missing is a set of design decisions for the agent to follow, so it falls back on what is common.

A design system gives it those decisions. Here is what that means with Divplate.

## Finished sections to install [#finished-sections-to-install]

Your agent installs a block rather than writing one. An installed block comes with its phone layout, its dark mode and its accessibility done. A copy from a screenshot usually loses them. See [install, do not copy](https://divplate.com/docs/ai-assistants#installing-not-rebuilding).

## Rules for what is not in the library [#rules-for-what-is-not-in-the-library]

Your first install adds `components/blocks/AGENTS.md`, a short file on how the blocks are built: how wide a row of cards gets, how sections are spaced, and which classes do nothing. When you ask for a section we do not have, your agent can read it, so what it writes fits in. See [new sections](https://divplate.com/docs/ai-assistants#agents-md).

## Your colors, not ours [#your-colors-not-ours]

Everything in a block is a shadcn/ui variable, so a block takes on your existing theme. If you have none, install [one of our palettes](https://divplate.com/docs/colors).

## Try it [#try-it]

The [setup prompt](https://divplate.com/docs/getting-started#with-an-agent) connects your agent in one step. Then ask for a page in plain words.
