flyway

Name: flyway
Author: Zalesovsky

Flyway Migration Rules

by Zalesovsky(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from Zalesovsky/ai-in-development-task-2 (.cursor/rules/flyway/flyway.mdc). Copyright stays with the author.

Flyway Migration Rules

Create a separate table in the database for each entity.
Each table must be created in a separate migration (one migration file — one table).
Migration file naming:
- Use the format: V<version>__<table_name>_table.sql
- Example: V1__user_table.sql, V2__address_table.sql
Use CREATE something IF NOT EXISTS

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Installed into a catalogue, chosen by a router

Install flyway and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

zalesovsky-ai-in-development-task-2-flyway-rule.ocm.jsonjson

{
  "ocm": "1",
  "id": "zalesovsky-ai-in-development-task-2-flyway-rule",
  "kind": "skill",
  "name": "flyway",
  "description": "Flyway Migration Rules",
  "publisher": "Zalesovsky",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-cursor-rules"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Flyway Migration Rules"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-cursor-rules",
      "repository": "https://github.com/Zalesovsky/ai-in-development-task-2",
      "path": ".cursor/rules/flyway/flyway.mdc",
      "ref": "8b6e6cfe76d70659142b2600b6b75bb746efa31b",
      "url": "https://github.com/Zalesovsky/ai-in-development-task-2/blob/8b6e6cfe76d70659142b2600b6b75bb746efa31b/.cursor/rules/flyway/flyway.mdc",
      "key": "Zalesovsky/ai-in-development-task-2/.cursor/rules/flyway/flyway.mdc"
    }
  },
  "instructions": "# Flyway Migration Rules\n\n- Create a separate table in the database for each entity.\n- Each table must be created in a separate migration (one migration file — one table).\n- Migration file naming:\n   - Use the format: `V<version>__<table_name>_table.sql`\n   - Example: `V1__user_table.sql`, `V2__address_table.sql`\n- Use CREATE *something* IF NOT EXISTS",
  "cost": {
    "context_tokens": 88
  }
}

Fetch it by URL: GET /api/v1/registry/zalesovsky-ai-in-development-task-2-flyway-rule/manifest?version=1.0.0

About

Flyway Migration Rules

Use it

Install flyway and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews