setup-dev-env
Skill2 starsChanged 10 months agoApache-2.0View on GitHub
Set up the development environment for the project. Use when starting work on the project, when dependencies are out of sync, or to fix environment setup failures.
- Installs packages
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- yu-iskw/coding-agent-fabricedited, first seen Feb 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- yu-iskw/coding-agent-fabric★ 184% same
Wrote their own version · 0
None found.
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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- .cursor/rules/typescript-coding-convention.mdcCursor rule
- .cursor/rules/unit-test-manners.mdcCursor rule
- build-and-fixSkill
- clean-projectSkill
- initialize-projectSkill
- lint-and-fixSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- test-and-fixSkill
- update-llm-modelsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read the .node-version file in the workspace root.
- Distinctive: line 44
Run the following command at the workspace root to install all project dependencies, including the Trunk launcher.
- Very specific: line 70
Invoke Verifier: Run the verifier subagent (../../agents/verifier.md).
- Very specific: line 71
Handle Failure: If the verifier fails, follow its reporting to resolve environment-specific issues.
≈ “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.
Files
Setup Development Environment
This skill automates the process of setting up the development environment to ensure all tools and dependencies are correctly installed and configured.
Workflow Checklist
- Step 1: Environment Validation
- Check Node.js version against
.node-version - Check for
pnpminstallation
- Check Node.js version against
- Step 2: Dependency Installation
- Run
pnpm install(this also installs thetrunklauncher)
- Run
- Step 3: Tooling Setup
- Run
pnpm trunk installto fetch managed linters and formatters
- Run
Detailed Instructions
1. Environment Validation
Node.js Version
Read the .node-version file in the workspace root. Ensure the current Node.js environment matches this version. If there's a mismatch, inform the user to switch Node versions (e.g., using nvm or fnm).
Trunk CLI
Trunk is managed via pnpm in this project using @trunkio/launcher. This ensures it works in cloud environments like Claude Code Cloud without manual installation.
The trunk launcher is installed automatically during pnpm install. You can then run Trunk commands using pnpm trunk.
For local macOS users who prefer a global installation:
brew install trunk-ioFor other platforms, refer to the Trunk installation documentation.
2. Dependency Installation
Run the following command at the workspace root to install all project dependencies, including the Trunk launcher. Refer to ../common-references/pnpm-commands.md for more pnpm commands.
pnpm install3. Tooling Setup
Trunk manages linters and formatters hermetically. Run the following command to ensure all required tools are downloaded and ready.
pnpm trunk installRefer to ../common-references/trunk-commands.md for more Trunk commands.
Success Criteria
- All
pnpmdependencies are installed successfully. trunkis installed and all managed tools are initialized.- The Node.js version matches the requirement in
.node-version.
Post-Setup Verification
To ensure the environment is fully operational:
- Invoke Verifier: Run the
verifiersubagent (../../agents/verifier.md). This confirms that the freshly installed dependencies allow for a successful build, pass lint checks, and satisfy all unit tests. - Handle Failure: If the
verifierfails, follow its reporting to resolve environment-specific issues.
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.