env-setup

Generate an environment setup document from existing spec files and project configuration.

Updated May 3, 2026
One-click install
npx skills add https://github.com/ousiass/dotfiles --skill env-setup-ousiass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-setup
Source: https://github.com/ousiass/dotfiles/tree/main/.claude/skills/env-setup
Command: npx skills add https://github.com/ousiass/dotfiles --skill env-setup-ousiass

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns an existing project/spec into a complete environment setup document, so teams don’t guess about CI, lint/format, hooks, or Swagger/OpenAPI setup and instead align on a consistent approach.

Core Features & Use Cases

  • Spec discovery & architecture understanding: Scans a spec directory (or auto-discovers common spec locations) and reads architecture and component design to ground the generated setup.
  • Stack-aware configuration guidance: Detects existing dependencies and tooling (CI, lint/format, hooks, task runners, Swagger/OpenAPI) and proposes an integrated recommended setup.
  • Interactive confirmation workflow: Uses structured questions to lock in CI/CD, lint, format, linterly rules, git hooks, and Swagger/OpenAPI decisions with minimal ambiguity.
  • Opinionated TypeScript/JavaScript package manager: Enforces bun as the standardized package manager in commands and documentation, including migration suggestions from npm/yarn/pnpm.

Quick Start

Ask an AI to run the env-setup skill with your spec directory path (for example, docs/ or /env-setup docs/) to generate docs/environment/setup.md based on the existing architecture and current project settings.

Frequently Asked Questions about env-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a CI/CD and lint environment setup document from an existing spec?

You generate an environment setup document by pointing the skill to your spec directory so it can discover architecture, propose CI/CD and lint configurations, and confirm git hooks and Swagger setup interactively.

What is the best way to standardize TypeScript environment setup across a team?

Standardizing TypeScript environment setup is achieved by enforcing bun as the package manager, proposing consistent lint and format rules, and locking in CI/CD and git hooks through an interactive confirmation workflow.

Can I use npm or yarn instead of bun for JavaScript environment configuration?

You cannot use npm or yarn; the skill enforces bun consistently for JavaScript and TypeScript workflows, but it does provide migration suggestions if you are currently using npm, yarn, or pnpm.

Does the environment setup generation work without an existing project spec?

No, environment setup generation requires an existing formal spec to ground the proposed CI/CD, lint, and Swagger/OpenAPI decisions in your actual project architecture and component design.

How does Swagger or OpenAPI setup get configured during developer onboarding?

Swagger or OpenAPI setup is configured during developer onboarding by discovering existing project tooling, proposing an integrated documentation plan, and locking in decisions via strict interactive confirmation questions.