A standalone CSS library with 920 classes — optimized to work with the ANTSAND Databoard compiler, where every deployed site ships with these styles by default.
Three Ways to Use
ANTSAND Styles works at every level — from a standalone CSS drop-in, to the styling layer of a headless data backend, to the fully compiled website pipeline.
📦
Standalone CSS
Drop one CSS file into any HTML project. No ANTSAND, no build tools, no backend required.
✓ CDN or local include
✓ 24 component types, 200+ utilities
✓ 4 themes, 40+ fonts, zero deps
✓ Any framework: React, Vue, plain HTML
Best for: static sites, prototypes, non-ANTSAND projects
🔗
Headless + ANTSAND Data
Build your own custom frontend, but use ANTSAND Databoard as a headless CMS for all your data management. Include the styles library in your app for visual consistency.
✓ Your app, your framework, your hosting
✓ ANTSAND manages content & data via API
✓ Include styles via CDN in your frontend
✓ Same class system across all your apps
Best for: custom apps using ANTSAND as a data backend
⚡
Full Compiler (Default)
ANTSAND compiles and deploys your entire site. Styles are auto-attached — you just assign CSS classes to Databoard fields. AI agents style through the REST API.
✓ Styles auto-included on deploy
✓ Assign classes via API or control panel
✓ Sass scanner = zero-waste CSS
✓ Inspect → Patch → Compile → Deploy
Default for: ANTSAND-deployed production sites
Already using ANTSAND? If Databoard compiles your site, antsand-v2.css is already in every page's <head> — no install needed.
If you use ANTSAND as a headless CMS with your own frontend, include the library via CDN so your app shares the same design system.
Standalone & Headless Quick Start
For standalone projects or custom frontends using ANTSAND as a headless CMS, include the library via CDN:
When you deploy a site through ANTSAND, the styles library is already in the rendered HTML. You style by assigning CSS class names to Databoard fields:
Databoard field → CSS class assignment (via API or control panel)
How it works: The ANTSAND compiler reads a Databoard JSON object containing your content + CSS class assignments. It resolves Volt templates, applies the Header/Body/Footer section contract, compiles Sass, and deploys a production site. The antsand-v2.css stylesheet is auto-included — no manual linking needed.
AI agents use a REST API to style ANTSAND sites programmatically:
Agent loop (curl)
# 1. Inspect current state
curl -X GET /api/v1/databoards/{BOARD_ID} -H "Authorization: Bearer TOKEN"
# 2. Patch CSS classes on fields
curl -X POST /api/v1/databoards/{BOARD_ID}/patch \
-H "Authorization: Bearer TOKEN" \
-d '{ "patch_delta": { "datalist.0.css.section.container": "antsand-section theme-dark-corporate" } }'
# 3. Compile utilities (generates only used CSS)
curl -X POST /api/v1/databoards/{BOARD_ID}/utilities/compile -H "Authorization: Bearer TOKEN"
# 4. Deploy
curl -X POST /api/v1/databoards/{BOARD_ID}/deploy -H "Authorization: Bearer TOKEN"
Rule: Buttons are always antsand-btn — never px-4 py-2 bg-blue. Semantic wins for components. Utilities complement, not replace.
For AI Agents
Copy the getting-started prompt to give your AI agent full context on using ANTSAND Styles — both standalone and with the Databoard compiler.
🤖 Agent Getting Started Prompt — standalone + ANTSAND integration
ANTSAND STYLES v2 — GETTING STARTED PROMPT FOR AI AGENTS
## What is ANTSAND Styles?
A two-tier CSS framework: semantic component classes (Tier 1) + utility classes (Tier 2).
920 classes, 24 component types, 4 themes, 40+ self-hosted fonts, 128KB compiled.
Zero dependencies, WCAG accessible, responsive (breakpoints: sm 640px, md 768px, lg 1024px, xl 1280px).
## Three Ways to Use
### Path 1: Standalone CSS (any HTML project, no ANTSAND)
Include via CDN:
<link rel="stylesheet" href="https://styles.antsand.com/css/antsand-v2/antsand.css">
Or download: https://github.com/antsand/styles/raw/master/archive/styles.zip
Then use classes directly in your HTML:
<button class="antsand-btn antsand-btn-primary">Click Me</button>
<div class="antsand-grid md:grid-cols-3 gap-6">
<div class="antsand-card shadow">Content</div>
</div>
<section class="antsand-section theme-dark-corporate">...</section>
### Path 2: Headless ANTSAND (your own frontend + ANTSAND data backend)
Use ANTSAND Databoard as a headless CMS for content and data management,
but build your own custom frontend (React, Vue, Next.js, plain HTML — anything).
Include the styles library via CDN in your app so your frontend uses the same
design system as ANTSAND-deployed sites.
This gives you:
- Full control over your app architecture and hosting
- ANTSAND manages all your content/data via its API
- Same CSS classes, themes, and components as the full compiler path
- Visual consistency if you also have ANTSAND-compiled sites
### Path 3: Full ANTSAND Compiler (default — styles auto-attached)
When a site is deployed through the ANTSAND Databoard compiler, antsand-v2.css is
automatically included in every page. You do NOT link it manually.
Instead, assign CSS classes to Databoard fields via the control panel or REST API:
section.container → "antsand-section theme-warm-editorial"
data.container → "antsand-grid md:grid-cols-3 gap-6"
data.sub_container → "antsand-card shadow transition-all hover:-translate-y-1"
data.h3 → "line-clamp-2 font-semibold md:text-xl"
data.p → "line-clamp-3 opacity-75"
data.cta → "antsand-btn antsand-btn-primary antsand-btn-sm"
data.img_container → "aspect-video overflow-hidden"
data.img → "object-cover rounded-lg"
The compiler reads these assignments, resolves Volt templates, applies the
Header/Body/Footer section contract, compiles Sass, and deploys the production site.
## Agent Workflow for Databoard Sites
1. GET /api/v1/me → verify auth
2. GET /api/v1/databoards → list boards
3. GET /api/v1/databoards/{id} → inspect current CSS assignments
4. POST /api/v1/databoards/{id}/patch → apply class changes via patch_delta
5. POST /api/v1/databoards/{id}/utilities/compile → generate only the CSS used
6. POST /api/v1/databoards/{id}/deploy → build + deploy live site
7. GET http://site-url/ → smoke test (expect 200)
All requests use: Authorization: Bearer YOUR_API_KEY, Content-Type: application/json.
This loop is idempotent — patches overwrite, they don't append. Safe to repeat.
## Key Rules
- Buttons are ALWAYS Tier 1: antsand-btn antsand-btn-primary (never px-4 py-2 bg-blue)
- Themes activate via one class on section.container: theme-dark-corporate, theme-warm-editorial, theme-bold-gradient, theme-minimal-clean
- Every section follows Header/Body/Footer contract — same HTML structure, CSS alone controls layout
- Grid layouts: antsand-grid + md:grid-cols-{1-6} + gap-{1-12}
- Responsive prefixes: sm: md: lg: xl: (mobile-first)
## Reference Pages
- Full class reference: https://styles.antsand.com/
- Components: https://styles.antsand.com/components
- Utilities: https://styles.antsand.com/utilities
- Font library: https://styles.antsand.com/utilities/fonts
- API reference: https://styles.antsand.com/docs/apireference
- Agent quickstart: https://styles.antsand.com/docs/agentquickstart
- Databoard utilities: https://styles.antsand.com/utilities/databoard