agentleFS
Sign inStart free
omdenkar2-uiomdenkar2-ui/all-in-one/skills/aio-data/SKILL.md

aio-data

Skill0 starsChanged 30 days agoMITView on GitHub

Plan and implement backend schemas, transactions, tenant access and compatible data migrations.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read data, current schema/query plans and the exact access roles.

    line 12
  2. Distinctive:

    Use aio-tdd for changed invariants and access behavior.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AIO Data

Plan and implement backend schemas, transactions, tenant access and compatible data migrations.

Protocol

  1. Read data, current schema/query plans and the exact access roles. Put invariants in constraints/transactions where appropriate rather than relying only on application checks.
  2. Model ownership, uniqueness/idempotency, transactional effect/outbox boundaries and tenant predicates. Test with actual constrained roles; administrator success is not evidence of isolation.
  3. Design migrations for mixed old/new code, realistic data volume, locks, backfill restart and validation. Use expand/migrate/contract where compatibility requires it; destructive cleanup needs actual authorization.
  4. Use aio-tdd for changed invariants and access behavior. Measure affected query plans and connection budgets. Verify concurrent writes, rollback, duplicate identity, stale readers, tenant access, migration interruption and old/new consumers.
  5. Record rollout/recovery and retention/deletion implications. A rollback command is insufficient when data loss or irreversible transformation must be addressed separately.

Return and handoff

A schema/migration/query change with invariant, compatibility, access and operational evidence.

In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free