sena-nana

lilia-app-boundary

Ownership rules for deciding whether a LiliaCode desktop change belongs in apps/desktop, NanaUI, or lilia-contracts. Use when a change touches shell, titlebar, sidebar, settings, menus, theme, window state, layout primitives, platform APIs, or cross-end data.

lilia-app-coding

Coding workflow for the LiliaCode native desktop app. Use when implementing features, fixing bugs, refactoring, adding UI surfaces or runtime commands, changing cross-end data contracts, touching apps/desktop Rust code, NanaUI consumers, or crates/lilia-contracts.

Web & Frontend Listed

lilia-app-design

Design and interaction standards for the LiliaCode native desktop app. Use when designing, implementing, reviewing, or fixing pages, panels, cards, empty/loading/error states, dialogs, menus, layout composition, borders, visual hierarchy, or any UI behavior in apps/desktop rendered with NanaUI (Rust retained tree, WGPU).

lilia-agent-debug

Agent debugging workflow for the LiliaCode native desktop. Use when adding, changing, validating, or reviewing stable target IDs, the LILIA_AGENT_DEBUG TCP protocol, debug-only instrumentation, or cargo xtask agent-debug harness behavior.

lilia-app-validation

Validation strategy for LiliaCode native desktop changes. Use when choosing or reporting checks after app code, contracts, UI, platform, build config, documentation, or dependency pins change.

Code & Development Listed

lilia-app-git

Git workflow for LiliaCode desktop changes. Use when staging, committing, pushing, merging, syncing dependencies, reviewing diffs before committing, or preserving user and other-agent changes.