local-dev-setup
Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use when asked to write a dev setup guide, create onboarding documentation for engineers, document local environment setup, or write a getting-started guide for a codebase. Produces a complete setup guide that a new engineer can follow from zero to running tests in under 30 minutes, with a troubleshootin
npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Local Dev Setup Skill Produce a complete local development environment setup guide for a service or project — walking a new engineer from zero (a clean laptop) to a working local environment with passing tests in under 30 minutes. A good setup guide reduces onboarding time, prevents the "it works on my machine" problem, and lets engineers make their first contribution with confidence. Write every step as a concrete command or action — not a description of what needs to happen. ## Required Inputs Ask for these if not already provided: - **Service name** and what it does - **Tech stack** — language, framework, database, cache, message queue, and any external services - **Dependencies** — databases, caches, message queues, and external services (mocked or real) - **Test framework** — how tests are run and what the test suite covers - **CI/CD platform** — GitHub Actions, CircleCI, Jenkins, etc. (for context on what "passing CI" means locally) ## Output Format --- # Local Development Setup: [Service Name] **Tech stack:** [Language + version] | [Framework] | [Database] | [Cache] **Estimated setup time:** [20–30 minutes] on a clean machine **Last verified:** [Date] on [macOS Ventura 13.
- Required Inputs
- Output Format
- Prerequisites
- Required Tools
- Optional but Recommended
- Required Accounts and Access
- 1. Repository Setup
- 2. Environment Variables
- Step 1 — Copy the example file
- Step 2 — Fill in the values
- 3. Local Service Dependencies
- What Docker Compose Starts
- Stopping Dependencies
- 4. Install Dependencies and Build
Clone the repository git clone git@github.com:[org]/[repo-name].git cd [repo-name] Install git hooks (required — enforces commit message format and runs pre-commit checks) make install-hooks Or manually: cp scripts/hooks/pre-commit .git/hooks/pre-commit && chmod +x .git/hooks/pre-commit Verify your git setup git config user.name # should be your name git config user.email # should be your work email
What does the local-dev-setup skill do?
Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use when asked to write a dev setup guide, create onboarding documentation for engineers, document local environment setup, or write a getting-started guide for a codebase. Produces a complete setup guide that a new engineer can follow from zero to running tests in under 30 minutes, with a troubleshootin
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill local-dev-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.