Design Tools · a practical workflow
Give your next build a direction.
Use studied references to explain what you want, turn that brief into a direction, and check the result. SaturnAI Design Tools provide guidance for the assistant you already use. Your assistant does the building.
01 · point
Start with an assistant that can read the web.
Paste the connect line into your current conversation. Ask your assistant to read the instructions and retrieve a relevant reference. Open the source it names to confirm the fetch worked.
The URL provides context for that conversation. For callable tools, use the MCP or HTTP setup guide. Future conversations may need the context again.
02 · study
Choose a reference for a reason.
Search studies of real products and techniques. Ask which detail serves your task: a readable pricing table, a clear first-run flow, or navigation that works on a small screen.
The public catalog includes 634 entries, every blueprint, and 11 full write-ups. A free account unlocks the remaining write-ups. See access and usage limits.
03 · commit
Make the brief specific enough to use.
Describe the audience, the main action, and the constraints of your project. The compose tool returns a direction with references and implementation guidance.
Keep your requirements explicit: an existing framework, system fonts, no imagery, or no animation. Review the proposal with your assistant before it changes the project.
04 · build
Build in the tools you already use.
Your assistant applies the direction in your project. Technique cards include dated support information and fallbacks; check them against the browsers and devices you need to support.
Design Tools return references and guidance. File changes, previews, test runs, and deployment depend on your assistant and the tools you give it.
05 · grade
Check the evidence. Inspect the result.
The hosted review applies deterministic checks to the evidence your assistant supplies and returns PASS, REVISE, or REJECT with findings. It does not inspect screenshots and does not operate the page itself.
A PASS covers the evidence supplied. Open the rendered page, try the main interaction, check keyboard access, and inspect the work before accepting it. Missing evidence and untested behavior still need attention.