What problem does it solve? Developers often struggle to decide where different kinds of application data should live, leading to misused storage layers such as putting OAuth tokens in plain settings or domain data in ephemeral state. This Skill provides clear rules and code patterns for choosing the correct storage layer in an agent-native app backed by a single SQL database. ## Core Features & Use Cases - Four storage layers documented: Settings for persistent key-value config, Application State for ephemeral session-scoped UI state with SSE sync, Drizzle tables for structured domain data, and an encrypted OAuth token store for credentials. - Decision table: Maps data types (user preferences, navigation commands, form definitions, refresh tokens) to the correct layer with rationale. - Code patterns: Shows imports and read/write calls from @agent-native/core for settings, application-state, db/schema, and oauth-tokens modules. - Use Case: When adding a new feature like user theme preferences, use this Skill to determine it belongs in Settings via putSetting, and get the exact code snippet with automatic SSE notification behavior. ## Quick Start Ask the agent where to store a new piece of data, such as "where should I store the user's theme preference and how do I read and write it?"