shipfree
Copilot instructions0 starsChanged 11 days agoMITView on GitHub
alwaysApply: true --- When the goal is to deploy an AI service for free, load the shipfree skill from .agents/skills/shipfree/SKILL.md and follow it. It carries the machine-verified free-tier limits and the architecture that fits inside them. The four rules that cause most free-tier failures: 1. Cloudflare Workers Free gets 10 ms of CPU per invocation. Time waiting on a socket is not CPU time, so streaming a model response is cheap. Buffering and parsing a large JSON body is not.…
We split this copilot-instructions.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
When the goal is to deploy an AI service for free, load the shipfree skill from .agents/skills/shipfree/SKILL.md and follow it.
- Very specific: line 25
Never put a provider API key in the frontend.
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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.
Files
alwaysApply: true
Shipfree
When the goal is to deploy an AI service for free, load the shipfree skill
from .agents/skills/shipfree/SKILL.md and follow it. It carries the
machine-verified free-tier limits and the architecture that fits inside them.
The four rules that cause most free-tier failures:
- Cloudflare Workers Free gets 10 ms of CPU per invocation. Time waiting on a socket is not CPU time, so streaming a model response is cheap. Buffering and parsing a large JSON body is not. Pipe response bodies; do not buffer them.
- Durable Objects get 30 seconds of CPU per request. Anything needing real CPU, per-user state, or WebSockets belongs in a Durable Object, not a Worker. Use the WebSocket Hibernation API so idle sessions are not billed.
- D1 allows 50 queries per Worker invocation. Batch reads into one statement instead of looping. KV allows only 1,000 writes per day and one write per second per key, so KV is a cache, never a database.
- Queue consumers get 5 minutes of CPU. Move embedding, summarising, scraping and transcoding off the request path into a queue consumer.
Never put a provider API key in the frontend. Proxy through a Worker and
keep the key in wrangler secret put.
Full limits, workflow and templates: .agents/skills/shipfree/SKILL.md.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/shipfree.mdcCursor rule
- shipfreeSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.