agentleFS
tjg37tjg37/ironclaw/.claude/skills/start/SKILL.md

start

Skill1 starsChanged 7 months agoMITView on GitHub

Start IronClaw — ensures Docker services are running, runs migrations if needed, then starts the agent

  • Reads credentials

139 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

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 126 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Run docker compose -f docker-compose.dev.yml ps --format json to check if Postgres and NATS are running

    line 12
  2. Very specific:

    If either is not running or unhealthy, start them: docker compose -f docker-compose.dev.yml up -d

    line 13
  3. Very specific:

    Wait for Postgres to be healthy: docker compose -f docker-compose.dev.yml ps until postgres shows "healthy"

    line 14
  4. Very specific:

    Ensure pgvector is enabled: docker exec ironclaw-postgres-1 psql -U ironclaw -d ironclaw -c "CREATE EXTENSION IF NOT EXISTS vector;" …

    line 15
  5. Very specific:

    Run pnpm db:migrate to ensure the database schema is up to date

    line 19
  6. Distinctive:

    Ask the user which mode they want:

    line 24
  7. Very specific:

    If .env is missing auth config, tell the user to run /setup instead

    line 37

“Common” is measured: kept by at least 6 in 10 of the 126 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

/start — Start IronClaw

Get IronClaw running with a single command. Handles infrastructure automatically so the user doesn't have to remember Docker commands.

Step 1: Check Docker services

  • Run docker compose -f docker-compose.dev.yml ps --format json to check if Postgres and NATS are running
  • If either is not running or unhealthy, start them: docker compose -f docker-compose.dev.yml up -d
  • Wait for Postgres to be healthy: docker compose -f docker-compose.dev.yml ps until postgres shows "healthy"
  • Ensure pgvector is enabled: docker exec ironclaw-postgres-1 psql -U ironclaw -d ironclaw -c "CREATE EXTENSION IF NOT EXISTS vector;" 2>/dev/null

Step 2: Run migrations

  • Run pnpm db:migrate to ensure the database schema is up to date
  • This is safe to run repeatedly — it only applies pending migrations

Step 3: Start the agent

  • Ask the user which mode they want:
    • CLI mode (default): pnpm start — direct conversation, no Gateway/NATS needed
    • All-in-one mode: pnpm start:all — starts Docker, migrations, then Gateway + Runtime + Web in one terminal with color-coded output
    • Full mode (separate terminals): Tell the user to run:
      • pnpm start:gateway (Terminal 1)
      • pnpm start:runtime (Terminal 2)
      • pnpm start:web (Terminal 3, optional — web app at http://localhost:3000)
  • For CLI mode, run pnpm start directly

Notes

  • Postgres runs on port 5433 (not 5432) to avoid conflicts
  • NATS runs on port 4222 with JetStream enabled
  • If .env is missing auth config, tell the user to run /setup instead

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.