Astra
corporate Visual styleAn orbital diagram and clear operational panels
Reference year: 2026
Compare this themeBest for
Dashboard, Developer tools, SaaS
Less suitable for
- Long reading pages or playful shopping experiences that need a light visual tone.
Live component preview
Try the sample controls. daisyUI uses compiled library classes; shadcn/ui uses React components from the New York registry. The three example layouts demonstrate styling with the selected tokens. All content is demo data.
Color Palette
Typography
Key Characteristics
- Deep navy page background and opaque data panels
- Space Grotesk headings at 32-58px with compact IBM Plex Sans body text
- One orbital diagram as the main visual element
- Cyan action color, lavender secondary color, and amber attention color
- Thin panel borders, small corners, and no card shadows
- Left-aligned headings and unequal panel widths for information hierarchy
Tags
Astra is a space-themed style for dashboards and developer tools. A single orbital diagram establishes the visual identity. The rest of the page uses readable, opaque panels and clear controls.
Layout
Place the orbital diagram beside a left-aligned heading. Give the main data panel more width than supporting panels. Use a compact navigation row or sidebar when the content needs it. Stack panels on phones and keep the reading order unchanged.
Color and type
Use cyan for primary actions and lavender for secondary elements. Reserve amber for attention states. Include text with status colors. Use Space Grotesk for headings and IBM Plex Sans for labels, forms, and tables.
Motion
Orbital motion is optional. Animate only the decorative diagram. Keep text and controls stationary. Respect reduced motion and provide a static diagram when animation is disabled.
Export style
Choose a library mapping or use the CSS variables in your own components. JSON includes the same mapping. Load the listed fonts separately.
:root {
--tx-surface-bg: #080F1C;
--tx-font-heading: "Space Grotesk", sans-serif;
--tx-font-body: "IBM Plex Sans", sans-serif;
--tx-surface-bg-image: radial-gradient(circle at 82% 20%, rgba(115,223,245,0.06), transparent 32%);
--tx-card-bg: #111C2E;
--tx-card-border: #34465F;
--tx-card-border-width: 1px;
--tx-card-radius: 0.375rem;
--tx-card-shadow: none;
--tx-card-backdrop-blur: 0px;
--tx-card-border-hover: #73DFF5;
--tx-card-shadow-hover: none;
--tx-font-heading-weight: 600;
--tx-font-body-weight: 400;
--tx-text-muted: #B3C4DB;
--tx-text-subtle: #94A9C4;
--tx-link-color: #73DFF5;
--tx-button-radius: 0.375rem;
--tx-input-bg: #080F1C;
--tx-input-border: #526985;
--tx-text: #ECF3FF;
--tx-primary: #73DFF5;
--tx-secondary: #A0ABFF;
--tx-accent: #F5BC68;
--tx-media-filter: none;
}
Prompt Builder
Choose your project, UI library, and output. Prompts, documents, and exports use the same resolved theme values.
Use your own components with the exported CSS variables.
Astra
Live component preview
Try the sample controls. daisyUI uses compiled library classes; shadcn/ui uses React components from the New York registry. The three example layouts demonstrate styling with the selected tokens. All content is demo data.
Copy this prompt into your coding assistant. The task mode applies to the UI prompt.
Generated prompt
You are building a web application using Next.js with Tailwind.
Read existing project instructions and reuse installed components where available.
## Project
Project brief: Not specified
Target users: Not specified
Page purpose: Dashboard
Framework: Next.js
CSS approach: Tailwind
UI library: Custom / no library
Tone: Professional
## Visual direction
Base theme: Astra (visual-style)
- Deep navy page background and opaque data panels
- Space Grotesk headings at 32-58px with compact IBM Plex Sans body text
- One orbital diagram as the main visual element
- Cyan action color, lavender secondary color, and amber attention color
- Thin panel borders, small corners, and no card shadows
- Left-aligned headings and unequal panel widths for information hierarchy
## Resolved style
Use this final token set. It already includes the selected layers. These values take precedence over conflicting base characteristics.
Color palette: primary #73DFF5, secondary #A0ABFF, accent #F5BC68, background #080F1C, text #ECF3FF
Typography: Space Grotesk for headings, IBM Plex Sans for body text
Load the declared fonts with the required weights. Use system fallbacks when a font is unavailable.
```css
:root {
--tx-surface-bg: #080F1C;
--tx-font-heading: "Space Grotesk", sans-serif;
--tx-font-body: "IBM Plex Sans", sans-serif;
--tx-surface-bg-image: radial-gradient(circle at 82% 20%, rgba(115,223,245,0.06), transparent 32%);
--tx-card-bg: #111C2E;
--tx-card-border: #34465F;
--tx-card-border-width: 1px;
--tx-card-radius: 0.375rem;
--tx-card-shadow: none;
--tx-card-backdrop-blur: 0px;
--tx-card-border-hover: #73DFF5;
--tx-card-shadow-hover: none;
--tx-font-heading-weight: 600;
--tx-font-body-weight: 400;
--tx-text-muted: #B3C4DB;
--tx-text-subtle: #94A9C4;
--tx-link-color: #73DFF5;
--tx-button-radius: 0.375rem;
--tx-input-bg: #080F1C;
--tx-input-border: #526985;
--tx-text: #ECF3FF;
--tx-primary: #73DFF5;
--tx-secondary: #A0ABFF;
--tx-accent: #F5BC68;
--tx-media-filter: none;
}
```
Use the CSS variables in your own components. Apply the heading and body font variables to their respective elements.
## Layout
- Use left-aligned content and a consistent 8px spacing scale. Place one orbital diagram beside the main heading. Keep data panels below it.
- Use a wider primary data panel beside narrower supporting panels. Collapse panels and the diagram to one column on narrow screens.
## Interaction
- Use cyan borders for selected controls and amber for attention states. Include a text label with each status.
- Keep orbital motion optional and limited to the decorative diagram. Stop it when reduced motion is requested. Keep data and controls stationary.
## Suitability notes
Use these limitations to assess the chosen page purpose. Explain any mismatch before applying an unsuitable treatment.
- Astra: Long reading pages or playful shopping experiences that need a light visual tone.
## Components
Generate the following components in this style:
- Sidebar
- Tables
- Forms
## Quality requirements
Choose section order and visual emphasis from the real content and page purpose. Add only sections needed for the task.
Use supplied content. Label sample data. Do not invent testimonials, customer logos, statistics, or compliance claims.
Every interactive control must perform its declared action or be clearly labeled as a demo.
Include loading, empty, error, success, disabled, and focus states where applicable.
Use semantic HTML, visible keyboard focus, readable text contrast, and labeled form fields.
Ensure responsive design (mobile-first). Preserve reading order and avoid horizontal page overflow.
Respect prefers-reduced-motion. Keep essential content visible when animations are disabled.
## Verification
Check representative desktop and mobile widths, keyboard interaction, and relevant component states. Run available project checks and report what was actually verified.
Use Tailwind utility classes with the declared tokens.
Product context is incomplete. Label assumptions and treat the result as a draft until the missing context is supplied.