skills.rest
oporpino
oporpinoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

br4zz4:setup-orchestration

Organizes shared and project-specific setup scripts across environment and dev scopes.

Updated May 25, 2025
Search Tags:#devops#docker#setup#monorepo#make#shell scripts#bootstrap
One-click install
npx skills add https://github.com/oporpino/commons --skill br4zz4-setup-orchestration-oporpino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: br4zz4:setup-orchestration
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Asetup-orchestration
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-setup-orchestration-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams maintaining multiple projects struggle to keep bootstrap and setup logic consistent between shared commons tooling and project-specific configuration, leading to duplicated scripts and drift between host and container environments. ## Core Features & Use Cases - Canonical Split: Enforces a clear separation between setup/environment/* (bootstrap that must work in host and container) and setup/dev/* (development configuration like .env and local defaults). - Scope Rules: Defines ownership boundaries where .commons holds shared mechanisms and .project holds project-specific setup steps. - Execution Model: Ensures make setup and Docker builds run the same setup contract through a shared runner instead of hardcoded per-project logic. - Use Case: When adding a new bootstrap step, use this Skill to decide whether it belongs in .commons/setup/environment, .commons/setup/dev, .project/setup/environment, or .project/setup/dev. ## Quick Start Ask the assistant to review where a new setup script should live in the commons and project setup structure.

Frequently Asked Questions about br4zz4:setup-orchestration

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

FAQPage Schema
How do I structure setup scripts across shared and project scopes?▼

Split setup into environment scripts that bootstrap tooling and must work in both host and container, and dev scripts for local configuration like .env files. Place shared steps in .commons and project-specific steps in .project, mirroring the same conceptual split in both.

Where should a new bootstrap script go in a monorepo setup?▼

Put it in .commons/setup/environment if it is shared across projects, .commons/setup/dev if it is shared dev configuration, .project/setup/environment for project-specific bootstrap, or .project/setup/dev for project-specific dev configuration.

How does make setup work with Docker builds?▼

Both make setup and the Docker build run the same setup contract through a shared runner. Shared setup steps are discovered and executed by the runner rather than being hardcoded per project, keeping host and container behavior consistent.

Should I create a .project/bin directory for setup scripts?▼

No, avoid creating .project/bin. The run/ directory is the application entrypoint surface, while bin/ holds only stack binstubs. Prefer small scripts with a single responsibility each under the shell/ technical namespace.

Related Skills

Explore More Software Engineering Skills→
kettleofketchupkettleofketchup

just

Bootstrap repositories with modular justfile structures and a setup script.

Community
Intermediate
enoch-robinsonenoch-robinson

docker-helper

Design Dockerfiles and docker-compose configurations for containerized applications.

Community
Advanced
marvelousempiremarvelousempire

multi-surface-single-engine

Centralize operation logic in one script, API, or binary with multiple interfaces.

Community
Advanced
dige04dige04

mise-expert

Centralize tool version management, per-directory environments, and task orchestration with mise.toml.

Community
Advanced