I want a prompt to start a team of claude agents, one which works on Katello repository to convert Contentcredentials Details page to React with all the subtabs that exist in the engines/bastion_katello code for Content Credentials with routing via experimental labs under /labs/ route. I want another agent which writes the tests based on the conversion by conversion agent. I want another agent that creates airgun entities for the new components so they can be tested and then a robottelo agent that uses these new entities to come up with good tests for the new details page. Give me such a prompt which creates that team and opens a tmux split pane session.
# Katello Content Credentials React Conversion Team Prompt
Create a team to convert the Katello Content Credentials Details page from Angular (bastion_katello) to React with full test coverage.
## Team Setup
1. **Create Team**: Create a team named "katello-cc-react" with description "Convert Content Credentials Details page to React with routing under /labs/ and full test coverage"
2. **Create Initial Tasks**:
- Task 1: "Convert Content Credentials Details page to React" - Analyze engines/bastion_katello code for Content Credentials Details page and all subtabs, then convert to React components under experimental labs with /labs/ routing
- Task 2: "Write React tests for converted components" - Write comprehensive React tests (RTL/Jest) for all converted Content Credentials components and subtabs (blocked by Task 1)
- Task 3: "Create airgun entities for new components" - Create airgun page objects and entities for the new React Content Credentials components to enable integration testing (blocked by Task 1)
- Task 4: "Write robottelo tests using airgun entities" - Write comprehensive robottelo integration tests for the Content Credentials Details page using the new airgun entities (blocked by Task 3)
3. **Spawn Agents**:
**Agent 1: "react-converter"** (general-purpose, opus model)
- Task: Analyze the existing Angular Content Credentials Details page in engines/bastion_katello/app/assets/javascripts/bastion_katello/content-credentials/ (or similar path)
- Identify all subtabs: Details, Products, Repositories, etc.
- Convert to React functional components with hooks
- Implement routing under /labs/content-credentials/:id structure
- Use existing Katello React patterns (check webpack/assets/javascripts/ for examples)
- Ensure API integration matches existing endpoints
- Create components in webpack/assets/javascripts/components/ContentCredentials/
- Add routing in webpack/assets/javascripts/react_app/routes/
- Mark Task 1 as in_progress, then completed when done
**Agent 2: "test-writer"** (general-purpose, sonnet model)
- Wait for react-converter to complete Task 1
- Claim Task 2 when available
- Write RTL (React Testing Library) tests for all converted components
- Cover all subtabs and user interactions
- Test API mocking and data fetching
- Ensure >80% code coverage
- Place tests in webpack/assets/javascripts/components/ContentCredentials/__tests__/
- Mark Task 2 as completed when done
**Agent 3: "airgun-dev"** (general-purpose, sonnet model)
- Wait for react-converter to complete Task 1
- Claim Task 3 when available
- Analyze the new React components and their DOM structure
- Create airgun page objects in appropriate airgun directory structure
- Create entity classes for Content Credentials operations (create, read, update, delete)
- Follow existing airgun patterns for page objects and entities
- Ensure selectors work with the new React components
- Mark Task 3 as completed when done
**Agent 4: "robottelo-tester"** (general-purpose, sonnet model)
- Wait for airgun-dev to complete Task 3
- Claim Task 4 when available
- Write comprehensive robottelo tests using the new airgun entities
- Cover CRUD operations for Content Credentials
- Test all subtabs functionality (Products, Repositories association)
- Test edge cases and error handling
- Follow existing robottelo test patterns
- Mark Task 4 as completed when done
4. **Setup tmux session**:
```bash
# Create new tmux session with 4 panes
tmux new-session -d -s katello-cc-react
tmux split-window -h -t katello-cc-react
tmux split-window -v -t katello-cc-react:0.0
tmux split-window -v -t katello-cc-react:0.1
# Label panes
tmux select-pane -t 0 -T "React Converter"
tmux select-pane -t 1 -T "Test Writer"
tmux select-pane -t 2 -T "Airgun Dev"
tmux select-pane -t 3 -T "Robottelo Tester"
# Send commands to monitor each agent's work
tmux send-keys -t katello-cc-react:0.0 'echo "React Converter Agent - Converting Angular to React"' C-m
tmux send-keys -t katello-cc-react:0.1 'echo "Test Writer Agent - Writing React Tests"' C-m
tmux send-keys -t katello-cc-react:0.2 'echo "Airgun Dev Agent - Creating Page Objects"' C-m
tmux send-keys -t katello-cc-react:0.3 'echo "Robottelo Tester Agent - Writing Integration Tests"' C-m
# Attach to session
tmux attach-session -t katello-cc-react- TeamCreate creates the team and task list
- All 4 tasks are created with dependencies (Task 2,3 blocked by Task 1; Task 4 blocked by Task 3)
- All 4 agents spawn in parallel
- react-converter claims and starts Task 1 immediately
- Other agents wait for their blocking tasks to complete
- As tasks complete, agents claim next available unblocked tasks
- tmux session provides real-time visibility into all agents' work
- When all tasks complete, agents gracefully shut down
- React Patterns: Agents should study existing Katello React code for consistency
- API Compatibility: Maintain compatibility with existing Katello API endpoints
- Labs Routing: All new routes under /labs/ prefix for experimental features
- Test Coverage: Comprehensive unit and integration test coverage
- Dependencies: Proper task dependencies ensure sequential work where needed
- Parallel Work: Agents 2 and 3 can work in parallel once Agent 1 completes
---
## Notes
This prompt sets up a coordinated team of 4 Claude agents working on different aspects of the Katello Content Credentials React conversion:
1. **react-converter**: Converts the Angular page to React
2. **test-writer**: Writes React component tests
3. **airgun-dev**: Creates page objects for UI testing
4. **robottelo-tester**: Writes integration tests
The agents work in a coordinated fashion with proper task dependencies, and the tmux session provides visibility into all agents' work in real-time.