Use for storefront pages, bugs, APIs, data scripts, integrations, validation, and technical handoff.
DocsQuick start guide
Get started with Smaug in 10 minutes
Use this guide to create a storefront agent, provide market and product context, attach source files, choose the right specialist workflow, and review the delivered result and approval points.
10minutes
8core steps
FAQsupport ready
How to register an account
Open the registration page, enter a username, email, and password, then sign in to reach your Smaug workspace. Use a work email when possible so billing and support messages stay connected to your team.
Recommended next action
Go to registration or workspace
02
How to create your first agent
Start with the target market, product, storefront URL, business goal, source files, constraints, target languages, and a reviewable output such as a market brief, page package, report, checklist, or code change.
Task draft
Audit this product page for the target market and deliver customer-journey issues, SEO/GEO findings, localized section copy, recommended fixes, and implementation notes.
Output
Audit report + action list
How to choose a task type
Choose the specialist workflow that matches the storefront outcome. Use development for implementation, SEO/GEO for search visibility, localization for market-ready content, research for evidence, and operations for recurring reports and follow-up.
Use for keyword intent, AI search visibility, structure, and indexing issues.
Use for market-aware product pages, campaigns, email, social content, support copy, and FAQs.
04
How to upload files
Attach market briefs, product specifications, storefront screenshots, analytics exports, customer research, existing copy, brand guidelines, code context, or operating notes, then explain how each file should be used.
Context files
- Target market and product brief
- Existing storefront copy and brand guidelines
- Search, storefront, campaign, or customer data export
How to let Smaug write code
Describe the storefront stack, feature, customer flow, expected behavior, constraints, acceptance criteria, and approval boundary. Include repository context, errors, and file paths when available.
Improve this product-page FAQ for mobile. Follow the existing design system, preserve structured data, keep content visible without JavaScript, and report the files and checks used.
How to let Smaug do SEO/GEO analysis
Give SmaugBrain the storefront URL, target country and language, product categories, customer questions, search data, competing pages, and publishing capacity. Ask for intent, content gaps, internal links, structured data, AI-answer readiness, and implementation priorities.
Search intent
Content gaps
AI answer readiness
Next actions
07
How to view execution results
Open the task result to review the summary, files, recommendations, and next steps. If the result needs adjustment, continue the same task with clearer feedback instead of starting from zero.
Result package
Summary, deliverables, decisions, and follow-up tasks
How to manage plans and usage
Use the plan and account pages to review your current package, quota, orders, and renewal status. Upgrade when task volume, agent count, or team collaboration needs increase.
Plan management
View plans and pricing
Frequently asked questions
No. Start with the market, product, storefront, business goal, and expected result. Technical details improve development tasks, but SmaugBrain can help identify missing requirements before execution.
Include the target market, product, storefront URL, goal, customer context, constraints, target language, source files, approval boundaries, and delivery format.
Yes. Continue from the same task and explain what should change, what was missing, or which direction should be prioritized.
Support
Contact support
Contact support
If you are blocked, send your account email, task name, expected result, and a short description of the issue so support can locate the right workspace context.