packages/docs/src/routes/(routes)/blueprint/workflow/+page.md
LLMs often produce generic AI slop by default. They can skim skill files, ignore difficult instructions, hallucinate component syntax, and settle for mediocre design. You then spend more time, effort, and tokens asking for edits.
Blueprint solves this with a guided MCP workflow. Six tools walk the LLM through the task, supply rules and resources one step at a time, and confirm the LLM understood them. The LLM then writes the code. A final inspection finds quality problems for the LLM to fix.
Provides project-specific setup resources:
This helps the LLM work with your existing project instead of guessing its setup or adding conflicting configuration.
Provides the complete daisyUI requirements for:
This keeps the LLM from skimming the rules or dropping constraints once it starts coding.
Provides design guidance for:
This gives the LLM one clear visual direction. It avoids disconnected choices and familiar AI-generated layouts.
Provides a matching plan from 211 page architectures, including:
This helps the LLM plan the full page before writing markup, including states a short prompt may leave out.
Provides current daisyUI resources for each required component:
This lets the LLM use maintained daisyUI syntax instead of recalling stale or invented classes from training data.
Checks the finished source for:
This gives the LLM a specific repair list. The work finishes after the LLM fixes the reported issues and verifies the result.
<div class="mt-12 flex justify-center not-prose"> <a href="/blueprint/checkout/" class="btn btn-primary">Get Blueprint MCP</a> </div>