This document covers Google Antigravity's comprehensive design and SEO requirements for web application development. These mandates enforce premium visual quality and search engine optimization standards that must be automatically applied to every web application created by the system.
For information about the underlying technology stack and framework choices, see Web Application Development Standards. For the overall system architecture, see System Architecture and Identity.
Antigravity treats design aesthetics as a critical, non-negotiable requirement with explicit failure conditions. The system includes the following enforcement statement:
Google/Antigravity/Fast Prompt.txt33
This is one of the strongest mandates in the entire system prompt, comparable to Qoder's $100M penalties for tool misuse. The requirement is restated at the end of the web development section:
Google/Antigravity/Fast Prompt.txt73
Antigravity requires that users must be "wowed at first glance" by the design. The system mandates specific modern design techniques:
| Design Element | Required Features |
|---|---|
| Color Schemes | Vibrant colors, dark modes, HSL-tailored palettes |
| Visual Effects | Glassmorphism, smooth gradients, subtle animations |
| Typography | Google Fonts (Inter, Roboto, Outfit) instead of browser defaults |
| Interactivity | Hover effects, micro-animations, responsive elements |
| Overall Quality | Premium, state-of-the-art designs (not MVPs) |
Google/Antigravity/Fast Prompt.txt33-41
Sources: Google/Antigravity/Fast Prompt.txt32-42
The system explicitly prohibits generic colors and mandates curated palettes:
Prohibited:
Required:
Google/Antigravity/Fast Prompt.txt35
Typography must use modern fonts instead of browser defaults:
Recommended Google Fonts:
InterRobotoOutfitThese fonts must be imported from Google Fonts rather than relying on system fonts or browser defaults.
Google/Antigravity/Fast Prompt.txt36
The system emphasizes creating interfaces that feel "responsive and alive":
Required Interactive Elements:
The justification provided: "An interface that feels responsive and alive encourages interaction. Achieve this with hover effects and interactive elements. Micro-animations, in particular, are highly effective for improving user engagement."
Google/Antigravity/Fast Prompt.txt39
Antigravity explicitly rejects minimum viable product (MVP) approaches:
Google/Antigravity/Fast Prompt.txt40
This aligns with the "state of the art" requirement, demanding production-quality designs from the initial implementation.
When images are needed, the system prohibits placeholder images and mandates using the generate_image tool:
Google/Antigravity/Fast Prompt.txt41
This integrates with the generate_image tool defined at Google/Antigravity/Fast Prompt.txt382-392
Sources: Google/Antigravity/Fast Prompt.txt40-41
SEO best practices must be "automatically implemented on every page" without requiring user requests. This is a non-optional, systemic requirement.
Google/Antigravity/Fast Prompt.txt66
Sources: Google/Antigravity/Fast Prompt.txt65-72
Requirement: Include proper, descriptive title tags for each page.
Implementation: Each HTML page must have a <title> element in the <head> section with descriptive content specific to that page's purpose.
Example Pattern:
Google/Antigravity/Fast Prompt.txt67
Requirement: Add compelling meta descriptions that accurately summarize page content.
Implementation: Include <meta name="description"> tags with accurate, engaging summaries of page content.
Example Pattern:
Google/Antigravity/Fast Prompt.txt68
Requirements:
<h1> per page<h1> → <h2> → <h3>, etc.)Implementation: Each page must have exactly one <h1> element representing the primary page topic, with subsequent headings following semantic hierarchy without skipping levels.
Example Structure:
Google/Antigravity/Fast Prompt.txt69
Requirement: Use appropriate HTML5 semantic elements.
Implementation: Replace generic <div> and <span> elements with semantic alternatives where appropriate:
| Element | Purpose |
|---|---|
<header> | Page or section header |
<nav> | Navigation links |
<main> | Main content area |
<article> | Self-contained content |
<section> | Thematic grouping |
<aside> | Tangential content |
<footer> | Page or section footer |
Google/Antigravity/Fast Prompt.txt70
Requirement: Ensure all interactive elements have unique, descriptive IDs.
Purpose: This serves two functions:
browser_subagent toolImplementation Pattern:
Note the dual purpose stated in the requirement: "for browser testing" - this directly integrates with Antigravity's browser_subagent tool defined at Google/Antigravity/Fast Prompt.txt326-336
Google/Antigravity/Fast Prompt.txt71
Requirement: Ensure fast page load times through optimization.
Implementation Considerations:
This requirement is stated broadly, leaving specific optimization techniques to implementation judgment.
Google/Antigravity/Fast Prompt.txt72
Sources: Google/Antigravity/Fast Prompt.txt65-72
Antigravity defines a systematic five-phase approach for building web applications that ensures design quality and SEO compliance from the start.
Sources: Google/Antigravity/Fast Prompt.txt43-63
Objectives:
This phase emphasizes research and conceptualization before implementation begins.
Google/Antigravity/Fast Prompt.txt45-48
Objectives:
index.cssKey Principle: The design system must be established before components are created. This file (index.css) serves as the single source of truth for:
Google/Antigravity/Fast Prompt.txt49-52
Objectives:
Critical Constraint: Components must use the design system defined in index.css. Ad-hoc inline styles or utility classes are prohibited. This ensures consistency and maintainability.
Google/Antigravity/Fast Prompt.txt53-56
Objectives:
This phase integrates components into complete pages with routing logic.
Google/Antigravity/Fast Prompt.txt57-60
Objectives:
This final phase applies both the design aesthetics review (ensuring WOW factor) and the SEO best practices (performance optimization).
Google/Antigravity/Fast Prompt.txt61-64
Sources: Google/Antigravity/Fast Prompt.txt43-64
The workflow requires creating/modifying index.css as the foundation file. This is accomplished using:
write_to_file tool for creating new index.css files Google/Antigravity/Fast Prompt.txt593-609replace_file_content tool for modifying existing design systems Google/Antigravity/Fast Prompt.txt462-488multi_replace_file_content tool for multiple simultaneous CSS updates Google/Antigravity/Fast Prompt.txt438-460The mandate to avoid placeholders integrates with the generate_image tool:
Tool Definition: Google/Antigravity/Fast Prompt.txt382-392
Parameters:
ImageName: Descriptive name (lowercase with underscores, max 3 words)Prompt: Text description for generationImagePaths (optional): Existing images to edit or combineUsage Pattern:
generate_image(
ImageName: "hero_section_background",
Prompt: "Modern abstract gradient background with vibrant colors..."
)
The SEO requirement for unique IDs integrates with the browser_subagent tool:
Tool Definition: Google/Antigravity/Fast Prompt.txt326-336
Purpose: The browser subagent can interact with elements by their IDs during automated testing, which is why descriptive, unique IDs are mandatory.
Example Task:
browser_subagent(
TaskName: "Testing Form Submission",
Task: "Click the button with id 'submit-form-btn' and verify success message appears",
RecordingName: "form_submission_test"
)
The planning phase mentions "draw inspiration from modern, beautiful, and dynamic web designs". This can leverage:
Tool: search_web Google/Antigravity/Fast Prompt.txt544-549
Usage Pattern:
search_web(
query: "modern web design trends 2024 glassmorphism dark mode"
)
After assembly, the system can validate HTML structure using:
view_file to review HTML output Google/Antigravity/Fast Prompt.txt571-581grep_search to find heading structure issues Google/Antigravity/Fast Prompt.txt394-410Example Search for Multiple H1s:
grep_search(
Query: "<h1",
SearchPath: "/path/to/html/file.html",
MatchPerLine: true
)
Sources: Google/Antigravity/Fast Prompt.txt326-336 Google/Antigravity/Fast Prompt.txt382-392 Google/Antigravity/Fast Prompt.txt394-410 Google/Antigravity/Fast Prompt.txt438-460 Google/Antigravity/Fast Prompt.txt462-488 Google/Antigravity/Fast Prompt.txt544-549 Google/Antigravity/Fast Prompt.txt571-581 Google/Antigravity/Fast Prompt.txt593-609
| System | Design Mandate Level | Specific Requirements |
|---|---|---|
| Antigravity | UNACCEPTABLE to fail | Rich aesthetics, premium designs, WOW factor |
| v0 | Strict design system | 3-5 color limit, semantic tokens, Tailwind CSS v4 |
| Same.dev | Responsive standards | shadcn/ui customization, color palette restrictions |
| Lovable | Not explicitly stated | Tool-based approach without aesthetic mandates |
Antigravity is unique in declaring design failure as "UNACCEPTABLE" with explicit language comparable to critical security violations in other systems.
| System | SEO Approach | Automation Level |
|---|---|---|
| Antigravity | Automatic on every page | Mandatory |
| v0 | Not explicitly documented | Implicit through framework |
| Same.dev | Not explicitly documented | Implicit through framework |
| Windsurf | Not explicitly documented | Developer responsibility |
Antigravity is the only system with explicit, mandatory SEO requirements in the system prompt.
Sources: Google/Antigravity/Fast Prompt.txt32-73
Google Antigravity enforces the most comprehensive and strict design aesthetics and SEO standards among documented AI coding assistants. The system treats visual quality as a critical requirement with explicit failure conditions and mandates automatic SEO implementation on every page. This approach reflects a philosophy that production-quality, premium designs should be the default output, not an optional enhancement.
The five-phase implementation workflow ensures design systems are established before component creation, maintaining consistency through predefined styles in index.css. The integration with tools like generate_image and browser_subagent creates a cohesive system where design quality and testability are built into the development process from the start.
Sources: Google/Antigravity/Fast Prompt.txt19-73 Google/Antigravity/Fast Prompt.txt326-609
Refresh this wiki