When creating or editing cookbook documentation, the following should be addressed in the cookbook in this order, utilizing the suggested mintlify components:

"What You'll Build" section should cover:

• What is the end result/system the user will have built?
• What is the main workflow or automation being created?
• Component: Use <Card title="What You'll Build" icon="robot"> with blank lines and proper indentation

For "What You'll Learn" section (3-4 items) should cover:

• What is the primary tool/MCP being used and its main function?
• What specific skills will they learn? (e.g., "Analyze X with AI", "Automatically create Y", "Set up Z monitoring")
• Format: Use ## What You'll Learn heading with bulleted list starting with "This cookbook teaches you to:"

For "Prerequisites" section include:

• What is the primary requirement? (e.g., "GitHub repository", "API account")
• What service account is needed and what plan tier?
• What additional tools are required and how to verify installation?
• What service-specific setup step is needed?
• Components: Use <Steps> component with proper indentation, <Tip> component for helpful notes

For "Workflow Options" section:

• What is the service name for the section title?
• Where is the pre-built agent located? (Hub URL)
• What command installs the agent?
• What are the agent's key features/benefits?
• What is the first task users should try?
• Where is the MCP located on Continue Hub?
• What are the manual setup steps?
• Components: Use <Card title="🚀 Fastest Path to Success" icon="zap">, <Tabs> with <Tab> components, <Steps>, <Info> for explanations, <Accordion> for requirements

Mintlify Component Guidelines:

• Always add blank lines after opening and before closing component tags
• Indent content by 2 spaces within components
• Use proper list formatting with each item on its own line
• For <Info>, <Tip>, <Warning>: Format lists as bullet points, not inline
• For <Steps>: Each step should have a clear title and indented content
• For <Tabs>: Maintain proper nesting with consistent indentation

Always ask for specific details rather than accepting vague descriptions. Ensure all links and commands are accurate.