halftonedesignsystem.com valid
Halftone Design System
One brand on phone and web: Expo and Next.js kits your coding agent builds from.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T04:52:12.310Z. Cached copy · Source on halftonedesignsystem.com
# Halftone Design System
> One brand on phone and web: Expo and Next.js kits your coding agent builds from.
Two prototype kits on one set of design tokens: a native kit (Expo, React Native, NativeWind,
react-native-reusables) and a web kit (Next.js, Tailwind 4, shadcn/ui). Each kit lists the only components a
prototype may use. Start with the install guide.
## This site
- [Install guide for agents](https://halftonedesignsystem.com/install.md): pick a kit and a path, then the rules
- [Everything in one file](https://halftonedesignsystem.com/llms-full.txt)
- [shadcn registry for Expo + react-native-reusables (@halftone-native)](https://halftonedesignsystem.com/r/native/registry.json)
- [shadcn registry for Next.js + shadcn/ui (@halftone-web)](https://halftonedesignsystem.com/r/web/registry.json)
- [Studio](https://halftonedesignsystem.com/studio/): people make and keep design systems here (saved in their browser). They hand you an `ht-` theme code or a `.halftone.json`; apply either with `npx halftone-tokens theme apply <code|file>` (the kits' apply-theme skill)
## Native kit
> A brand-agnostic Expo + React Native prototype kit (Expo Router, NativeWind, react-native-reusables).
> Screens are composed ONLY from the components listed below; nothing else exists.
Generated by `npm run registry:build` from registry/components.ts — do not edit by hand.
### Read first
- [AGENTS.md](https://github.com/itsHendri/halftone/blob/main/apps/mobile/AGENTS.md): stack, commands, how to build a prototype, gotchas
- [DESIGN_SYSTEM.md](https://github.com/itsHendri/halftone/blob/main/apps/mobile/DESIGN_SYSTEM.md): tokens, the component registry, patterns, anti-patterns, the hallucination guard
- [DESIGN.md](https://github.com/itsHendri/halftone/blob/main/apps/mobile/DESIGN.md): the design tokens in the DESIGN.md format
### Rules
- Use only the components below, by their exact names. Missing something: stop and say so (the `add-component` skill adds it properly).
- Style with semantic Tailwind classes only. No hex, no Tailwind palette colours, no StyleSheet colours.
- `npm run lint` enforces these rules (`halftone/*`): fix every error before calling a screen done.
- Text through `<Text variant>` from components/ui/text; icons through `<Icon as={…} />` (lucide).
- Check every screen in light and dark.
### Components
#### Actions
- [Button](https://github.com/itsHendri/halftone/blob/main/apps/mobile/components/ui/button.tsx): `variant` default/secondary/outline/ghost/link/destructive · `size` sm/default/lg/icon · children are `<Text>`/`<Icon>` — `<Button variant? size? disabled?><Text>…</Text></Button>`
- [Toggle](https://github.com/itsHendri/halftone/blob/main/apps/mobile/components/ui/toggle.tsx): pressed two-state button — `<Toggle pressed onPressedChange><ToggleIcon as={…} /></Toggle>`
- [ToggleGroup](https://github.com/itsHendri/halftone/blob/main/apps/mobile/components/ui/toggle-group.tsx): `type` single/multiple — `<ToggleGroup type="single|multiple"
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| once-ui.com | Once UI | transactional Design Developer tools | US | 51 | ✓ | ||
| supernova.io | Supernova.io | documentation AI and machine learning Design +1 | US | 51 | ✓ | ||
| control-ui.dev | Control UI | documentation Developer tools Design | US | 45 | ✓ | ✓ | |
| expo.dev | Expo documentation | documentation Developer tools | — | 68 | ✓ | ✓ | |
| meshdesignsystem.com | Mesh Design System | documentation Design Documentation and reference | — | 46 | ✓ | ||
| carbondesignsystem.com | Carbon Design System | documentation Design Documentation and reference +1 | — | 59 | ✓ | ||
| weaverse.io | Weaverse | documentation Ecommerce Developer tools | US | 51 | ✓ | ✓ | |
| gntik-ui.vercel.app | gntik-ui | informational Design | US | 45 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=halftonedesignsystem.com · GET /v1/domain/halftonedesignsystem.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage halftonedesignsystem.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for halftonedesignsystem.com:
1. POST https://agentwebmap.com/v1/sites/halftonedesignsystem.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://halftonedesignsystem.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/halftonedesignsystem.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/halftonedesignsystem.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.