storage-rules

Govern storage changes across database schemas, migrations, and access policies.

2|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill storage-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: storage-rules
Source: https://github.com/timgranlundmarsden/claude-agent-flow/tree/main/skills/storage-rules
Command: npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill storage-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or inconsistent changes to database storage, schema, and access control by centralizing all persistence-related decisions in one place.

Core Features & Use Cases

  • RLS Ownership: Keeps row level security policy changes under storage-layer control so other layers do not accidentally modify access rules.
  • Reversible Migrations: Enforces up and down SQL migration structure, explicit naming, and conservative handling of destructive changes.
  • Storage Governance: Covers relational schema design, bucket access, signed URLs, local persistence patterns, retention, backup, encryption, and cost-aware storage decisions.
  • Use Case: When a feature requires a new table, file bucket, or access policy, this Skill guides the change so the implementation stays auditable, reversible, and secure.

Quick Start

Use the storage-rules skill to design the database change, write a reversible migration, and document any access policy before implementing it.

Frequently Asked Questions about storage-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure database migrations are reversible and safe for schema evolution?

Reversible database migrations require explicit up and down SQL structures, conservative handling of destructive changes, and centralized ownership of row level security policies to prevent unsafe schema evolution.

What is centralized row level security ownership for storage policies?

Centralized row level security ownership keeps access policy changes strictly under storage-layer control, preventing other application layers from accidentally modifying database access rules.

How do I manage access control for cloud buckets and signed URLs?

Managing access control for cloud buckets and signed URLs requires governing storage policies, documenting access rules, and applying conservative handling to maintain secure file persistence.

When do I need documented access rules for database schema changes?

Documented access rules are needed whenever a feature requires a new table, file bucket, or access policy, ensuring the database schema change remains auditable, reversible, and secure.

What is the best way to handle destructive storage changes in SQL migrations?

The best way to handle destructive storage changes is enforcing reversible up and down migration structures with explicit naming and conservative execution to maintain schema safety.

Does this approach work for local disk persistence and retention policies?

Yes, storage governance covers local disk patterns, retention, backup, and encryption, applying centralized access rules and conservative handling to all file persistence and relational schema decisions.