local-development-setup
/local-development-setup
Make a working local environment reachable in minutes from a clean machine, and keep it close to production. Use when onboarding takes days or developers cannot run the system locally.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Make a working local environment reachable in minutes from a clean machine, and keep it close to production. Use when onboarding takes days or developers cannot run the system locally.
Original author description
Make a working local environment reachable in minutes from a clean machine, and keep it close to production. Use when onboarding takes days or developers cannot run the system locally.
How it works
- Method
- Boundaries
SKILL.md preview
--- name: local-development-setup description: Make a working local environment reachable in minutes from a clean machine, and keep it close to production. Use when onboarding takes days or developers cannot run the system locally. --- # Local development setup A slow or broken local setup taxes every developer continuously and blocks new joiners entirely. It is usually neglected because the people who could fix it already have it working. ## Method 1. **Target one command from a clean checkout.** Everything else is documentation nobody follows correctly (see contributor-onboarding). 2. **Test on a genuinely clean machine.** Setup instructions written by someone with the tools installed always omit steps. 3. **Containerise dependencies.** Databases, queues, and services as containers rather than machine-wide installations that conflict between projects. 4. **Provide seed data.** An empty database is not a working environment, and realistic sample data is what makes local testing meaningful (see environment-provisioning). 5. **Keep it close to production.** Same major versions and configuration shape, since divergence moves bug discovery later. 6. **Make the feedback loop fast.** Hot reload and fast tests, because the edit-run cycle is repeated hundreds of times a day. 7. **Own it explicitly.** An unowned setup decays until someone new cannot start, which is when the cost becomes visible. ## Boundaries Local environments cannot reproduce production scale, data, or managed services fully. Some systems are too large to run locally and need alternatives such as remote development. Machine differences remain a source of divergence that containers reduce rather than eliminate.
Versions
The database has no other skills named local-development-setup.
Database snapshot: 13.11.2026 · package version c3d8aa8705bf (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100local-dev
Local development environment setup and commands. Use when helping with dev server, Docker, or local testing. - 100linear-local-dev-loop
Set up local Linear development environment and testing workflow. Use when configuring local development, testing integrations, or setting up a development workflow with Linear. Trigger with phrases like "linear local development", "linear dev setup", "test linear locally",… - 90onboarding-docs
Write onboarding docs that get a new contributor to a verified working setup and a first contribution fast. Use when new joiners struggle to get started or setup instructions keep breaking. - 100apollo-local-dev-loop
Configure Apollo.io local development workflow. Use when setting up development environment, testing API calls locally, or establishing team development practices. Trigger with phrases like "apollo local dev", "apollo development setup", "apollo dev environment", "apollo testing locally". - 100apollo-local-dev-loop
Configure Apollo.io local development workflow. Use when setting up development environment, testing API calls locally, or establishing team development practices. Trigger with phrases like "apollo local dev", "apollo development setup", "apollo dev environment", "apollo testing locally". - 100vercel-local-dev-loop
Configure Vercel local development with vercel dev, environment variables, and hot reload. Use when setting up a development environment, testing serverless functions locally, or establishing a fast iteration cycle with Vercel. Trigger with phrases like "vercel dev setup",…