# Nexamas UI Recipes

Recipes are task-oriented usage pages for developers who want a direct answer to a practical question:

> I want this UI or behavior. Which Nexamas UI public API should I use?

Recipes are separate from deep inventories and historical proof notes. They must be short, public-API-only, and suitable for copying into a normal consumer application.

## Recipe Rules

- Use only public consumer APIs.
- Prefer `MASApplication`, `MASApplicationWindow`, and `window.Controls.Add*` factory routes.
- Prefer `LayoutPage`, `LayoutApplicationSurface`, `MASSize`, and `MASLayoutSpacing` over manual bounds.
- Do not use `Friend`, internal, proof-only, test-only, or repository-only helpers.
- Every recipe must name the API it uses.
- Every recipe should be small enough to understand and adapt independently.
- Verification wording must match the evidence attached to that specific recipe.

## Planned Recipe Groups

| Group | Purpose | Initial status |
|---|---|---|
| [Application](application.md) | Create and attach a Nexamas UI window. | Initial recipes added. |
| [Layout](layout.md) | Build simple pages, grids, action groups, and app surfaces. | Initial recipes added. |
| [Buttons and actions](buttons.md) | Create primary page actions, grouped actions, and split actions. | Initial recipes added. |
| [Text and feedback](feedback.md) | Banners, validation messages, progress, and empty states. | Initial recipes added. |
| [Inputs](inputs.md) | TextBox, ComboBox, SearchTextBox, and Slider. | Initial recipes added. |
| [Data](datagrid.md) | DataGrid, DataView, filtering, large-data boundaries. | Initial recipes added. |
| [Surfaces and containers](surfaces.md) | GroupBox, Expander, Accordion, TileBox, and Card hosting boundary. | Initial recipes added. |
| [Navigation](navigation.md) | Tabs, Breadcrumb, Pagination, and CommandBar. | Initial recipes added. |
| [Theme and surfaces](theme-surface.md) | Select registered themes and apply public surface materials. | Initial recipes added. |
| [Localization and RTL](localization-rtl.md) | Attach the public RTL/localization page route. | Initial recipes added. |
| [Output](output.md) | Use supported Output routes and document unsupported routes honestly. | Initial recipes added. |
| Quality and verification | Use public Render Verification routes when appropriate. | Existing examples available. |
| [Product controls](product-controls.md) | TreeGrid, KanbanBoard, PivotTable, AgendaView, DashboardGrid, MasterDetailView, AppLayout, and SplitView. | Initial recipes added. |

## Current Example Sources

Existing source-verified examples live under [../examples/](../examples/README.md). The recipe phase should migrate or cross-link the useful examples into task-oriented pages without duplicating code carelessly.

## Verification boundary

Recipe correctness is audited against the current source and repository-owned consumer samples. All **41 / 41** governed recipes are Build-verified; all five Windows runtime smokes passed, and the Render Verification snapshot smoke passed separately. See the [build-verification ledger](build-verification-ledger.md), [snippet verification inventory](../_inventory/documentation-snippet-verification.md), and [Windows PASS proof](../quality-proof/documentation-recipes-windows-pass-2026-07-10.md). Maintainer-only execution details and Showcase planning remain outside the beginner path.