deployment
Skill14 starsChanged 8 months agoMITView on GitHub
Hosting, deployment, CI/CD, and going live. Activated when Claude works with deployment configs, Dockerfiles, Vercel/Netlify configs, or deployment-related commands.
- Reads credentials
33 other projects use a version of this.
Adopted by
Most recently taken up by
- artivilla/agent-skillstheir own version, first seen Nov 8, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- CrowdStrike/fusion-skillstheir own version, first seen Oct 30, 2026
- bmcszk/agent-skillstheir own version, first seen Oct 29, 2026
- microsoft/frontier-ghcp-ttt-rvastheir own version, first seen Oct 25, 2026
- SwastikPandey1024/agentic-engineering-ostheir own version, first seen Oct 20, 2026
Used with
Projects with it also use dependency-management, database and 8 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.
dkprogSkilldependency-management
Apply when wiring dependencies, integrating external services, or designing interfaces between modules. Ensures loose coupling through dependency injection, interface segregation, and proper abstraction boundaries.
Also in 3 projects that use this
mijunriSkilldatabase
数据库脚本与操作规范。脚本放在 db_scripts 目录，遵循查询优化、事务、安全等实践。
Also in 3 projects that use this
AnthropicSkilldocumentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Also in 5 projects that use this
pproencaSkillrefactoring
Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles. This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
0xSeroSkillsecurity
Also in 3 projects that use this
Other versions33 projects use a version of this.
Word for word · 1
- wewpellex21/code-sensei★ 3100% same
Edited · 0
None found.
Wrote their own version · 32
- NVIDIA/TensorRT-Model-Optimizer★ 5.6ksame name
- NVIDIA/Model-Optimizer★ 5.6ksame name
- matrixorigin/Memoria★ 624same name
- StarRocks/starrocks-debug-skills★ 77same name
- nahid-sparktales/agent-dispatcher★ 59same name
- digitalocean-labs/do-app-platform-skills★ 38same name
- CrowdStrike/fusion-skills★ 29same name
- manu14357/Zelaxy★ 15same name
- binnicordova/expo-boilerplate★ 11same name
- kpbray/power-bi-agent-skills★ 9same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- architectureSkill
- backendSkill
- databasesSkill
- debuggingSkill
- frontendSkill
- fundamentalsSkill
- javascriptSkill
- terminalSkill
- web-basicsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
0
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
- Very specific: line 12
Key insight: When you run npm start on your computer, only YOU can see the app.
“Common” is measured: kept by at least 6 in 10 of the 28 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.
Files
Deployment — CodeSensei Teaching Module
What is Deployment?
- Analogy: Deployment is moving from rehearsal to opening night. Your app works on your computer (localhost), and deployment puts it on a server so the whole world can use it.
- Key insight: When you run
npm starton your computer, only YOU can see the app. Deployment puts it on someone else's computer (a server) that's always on and connected to the internet.
Localhost vs Production
- localhost — your computer, only you can access it. The rehearsal stage.
- Production — a server in the cloud, anyone with the URL can access it. Opening night.
- Staging — a test server that mimics production. The dress rehearsal.
Common Deployment Platforms
- Vercel — one-click deployment for Next.js/React apps. Push to GitHub, it deploys automatically.
- Netlify — similar to Vercel, great for static sites and simple apps.
- Railway / Render — for backend apps with databases.
- AWS / GCP / Azure — the industrial-grade options. More complex but more powerful.
- Key insight: For most vibecoded projects, Vercel or Railway is all you need.
Domains & DNS
- Analogy: A domain name (like myapp.com) is a nickname for your server's actual address (an IP like 192.168.1.1). DNS is the phone book that translates names to addresses.
- Teaching flow: User types myapp.com → DNS looks up the address → Browser connects to the server → Server sends the app
Environment Variables in Production
- Key insight: Your .env file doesn't get uploaded. You set environment variables SEPARATELY in your hosting platform's dashboard.
- Why: Security. Your code is often public (on GitHub), but your secrets shouldn't be.
CI/CD (Continuous Integration / Continuous Deployment)
- Analogy: An automatic assembly line. Every time you push code to GitHub, the system automatically tests it, builds it, and deploys it — without you clicking anything.
- Key insight: This is why developers "push to main" to deploy. The pipeline handles the rest.
Docker (if encountered)
- Analogy: A shipping container for your app. It packages your code AND everything it needs to run (right version of Node, right libraries, right settings) into one portable box. That box runs the same everywhere.
- Dockerfile — the recipe for building the container
- Key insight: Docker solves "it works on my machine" — by shipping the machine too.
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.