devops
Skill43 starsChanged 8 months agoMITView on GitHub
Deploy to Vercel (frontends, serverless), Railway (backends, services), Supabase (database, auth, storage), GitHub Actions CI/CD. Use for deployments, infrastructure, monitoring, CI/CD.
- Reads credentials
50 other projects use a version of this.
Adopted by
Most recently taken up by
- DaraBoth/skilljmskilltheir own version, first seen Nov 8, 2026
- Surya8991/AgentMastertheir own version, first seen Nov 1, 2026
- darknecrocities/SkillBuildertheir own version, first seen Nov 1, 2026
- Mazalucas/El-DT-Lightweight-Armytheir own version, first seen Oct 26, 2026
- hu465/claude-skills-their own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use Problem-Solving Techniques.
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.
truongtv22SkillProblem-Solving Techniques
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
Also in 5 projects that use this
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
- mrgoonie/claudekit-skills★ 2.2ksame name
- Mindrally/skills★ 275same name
- mmtaee/ocserv-dashboard★ 275same name
- typv/nest-turbo-starter★ 224same name
- nicepkg/auto-company★ 188same name
- nagisanzenin/claude-code-production-grade-plugin★ 181same name
- hiromaily/go-crypto-wallet★ 128same name
- duongthinh03/portfolio★ 85same name
40 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 repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- code-review-securitySkill
- cold-email-sequence-generatorSkill
- community-led-growthSkill
- competitive-intelligence-analystSkill
- content-strategySkill
- deep-analysisSkill
- deep-reading-analystSkill
- deep-researchSkill
- email-sequenceSkill
- financial-unit-economicsSkill
- find-skillsSkill
- github-explorerSkill
- market-sizing-analysisSkill
- micro-saas-launcherSkill
- ph-community-outreachSkill
- premortemSkill
- pricing-strategySkill
- product-strategistSkill
- scientific-critical-thinkingSkill
- security-auditSkill
- senior-qaSkill
- seo-auditSkill
- seo-content-strategistSkill
- skill-creatorSkill
- startup-business-modelsSkill
- startup-financial-modelingSkill
- tailwind-v4-shadcnSkill
- teamSkill
- user-persona-creationSkill
- user-research-synthesisSkill
- ux-audit-rethinkSkill
- web-scrapingSkill
- webshSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
6
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
- could be automatic: a setting could enforce it
- Distinctive: line 150
Security: Never commit .env files, use platform-managed secrets, rotate keys regularly, use Supabase RLS policies
- Distinctive: line 151
Performance: Use Vercel edge caching, Railway health checks, Supabase connection pooling (pgBouncer)
- Very specific: line 153
Development: Use vercel dev / supabase start for local development, branch deploys for PRs
- Distinctive: line 161
Commit secrets to git -- use platform env vars instead
- Distinctive: line 164
Test on preview/staging before production
- Distinctive: line 165
Use migrations for database changes (never raw SQL on prod)
- Distinctive: line 166
Keep deployment logs for debugging
“Common” is measured: kept by at least 6 in 10 of the 38 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
DevOps Skill
Deploy and manage cloud infrastructure across Vercel, Railway, Supabase, and GitHub Actions.
When to Use
- Deploy frontends and serverless functions to Vercel
- Deploy backend services to Railway
- Manage databases, auth, and storage with Supabase
- Set up CI/CD pipelines with GitHub Actions
- Monitor deployments and debug production issues
- Manage environment variables and secrets
Platform Selection
| Need | Choose |
| Frontend / Next.js / static sites | Vercel |
| Serverless API routes / edge functions | Vercel |
| Long-running backend services | Railway |
| Background workers / cron jobs | Railway |
| PostgreSQL database | Supabase |
| User authentication | Supabase Auth |
| File/image storage | Supabase Storage |
| Realtime subscriptions | Supabase Realtime |
| Edge functions (Deno) | Supabase Edge Functions |
| CI/CD pipelines | GitHub Actions |
Quick Start
# Vercel - deploy frontend
vercel deploy # Preview deployment
vercel deploy --prod # Production deployment
# Railway - deploy backend
railway up # Deploy current directory
railway logs # View service logs
# Supabase - manage database
supabase db push # Push migrations to remote
supabase migration new feat_name # Create new migration
# GitHub Actions - CI/CD
gh workflow run deploy.yml # Trigger workflow manually
gh run list # View recent runsCommand Reference
Vercel
# Deployments
vercel deploy # Deploy to preview
vercel deploy --prod # Deploy to production
vercel ls # List recent deployments
vercel inspect <url> # Deployment details
vercel logs <url> # View function logs
vercel redeploy # Redeploy latest
# Environment variables
vercel env pull .env.local # Pull env vars locally
vercel env add SECRET_KEY # Add env var (interactive)
vercel env rm SECRET_KEY # Remove env var
# Project management
vercel link # Link local dir to project
vercel project ls # List all projects
# Domains
vercel domains add example.com # Add custom domain
vercel domains ls # List domainsRailway
# Deployments
railway up # Deploy current directory
railway up --detach # Deploy without tailing logs
railway logs # View service logs
railway logs --tail # Follow live logs
railway status # Service status
# Environment variables
railway variables # List all env vars
railway variables set KEY=VALUE # Set env var
railway variables get KEY # Get specific var
# Services
railway service # Current service info
railway open # Open in browser
# Database
railway connect postgres # Connect to Postgres shellSupabase
# Database
supabase db push # Push migrations to remote
supabase db reset # Reset LOCAL db only (never production!)
supabase migration new <name> # Create migration file
supabase migration list # List migrations
# Edge Functions
supabase functions deploy <name> # Deploy edge function
supabase functions serve # Local dev server
supabase functions list # List deployed functions
# Auth
supabase auth list # List auth providers
# Storage
supabase storage create <bucket> # Create storage bucket
# General
supabase link --project-ref <ref> # Link to remote project
supabase db diff # Show schema diff
supabase gen types typescript # Generate TS types from schemaGitHub Actions
# Workflows
gh workflow list # List all workflows
gh workflow run <name> # Trigger workflow
gh run list # List recent runs
gh run view <id> # View run details
gh run view <id> --log # View run logs
gh run watch # Watch running workflow
# Secrets
gh secret set SECRET_KEY # Set repo secret
gh secret list # List secretsBest Practices
Security: Never commit .env files, use platform-managed secrets, rotate keys regularly, use Supabase RLS policies
Performance: Use Vercel edge caching, Railway health checks, Supabase connection pooling (pgBouncer)
Cost: Stay on free tiers when possible, monitor usage in platform dashboards, use preview deployments to test before prod
Development: Use vercel dev / supabase start for local development, branch deploys for PRs
Safety Guardrails
NEVER do these:
vercel remove/vercel project rm-- deletes the projectrailway delete-- deletes the servicesupabase db reseton production -- destroys all data- Commit secrets to git -- use platform env vars instead
ALWAYS do these:
- Test on preview/staging before production
- Use migrations for database changes (never raw SQL on prod)
- Keep deployment logs for debugging
- Set up health check endpoints
Resources
- Vercel: https://vercel.com/docs
- Railway: https://docs.railway.com
- Supabase: https://supabase.com/docs
- GitHub Actions: https://docs.github.com/en/actions
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.

