agentleFS
lukashouthoofdlukashouthoofd/cenekathon/.agents/skills/deploy-fast/SKILL.md

deploy-fast

Skill1 starsChanged 13 days agoMITView on GitHub

Use when you need a public demo URL, a reproducible run command, or the "from prototype to scalable product" story.

  • Reads credentials

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:

    Fallback demo: keep a local run (docs/STACK.md: install, dev, test) and a 60-second screen recording — event wifi fails.

    line 11

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

Deploy fast

  1. Pick the zero-config host for the stack: static/Next/Vite → Vercel or Netlify; Python/Node API → Render, Railway or Fly; containers → one Dockerfile + docker compose up. Free tier is fine.
  2. Deploy the walking skeleton in the first hour, then redeploy on every merge to main (host's GitHub integration; no custom CI needed).
  3. Env vars go in the host dashboard, mirrored from .env.example; never commit .env.
  4. Fallback demo: keep a local run (docs/STACK.md: install, dev, test) and a 60-second screen recording — event wifi fails.
  5. Scale story (for the pitch, not for building): stateless app + managed DB, queue for slow jobs, cache for repeated AI calls, CDN for static, logs/metrics, CI/CD. Write 3 bullets in docs/PITCH.md — don't implement.
  6. Smoke-test the URL from a phone / incognito window before 19:00.

Done when: a public URL serves the latest main, and a teammate's fresh clone runs with the documented commands.

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.