Use the assistant to inspect and change breakpoints, fonts, SEO, domains, analytics, and design tokens, then choose staging or production explicitly and review the destination before any deployment runs.
Where: AI assistant → describe the setting/deploy — Ask the AI to change settings or deploy
Key ideas
- Settings route: The router directs configuration requests to tools that read and update project settings and shared design tokens.
- Shared values have reach: Changing a breakpoint, font, or token can affect many pages and components, so scope and current values should be reviewed first.
- Two deployment tools: Deploy to staging and Deploy to production are separate explicit actions with different consequences.
Steps
- Open the website assistant and name the exact setting and desired scope.
- Ask it to inspect current tokens/settings before changing shared values.
- Review the proposed breakpoint, font, SEO, domain, analytics, or token change.
- Apply the setting and preview affected pages and responsive widths.
- For review, explicitly request staging and verify the returned destination.
- Resolve errors and obtain approval before explicitly requesting production.
- Open the delivered site and check metadata, analytics, domain, navigation, and assets.
Supported work
- Breakpoints and fonts
- SEO metadata
- Custom domain and analytics
- Read/write design tokens
- Staging deployment
- Production deployment
Tips
- Use staging for stakeholder review.
- Name a specific token rather than asking for a vague global restyle.
Limitations and important notes
- DNS propagation and third-party analytics are external.
- A successful deployment does not validate every page or integration.
Troubleshooting
The assistant changed too much.
Restore or reverse the shared setting, then reissue the request with an exact page, breakpoint, or token scope.