agentleFS
ValueMelodyValueMelody/melody-auth/.claude/skills/generate-s2s/SKILL.md

generate-s2s

Skill649 starsChanged 8 months agoMITView on GitHub

Use this skill whenever the user asks to regenerate the S2S API artifacts, refresh the server swagger output, or update the generated admin-panel auth API client from the backend schema and routes. Also use this skill proactively whenever the current task changes any S2S generation inputs, even if the user did not explicitly ask for regeneration. Relevant changes include updates under `server/src/routes/`, `server/src/scripts/schemas/`, `server/src/scripts/generate-swagger.cjs`, or `admin-panel/scripts/generateService.ts`. Trigger on requests like "generate s2s", "regenerate swagger", "refresh auth api", "update the generated s2s client", or "run s2s:generate", and also when those source files were edited as part of the work.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When this skill is triggered, just run the root s2s:generate script from the project root and do nothing else.

    line 17
  2. Distinctive:

    If you changed any relevant S2S source files during the current task, invoke this skill before finishing the task even when the user never …

    line 20
  3. Very specific:

    Do not trigger this skill for edits that only touch generated outputs like server/src/scripts/swagger.json or …

    line 23
  4. Distinctive:

    Do not inspect files, check diffs, summarize changes, or run follow-up commands unless the user explicitly asks for that extra work.

    line 27

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

Generate S2S

When this skill is triggered, just run the root s2s:generate script from the project root and do nothing else.

If you changed any relevant S2S source files during the current task, invoke this skill before finishing the task even when the user never mentioned generation explicitly.

Do not trigger this skill for edits that only touch generated outputs like server/src/scripts/swagger.json or admin-panel/services/auth/api.ts, or for unrelated admin panel UI changes.

Do not inspect files, check diffs, summarize changes, or run follow-up commands unless the user explicitly asks for that extra work.

cd /Users/baozier/Projects/melody-auth && npm run s2s:generate

This regenerates the S2S swagger output and admin-panel/services/auth/api.ts.

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.