yu-iskwyu-iskw/coding-agent-fabric/.claude/skills/setup-dev-env/SKILL.md

setup-dev-env

Skill1 starsChanged 9 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/skill-inspectoredited, first seen Jan 23, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
yu-iskw/skill-inspector★ 275% 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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- initialize-projectSkill
- lint-and-fixSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- sync-readmeSkill
- test-and-fixSkill
- test-integration-dockerSkill

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read the .node-version file in the workspace root.
line 26
Very specific:
Check if trunk is installed by running trunk --version.
line 30
Very specific:
If trunk is not found, advise the user to install it.
line 31
Distinctive:
Run the following command at the workspace root to install all project dependencies.
line 41
Very specific:
Invoke Verifier: Run the verifier subagent (../../agents/verifier.md).
line 65
Very specific:
Handle Failure: If the verifier fails, follow its reporting to resolve environment-specific issues.
line 66

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

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 trunk installation
Step 2: Dependency Installation
- Run pnpm install
Step 3: Tooling Setup
- Run trunk install to fetch managed linters and formatters

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

Check if trunk is installed by running trunk --version. If trunk is not found, advise the user to install it. On macOS, use:

brew install trunk-io

For other platforms, refer to the Trunk installation documentation.

2. Dependency Installation

Run the following command at the workspace root to install all project dependencies. Refer to ../common-references/pnpm-commands.md for more pnpm commands.

pnpm install

3. Tooling Setup

Trunk manages linters and formatters hermetically. Run the following command to ensure all required tools are downloaded and ready. Refer to ../common-references/trunk-commands.md for more Trunk commands.

trunk install

Success Criteria

All pnpm dependencies are installed successfully.
trunk is 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 verifier subagent (../../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 verifier fails, follow its reporting to resolve environment-specific issues.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free