SaaS tool
For small AI tools with an input, generated result, and simple export path.
- Quiet professional tone
- Clear primary action
- Readable generated output
Free DESIGN.md drafts for AI coding agents
Starter contexts for the first validation audience: AI coding users building SaaS tools, dashboards, and directories.
For small AI tools with an input, generated result, and simple export path.
For operational products where users scan tables, statuses, and detail panels.
For SEO tools, resource libraries, and comparison-driven product directories.
Example briefs that produce different design rules without changing the core generator.
Input-heavy tool with a markdown result, validation checklist, and export actions.
Compact product surface for AI coding cost, sessions, and risk flags.
Comparison-first resource site with compatibility, setup facts, and update notes.
Each agent path stays factual: paste or attach the generated file as project context, then ask the agent to plan before it changes UI code.
Place the generated file in the project or paste it before a UI task. Ask Codex to list affected files, constraints, and verification steps first.
Use the file as project context before composing or editing components. Keep the change scoped to one visible surface.
Ask Claude Code to read the design context, propose a short UI plan, and verify the rendered result against the file.
The generator's readiness score is based on the same minimum file sections users need before asking an agent to implement UI.
Global style, palette, typography, spacing, layout, and component rules are concrete enough to execute.
The file states what the agent must preserve, what it must avoid, and when it should ask before changing direction.
The file includes browser checks for desktop, mobile, overflow, console errors, and visual fidelity.
Use each file for a different job. The MVP avoids claiming official integration and focuses on practical project context.
| File | Main job | Best used when | Risk if misused |
|---|---|---|---|
| DESIGN.md | Visual system and UI implementation rules. | Before building or restyling product surfaces. | Too vague, or copied from a brand without rights. |
| AGENTS.md | Project-level working rules for coding agents. | When a repository needs operating instructions. | Mixing process rules with visual design rules. |
| CLAUDE.md / Cursor rules | Tool-specific behavior and workflow preferences. | When one coding tool needs persistent instructions. | Locking context to one tool and losing portability. |
The MVP success signal is not praise. It is copy, download, real agent use, feedback, and requests for URL or screenshot extraction.
Ask 10 English AI coding users to paste one real project requirement, generate the file, and try it with their agent.
Continue only if users copy or download the file and ask for stronger extraction, validation, or reusable style libraries.