agentleFS
eric-cieloeric-cielo/moflo/.claude/skills/luminarium/SKILL.md

luminarium

Skill19 starsChanged 3 months agoMITView on GitHub

Print the localhost URL for The Luminarium — moflo's daemon dashboard — for the current project. Use when the user asks for "the luminarium link", "the moflo dashboard", "the daemon UI", or anything synonymous. Each project gets a deterministic port in 33000–33999; the actual bound port is recorded in `.moflo/daemon.lock`.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If the file exists and port is a valid number → the daemon is running and bound.

    line 23
  2. Very specific:

    If the file is missing or port is absent/invalid → the daemon is not running.

    line 24
  3. Distinctive:

    Don't fall back to any hardcoded port — there is no project-agnostic dashboard port.

    line 46
  4. Distinctive:

    Don't compute the deterministic port and report it as the link when the lock is missing — the daemon may be down, or bound to an alternate …

    line 47
  5. Very specific:

    Don't run flo daemon start automatically — the user asked for a link, not for daemon management.

    line 48
  6. Distinctive:

    Don't open a browser. Print the URL.

    line 49

≈ “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

/luminarium — Project Dashboard Link

Surface the URL for The Luminarium (the moflo daemon's localhost UI) for the project that this session is running in. No prompts, no confirmations — print the link and stop.

Procedure

  1. Find the project root. Walk up from process.cwd() looking for a .moflo/ directory. The session's cwd is almost always the project root, so check there first.
  2. Read .moflo/daemon.lock. It's a JSON file written by the daemon at bind time. The dashboard port is the port field:

    { "pid": 12345, "port": 33421, "startedAt": "...", ... }
    • If the file exists and port is a valid number → the daemon is running and bound. Use that port.
    • If the file is missing or port is absent/invalid → the daemon is not running. See step 4.
  3. Print the link in a single line, with the path verbatim — Claude Code renders it as clickable:

    The Luminarium: http://localhost:<port>

    Nothing else. No banner, no follow-up question, no "what would you like to do?".

  4. If the daemon isn't running (no lock file, or unparseable), say so in one line and offer the start command — don't run it:

    The moflo daemon isn't running for this project. Start it with: npx flo daemon start

Why read the lock, not compute the port

The port is project-deterministic (sha256(projectRoot) mapped into 33000–33999), but if the deterministic port was already taken at bind time the daemon scans forward and binds an alternate. The lock file is the only source of truth for what's actually bound. Do not compute the hash yourself — read the file.

Don't

  • Don't fall back to any hardcoded port — there is no project-agnostic dashboard port; a literal would route to a foreign daemon on a multi-project machine. If the lock is missing, report "not running".
  • Don't compute the deterministic port and report it as the link when the lock is missing — the daemon may be down, or bound to an alternate port. Report "not running" instead.
  • Don't run flo daemon start automatically — the user asked for a link, not for daemon management. Leave starting to /healer or the user.
  • Don't open a browser. Print the URL; let the user click.

Output

A single line. Examples:

The Luminarium: http://localhost:33421
The moflo daemon isn't running for this project. Start it with: npx flo daemon start

See Also

  • /healer — diagnoses and (with --fix) starts the daemon if it's not running.
  • src/cli/services/daemon-port.ts (and its JS twin bin/lib/daemon-port.mjs) — canonical port-resolution helpers; resolveClientPort() is what the rest of moflo uses.

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.