agentleFS
Sign inStart free
kennguyen887kennguyen887/agent-foundation/skills/rules-infra/SKILL.md

rules-infra

Skill1 starsChanged 5 months agoMITView on GitHub

Binding personal rules for live infrastructure and the local machine — load before touching any cloud/prod/staging resource (AWS/ECS/DNS/domains/hosts), any destructive action, or Docker/Colima on this Mac.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Verify live state first; task-def change = rolling restart (check health survives).

    line 12

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

rules-infra

These rules are binding (moved verbatim from ~/.claude/CLAUDE.md). Each heading names its full-text file in ~/.claude/rulebook/: Read that file before acting in its area — the one-liners are the trigger, not the whole rule.

Live Infrastructure — 18-live-infrastructure-change-safety.md

  • PROD (your-org us-east-1) strictly READ-ONLY: no infra/env/task-def changes, no scripts; fixes go via code PR or are surfaced for humans.
  • Verify live state first; task-def change = rolling restart (check health survives); avoid raw aws ecs CLI edits (follow operate-ecs-services-safely); one deliberate change at a time; rollback isn't guaranteed; confirm before shared-env changes, prefer reversible flips.
  • Any destructive action (any resource/tool) → revert runbook first: capture state + restore commands, hold the cheapest undo-token until the post-test passes, snapshot before data deletion, re-test the real consumer. Urgent prod incident + safe fix → apply now.
  • Retiring a host / moving a domain → prove ZERO prod consumers in every app first: every app × env incl. legacy V1 apps and apps pinned to an old shared-library version (read the PROD branch's pin, not rc's); grep each live prod bundle + build env for the host and read the host's access logs; an rc-only migration is not a prod migration; move every old-domain host a client calls (APIs, reports, uploads, tiles, webhooks), not just the one asked about; after the cut drive each prod client's real flow (a 307/wildcard 200 HTML is a failure).

Local Machine — 20-local-machine-container-runtime-is-colima-not-do.md

  • Colima, not Docker Desktop (never install/suggest it). Daemon down → colima start. Only ~ and /tmp/colima are mounted. More resources → colima stop && colima start --cpu N --memory N.

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