agentleFS
ZmokiZmoki/zmoki-astro-starter/.claude/skills/run/SKILL.md

run

Skill4 starsChanged 20 days agoMITView on GitHub

Launch the Astro dev server and verify it is working

  • Reads credentials

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use init, report and 6 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.
  • MicrosoftSkill

    init

    Also in 4 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 5 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • +1 more from microsoft

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Start the Astro dev server.

    line 7
  2. Distinctive:

    Start on a stable per-worktree port, with the chosen variables (none by default):

    line 18
  3. Distinctive:

    Check the health endpoint:

    line 30
  4. Distinctive:

    Never free a port by killing whatever listens on it.

    line 47

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

Run

Start the Astro dev server. No build or .env file is needed (see src/env.d.ts).

In a git worktree, run npm install first: node_modules isn't shared across worktrees.

Start

Analytics and captcha are off by default. Before starting, ask the user whether to enable either for this session (multi-select):

  • Analytics: sets PUBLIC_ANALYTICS_ENABLED=true. Real events go to the configured providers.
  • Captcha: sets PUBLIC_CAPTCHA_ENABLED=true. Turnstile's domain check may reject localhost.

Start on a stable per-worktree port, with the chosen variables (none by default):

PORT=$(( 4300 + $(echo "$PWD" | cksum | cut -d' ' -f1) % 100 ))

npm run dev -- --port $PORT
# or, with what the user enabled:
PUBLIC_ANALYTICS_ENABLED=true PUBLIC_CAPTCHA_ENABLED=true npm run dev -- --port $PORT

From an agent or other non-interactive shell, Astro starts the server in the background and returns. Read the URL it prints: if the port is taken it picks another one. Use that URL below.

Check the health endpoint:

curl -s <url>/-/astro/health
# → an HTML page containing "ok" and the short commit hash

Don't open a browser or take a screenshot. Once healthy, tell the user: Server running at <url>

Manage it with:

npx astro dev status   # is it running?
npx astro dev logs     # view logs (--follow to stream)
npx astro dev stop     # stop it

Never free a port by killing whatever listens on it.

Key routes

RouteWhat it tests
<url>/-/astro/healthHealth: "ok" + commit hash
<url>/Landing page
<url>/blog/Blog list
<url>/blog/<slug>/A post (PostLayout)
<url>/rss.xmlRSS feed
<url>/-/astro/brand/Brand / design-system reference

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.