prod-mimic
Skill0 starsChanged 5 months agoNo licenceView on GitHub
How to load-test a production web stack without touching production, by building a calibrated copy of it on one machine. Covers reading production's real shape, sizing every link the same (CPU and memory limits, a PgBouncer sidecar on the task's localhost, a capped database, a small cache, a load-balancer stand-in, network delay), seeding fake data instead of copying real users, calibrating the copy against a handful of ordinary production requests, step tests that climb until something breaks, the monitor that tells you what broke, and the symptom-to-cause table for reading the results. Distilled from a Django/gunicorn/PgBouncer/Postgres stack on ECS where the copy found the real wall (API CPU), a password hasher costing half of all CPU, a keep-alive mismatch behind daily 502s, and a worker-recycling stall. Load before any capacity question, before tuning threads or pool sizes, before an ad campaign or launch, or when asked "how much traffic can we take".
- Reads credentials
In this repository22 other files it gives its agents.
- production-authSkill
- awsSkill
- ckm:banner-designSkill
- ckm:brandSkill
- clean-codeSkill
- databaseSkill
- ckm:designSkill
- ckm:design-systemSkill
- dre-house-rulesSkill
- heimly-guideSkill
- ian-xiaohei-illustrationsSkill
- aws-infra-terraformSkill
- latency-tracingSkill
- loopSkill
- multi-tenant-isolationSkill
- observability-stackSkill
- payment-infrastructureSkill
- paymentSkill
- ckm:slidesSkill
- testingSkill
- ckm:ui-stylingSkill
- ui-ux-pro-maxSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.