hermeticormus/setup-env-skills · Archived
Set up a project's development environment.
npx skills add hermeticormus/setup-env-skills --skill setup-env
This repository is archived — consider an actively maintained alternative.
Set up AI Runway on AKS — from bare cluster to running model. Covers cluster verification, cont…
314.8K installsGuides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, Mon…
269.8K installsSet up a new Prisma Postgres database and connect it to a local project using the Management AP…
257.4K installsSafely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill …
104.1K installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Configure `MaterialApp.router` using a package like `go_router` for advanced URL-based navigati…
30.3K installsAdd `flutter_localizations` and `intl` dependencies, enable "generate true" in `pubspec.yaml`, …
29.4K installsCreate a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
26.9K installsDeclared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
2,230 B
SUMMARY.md
384 B
A protocol for setting up a project's development environment from a bare clone to a working first run.
Tradeoff: bias toward verifying each step over assuming it worked. For a project set up recently, use judgment.
Read the project's own docs and version files (README, .tool-versions, engines, python_requires, go.mod, Cargo.toml). Note the required runtime and version, note system dependencies, and compare against what is installed. A version mismatch is the most common setup failure. Report gaps before closing them.
Install the version the project asks for, not the latest. Prefer a version manager (nvm, pyenv, rbenv, rustup) over a system-wide install. Use the package manager the lockfile implies.
Install from the lockfile (npm ci, poetry install) so the dependency graph matches the committed one. For Python, create an isolated virtualenv first. If install fails, read the first error, not the last.
Copy .env.example to .env and fill every variable. Generate local secrets the project needs. Do not commit secrets or invent placeholder secret values.
Build, test, then start. Observe behavior rather than trusting an exit code: hit the health endpoint, load a page, run the CLI with --help. If a step fails, trace it to the earlier step it came from and fix that step, not the symptom.
Record the exact steps, the non-obvious gotchas, and the common-command set (build, test, run, lint) so the next person reproduces it without rediscovery.
See full content at https://github.com/HermeticOrmus/setup-env-skills.