lane-database

Files (1)

• SKILL.md

SKILL.md (first lines)

# Lane: Database

## Focus

- Data integrity and consistency.
- Safe migration planning.
- Query correctness and performance.

## Starter Checklist

- [ ] Data model change has backward-safe migration path.
- [ ] Constraints and indexes are reviewed.
- [ ] Read/write paths are explicit and tested.
- [ ] Rollback considerations documented for risky changes.
- [ ] Access policy impact reviewed (if applicable).

## Guardrails

- Avoid destructive migrations without explicit approval.
- Treat policy and permission changes as high risk.

## Implementation Pattern

Evidence: 4-repo field extraction — see `.ai/MERGE_REPORT.md`.

- Persistence/query access goes through one service or persistence layer per domain; UI and
  route handlers do not call the database client directly.
- Use a privileged/admin data client only in server-side service code, never in code reachable
  from the browser; enforce ownership/policy checks server-side, never via client-side
  filtering alone.
- Schema changes go through numbered/ordered migration files in one canonical migrations
  directory; never mutate schema ad hoc from application code.

If the current project already has an established pattern for any of these, follow the existing
pattern instead of this default.

From JahacksV1/day-one-agent-kit, MIT.

More from JahacksV1/day-one-agent-kit