Agent Rules

This file stays thin on purpose.

Core rules: - Prefer the repo docs over memory when making structural decisions. - Keep the library core UI-agnostic. - Keep editor-only concerns out of the core model. - Add new guidance by reference, not by growing this file into a handbook.

Reference docs: - Project Structure - Plan Phases - Type Model - Skills Prospect

Enabled KMP Agent Skills: - Skill Orchestrator (Start Here) - Layer 0 (Foundation): Scaffold, DI, Flavors, CI, Audit - Layer 1 (Infra): Auth, MongoDB, Kotlin RPC, Network, SQLDelight, XCFramework/SPM - Layer 2 (Patterns): Expect/Actual, Repository - Layer 3 (Feature): Navigation, Resources, MVI - Layer 4 (UI): Design System, Extended UI, Slot API, Hoisting, State Containers, Graphics/Modifiers

Working rule: - If a decision changes architecture, add or update a referenced doc first, then implement code. - Consult the Skill Orchestrator for any new KMP feature or project structural change.