conductor-setup
Set up this Rails project for Conductor, the Mac app for parallel coding agents.
Works with
0
total installs
0
this week
31.1K
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
31.1K
stars
Installation Guide
How to use conductor-setup on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
conductor-setup
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches conductor-setup from sickn33/antigravity-awesome-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate conductor-setup. Access via /conductor-setup in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
Set up this Rails project for Conductor, the Mac app for parallel coding agents.
When to Use
- 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, andscript/serverscaffolding for a Rails repo.
What to Create
1. conductor.json (project root)
Create conductor.json in the project root if it doesn't already exist:
{
"scripts": {
"setup": "bin/conductor-setup",
"run": "script/server"
}
}
2. bin/conductor-setup (executable)
Create bin/conductor-setup if it doesn't already exist:
#!/bin/bash
set -e
# Symlink .env from repo root (where secrets live, outside worktrees)
[ -f "$CONDUCTOR_ROOT_PATH/.env" ] && ln -sf "$CONDUCTOR_ROOT_PATH/.env" .env
# Symlink Rails master key
[ -f "$CONDUCTOR_ROOT_PATH/config/master.key" ] && ln -sf "$CONDUCTOR_ROOT_PATH/config/master.key" config/master.key
# Install dependencies
bundle install
npm install
Make it executable with chmod +x bin/conductor-setup.
3. script/server (executable)
Create the script directory if needed, then create script/server if it doesn't already exist:
#!/bin/bash
# === Port Configuration ===
export PORT=${CONDUCTOR_PORT:-3000}
export VITE_RUBY_PORT=$((PORT + 1000))
# === Redis Isolation ===
if [ -n "$CONDUCTOR_WORKSPACE_NAME" ]; then
HASH=$(printf '%s' "$CONDUCTOR_WORKSPACE_NAME" | cksum | cut -d' ' -f1)
REDIS_DB=$((HASH % 16))
export REDIS_URL="redis://localhost:6379/${REDIS_DB}"
fi
exec bin/dev
Make it executable with chmod +x script/server.
4. Update Rails Config Files
For each of the following files, if they exist and contain Redis configuration, update them to use ENV.fetch('REDIS_URL', ...) or ENV['REDIS_URL'] with a fallback:
config/initializers/sidekiq.rb
If this file exists and configures Redis, update it to use:
redis_url = ENV.fetch('REDIS_URL', 'redis://localhost:6379/0')
config/cable.yml
If this file exists, update the development adapter to use:
development:
adapter: redis
url: <%= ENV.fetch('REDIS_URL', 'redis://localhost:6379/1') %>
config/environments/development.rb
If this file configures Redis for caching, update to use:
config.cache_store = :redis_cache_store, { url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0') }
config/initializers/rack_attack.rb
If this file exists and configures a Redis cache store, update to use:
Rack::Attack.cache.store = ActiveSupport::Cache::RedisCacheStore.new(url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0'))
Implementation Notes
- Don't overwrite existing files: Check if conductor.json, bin/conductor-setup, and script/server exist before creating them. If they exist, skip creation and inform the user.
- Rails config updates: Only modify Redis-related configuration. If a file doesn't exist or doesn't use Redis, skip it gracefully.
- Create directories as needed: Create
script/directory if it doesn't exist.
Verification
After creating the files:
- Confirm all Conductor files exist and scripts are executable
- Run
script/serverto verify it starts without errors - Check that Rails configs properly reference
ENV['REDIS_URL']orENV.fetch('REDIS_URL', ...)
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
antigravity-design-expert
80sickn33/antigravity-awesome-skills
grill-me
356mattpocock/skills
premortem
194parcadei/continuous-claude-v3
deslop
113cursor/plugins
framer-motion
96pproenca/dot-skills
write-a-prd
88mattpocock/skills
Reviews
- WWilliam Park★★★★★Dec 20, 2024
conductor-setup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- HHiroshi Agarwal★★★★★Nov 11, 2024
conductor-setup reduced setup friction for our internal harness; good balance of opinion and flexibility.
- AAarav Thompson★★★★★Oct 2, 2024
Registry listing for conductor-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
- OOshnikdeep★★★★★Sep 5, 2024
conductor-setup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- DDev Bansal★★★★★Sep 5, 2024
conductor-setup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- GGanesh Mohane★★★★★Aug 24, 2024
Keeps context tight: conductor-setup is the kind of skill you can hand to a new teammate without a long onboarding doc.
- CCamila Liu★★★★★Aug 24, 2024
Keeps context tight: conductor-setup is the kind of skill you can hand to a new teammate without a long onboarding doc.
- YYuki Shah★★★★★Jul 27, 2024
Useful defaults in conductor-setup — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- RRahul Santra★★★★★Jul 15, 2024
Registry listing for conductor-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
- OOmar Anderson★★★★★Jul 15, 2024
Registry listing for conductor-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 30
Discussion
Comments — not star reviews- No comments yet — start the thread.