agentleFS
Sign inStart free
MarcSkyMarcSky/loanword/skills/start/SKILL.md

start

Skill5 starsChanged 53 days agoMITView on GitHub

Open the Loanword trainer — FSRS flashcard review in the browser at localhost:4747. Use when the user asks to review vocabulary, practise, or open the trainer.

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-audio and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +5 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Use run_in_background: true — the server has to stay up while the user works through the deck.

    line 17
  2. Distinctive:

    If there are no cards the UI says so itself.

    line 33
  3. Distinctive:

    Check once, after opening the browser — never before, and never twice in a session:

    line 39
  4. Very specific:

    Keep {placeholders} and inline HTML tags exactly as they appear in the key.

    line 55
  5. Distinctive:

    Never offer this twice, and never block opening the trainer on it.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 117 edited versions of this file we could read. “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

/loanword:start — the trainer

One command: it serves the trainer and opens the browser itself. It exits by itself if the port is already serving a trainer.

CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/serve.mjs"

Use run_in_background: true — the server has to stay up while the user works through the deck. It closes itself after 30 minutes with no requests, so a finished session never leaves the port held.

Say it in one line: opened http://localhost:4747 — space reveals the answer, 1–4 grade, esc quits.

To close it before then:

CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/serve.mjs" stop

LOANWORD_PORT overrides the port, --idle=<minutes> the timeout (0 disables it), --no-open skips the browser. The server binds 127.0.0.1 only.

If there are no cards the UI says so itself. Do not check that up front and do not run build unless asked.

Interface language

The trainer renders in the user's native language when a dictionary exists. Check once, after opening the browser — never before, and never twice in a session:

CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/i18n.mjs" audit "$(CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/store.mjs" config | node -pe 'JSON.parse(require("fs").readFileSync(0)).native')"
  • Clean, or the native language is en: say nothing.

  • No dictionary at all: offer in one line — "the trainer is in English; want me to translate it into <language>? about a minute, nothing leaves the machine". Only if they say yes:

    1. CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/i18n.mjs" keys for the exact list,
    2. translate every key yourself and Write ${CLAUDE_PLUGIN_ROOT}/ui/i18n/<code>.json,
    3. re-run audit <code> and fix what it reports.

    Keep {placeholders} and inline HTML tags exactly as they appear in the key. Plural keys look like card|cards and take an object of CLDR categories — see ui/i18n/README.md.

  • Dictionary exists but audit reports missing keys: mention the count in one line and offer to fill them. Do not rewrite entries that are already translated.

Never offer this twice, and never block opening the trainer on it.

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