agentleFS
Sign inStart free
VJDiPaolaVJDiPaola/skill-forge/seeded-catalog-sync/SKILL.md

seeded-catalog-sync

Skill0 starsChanged 30 days agoMITView on GitHub

Keep static content catalogs, seed scripts, and API reads aligned across multiple sources. Use when static content catalogs, seed scripts, and API reads must stay aligned.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this workflow when curated content is stored in files but served through a seeded database or API.

    line 8
  2. Distinctive:

    If content is layered across files, prefer importing the aggregated module in the seed path.

    line 20
  3. Distinctive:

    Keep IDs unique across base and additive layers.

    line 21
  4. Distinctive:

    Do not leave the UI reading one file while the server seeds another.

    line 22
  5. Very specific:

    Keep the seed idempotent with onConflictDoNothing or equivalent upsert behavior.

    line 26
  6. Very specific:

    Do not seed only on count === 0 if new records need to appear in existing local databases.

    line 28
  7. Distinctive:

    Avoid destructive rewrites unless the user explicitly asks to reset seeded data.

    line 29
  8. Distinctive:

    Verify that list and detail routes resolve records from the same dataset the UI imports in tests.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Seeded Catalog Sync

Use this workflow when curated content is stored in files but served through a seeded database or API.

Map The Source Of Truth

  1. Locate the base content files.
  2. Locate any aggregated module that layers additional records on top.
  3. Locate the server seed path, runtime routes, and tests that import the catalog.
  4. Decide which module is the effective runtime source of truth.

Sync Rules

  • Point UI, tests, and seed code at the same effective catalog.
  • If content is layered across files, prefer importing the aggregated module in the seed path.
  • Keep IDs unique across base and additive layers.
  • Do not leave the UI reading one file while the server seeds another.

Seed Strategy

  1. Keep the seed idempotent with onConflictDoNothing or equivalent upsert behavior.
  2. Backfill missing rows when current DB count is less than catalog length.
  3. Do not seed only on count === 0 if new records need to appear in existing local databases.
  4. Avoid destructive rewrites unless the user explicitly asks to reset seeded data.

Validation

  1. Compare expected catalog length to what the DB or API returns.
  2. Run npm.cmd run test.
  3. Run npm.cmd run check.
  4. Verify that list and detail routes resolve records from the same dataset the UI imports in tests.

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