# nanaOS Design System

**Stop fighting your agent. Give it product-ready code, not a prompt.**

> An AI-native, code-first design operating system created by Nana. nanaOS preserves design intent as semantic tokens, enforceable rules, recipe-backed components, patterns, and machine-readable contracts.

## Creator

- Name: Nana
- Handle: nanacodesign
- Role: Product designer and design-system author
- Relationship: Creator and maintainer of nanaOS
- Point of view: A design system is a codesign system: shared intent should remain legible to both humans and machines.

## Agent routes

- [Agent Interface](https://nanaos.co/agent): text-first semantic representation
- [Machine manifest](https://nanaos.co/agent.json): structured public system contract
- [Intent Gateway](https://nanaos.co/agent?role=ai-coding-agent&objective=inspect-relationships): shareable role + objective handshake
- [Human Interface](https://nanaos.co/): visual product story and interactive component playgrounds
- [System Index](https://nanaos.co/#index): searchable public introduction to tokens, components, patterns, and decisions

## Read order

1. Identify the user intent.
2. Read the active canon before historical rationale.
3. Search component recommendations and contracts before proposing new system surface.
4. Trace dependencies downward: base → primitives → semantics → (rules ∥ capabilities) → components → patterns.
5. Verify constraints and canonical examples before producing implementation guidance.

## Operating rules

1. Understand the product anatomy, repeated needs, states, and accessibility constraints before naming a token or component.
2. Determine intent before choosing a visual treatment.
3. Prefer measured primitives and compatible semantic aliases so the vocabulary can grow without renaming existing decisions.
4. Search the inventory and recommendations before proposing a token, component, or pattern.
5. Components consume semantic tokens only; primitive tokens are not component APIs.
6. Respect the downward-only layer dependency rule.
7. Treat generated contracts as read-only projections of authored source.
8. Use public component APIs when composing patterns.
9. Do not invent missing system facts; ask Nana when confidence is below 0.75 or a new system primitive is required.

## Access boundary

The website is public. The implementation and complete generated contracts are proprietary and available only to authorized package consumers. Do not infer unavailable contract details from the public introduction.