domains / families / devops / conductor-setup

conductor-setup

combined

Initialize project with Conductor artifacts (product definition, Configure a Rails project to work with Conductor (parallel coding agents)

When to use

• Working on conductor setup tasks or workflows
• Needing guidance, best practices, or checklists for conductor setup
• You need to configure a Rails project so it runs correctly inside Conductor workspaces.
• The project should support parallel coding agents with isolated ports, Redis settings, and shared secrets.
• You want the standard `conductor.json`, `bin/conductor-setup`, and `script/server` scaffolding for a Rails repo.

When not to use

• The task is unrelated to conductor setup
• You need a different domain or tool outside this scope
• Secret symlinks share the same sensitive values across workspaces; use only approved development credentials, preserve owner-only source permissions, exclude secrets from Git and do not imply worktrees are a secret sandbox.
• Sharing one Redis URL across Sidekiq, Cable and cache may still need service namespaces; dedicated instances or explicitly assigned namespaces are safer than modulo hashes. Never flush shared Redis as cleanup.
• npm/Gem installation and bin/dev execute project dependencies/scripts. Review them first; explicitly required lifecycle steps should be run individually after approval, not re-enabled silently.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies use the same skill name but describe different procedures. The first copy is a generic, interactive project onboarding flow that creates a conductor/ directory, setup_state.json, and product/tech/workflow/style documents. The second copy is a Rails-specific setup that creates conductor.json, bin/conductor-setup, script/server, and updates Redis-related Rails configuration. Neither copy is a shortened or wrapped version of the other; each contains material steps and constraints the other lacks, so crowning one would hide a real alternative.