templates/issues/.agents/skills/storing-data/SKILL.md
How and where to store application data. Use when adding new data models, deciding between settings vs Drizzle tables, reading/writing app config, or working with application state.
npx skillsauth add BuilderIO/agent-native storing-dataInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
All persistent data lives in SQL. Issue data comes from the Jira Cloud API — the app proxies requests through the Nitro backend. Agent notes and application state are stored locally in SQL.
| Layer | Purpose | API |
|-------|---------|-----|
| Settings | Persistent app config | getSetting/putSetting from @agent-native/core/settings |
| Application State | Ephemeral UI state, agent <-> UI bridge | readAppState/writeAppState from @agent-native/core/application-state |
| OAuth Tokens | Atlassian credentials | @agent-native/core/oauth-tokens |
tools
Public booking flow — the state machine, animations, and URL/app-state sync.
tools
Trigger-based automations — reminders, follow-ups, webhooks — across the booking lifecycle.
tools
Team event types, round-robin assignment, collective bookings, host weights, and no-show calibration.
development
The pure `computeAvailableSlots` function — inputs, outputs, invariants, and debugging guide.