claude-code-orchestrator-kit 1.4.15 → 1.4.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/agents/database/workers/api-builder.md +8 -0
- package/.claude/agents/database/workers/database-architect.md +8 -0
- package/.claude/agents/database/workers/supabase-fixer.md +825 -0
- package/.claude/agents/database/workers/supabase-realtime-optimizer.md +1086 -0
- package/.claude/agents/database/workers/supabase-storage-optimizer.md +1187 -0
- package/.claude/agents/development/workers/code-structure-refactorer.md +771 -0
- package/.claude/agents/development/workers/judge-specialist.md +3275 -0
- package/.claude/agents/development/workers/langgraph-specialist.md +1343 -0
- package/.claude/agents/development/workers/stage-pipeline-specialist.md +1173 -0
- package/.claude/agents/frontend/workers/fullstack-nextjs-specialist.md +10 -0
- package/.claude/agents/health/workers/bug-fixer.md +0 -1
- package/.claude/agents/infrastructure/workers/bullmq-worker-specialist.md +748 -0
- package/.claude/agents/infrastructure/workers/rag-specialist.md +799 -0
- package/.claude/agents/infrastructure/workers/server-hardening-specialist.md +1128 -0
- package/.claude/agents/integrations/workers/lms-integration-specialist.md +866 -0
- package/.claude/commands/supabase-performance-optimizer.md +73 -0
- package/.claude/commands/ultra-think.md +158 -0
- package/.claude/skills/senior-architect/SKILL.md +209 -0
- package/.claude/skills/senior-architect/references/architecture_patterns.md +755 -0
- package/.claude/skills/senior-architect/references/system_design_workflows.md +749 -0
- package/.claude/skills/senior-architect/references/tech_decision_guide.md +612 -0
- package/.claude/skills/senior-architect/scripts/architecture_diagram_generator.py +114 -0
- package/.claude/skills/senior-architect/scripts/dependency_analyzer.py +114 -0
- package/.claude/skills/senior-architect/scripts/project_architect.py +114 -0
- package/package.json +1 -1
|
@@ -0,0 +1,73 @@
|
|
|
1
|
+
---
|
|
2
|
+
allowed-tools: Read, Write, Edit, Bash, Task
|
|
3
|
+
argument-hint: [--all] | --queries | --indexes | --rls | --functions | --realtime | --storage
|
|
4
|
+
description: Optimize Supabase database performance by delegating to specialized agents
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Supabase Performance Optimizer
|
|
8
|
+
|
|
9
|
+
Optimize Supabase database performance with specialized agents: **$ARGUMENTS**
|
|
10
|
+
|
|
11
|
+
## Agent Delegation Matrix
|
|
12
|
+
|
|
13
|
+
| Argument | Agent | What it fixes |
|
|
14
|
+
|----------|-------|---------------|
|
|
15
|
+
| `--queries`, `--indexes`, `--rls`, `--functions` | `supabase-fixer` | Advisors API issues (security + performance) |
|
|
16
|
+
| `--realtime` | `supabase-realtime-optimizer` | Publication issues, subscription indexes |
|
|
17
|
+
| `--storage` | `supabase-storage-optimizer` | Orphaned files, table sizes, data types |
|
|
18
|
+
| `--all` | All three agents | Complete optimization |
|
|
19
|
+
|
|
20
|
+
## Task Execution
|
|
21
|
+
|
|
22
|
+
Based on **$ARGUMENTS**, delegate to the appropriate agent(s):
|
|
23
|
+
|
|
24
|
+
### For `--queries`, `--indexes`, `--rls`, `--functions`:
|
|
25
|
+
|
|
26
|
+
Use Task tool with:
|
|
27
|
+
- `subagent_type`: `supabase-fixer`
|
|
28
|
+
- `prompt`: Focus on performance advisors for query/index optimization, or security advisors for RLS/function issues
|
|
29
|
+
|
|
30
|
+
### For `--realtime`:
|
|
31
|
+
|
|
32
|
+
Use Task tool with:
|
|
33
|
+
- `subagent_type`: `supabase-realtime-optimizer`
|
|
34
|
+
- `prompt`: Optimize realtime subscriptions, check publications, add missing indexes for filters
|
|
35
|
+
|
|
36
|
+
### For `--storage`:
|
|
37
|
+
|
|
38
|
+
Use Task tool with:
|
|
39
|
+
- `subagent_type`: `supabase-storage-optimizer`
|
|
40
|
+
- `prompt`: Analyze table sizes, find orphaned files, optimize data types
|
|
41
|
+
|
|
42
|
+
### For `--all`:
|
|
43
|
+
|
|
44
|
+
Run all three agents sequentially:
|
|
45
|
+
1. First: `supabase-fixer` (security + performance advisors)
|
|
46
|
+
2. Then: `supabase-realtime-optimizer` (realtime publications)
|
|
47
|
+
3. Finally: `supabase-storage-optimizer` (storage cleanup)
|
|
48
|
+
|
|
49
|
+
## Expected Output
|
|
50
|
+
|
|
51
|
+
Each agent generates a structured report in `.tmp/current/`:
|
|
52
|
+
- `database-fixing-report.md` (from supabase-fixer)
|
|
53
|
+
- `realtime-optimization-report.md` (from supabase-realtime-optimizer)
|
|
54
|
+
- `storage-optimization-report.md` (from supabase-storage-optimizer)
|
|
55
|
+
|
|
56
|
+
## Quick Reference
|
|
57
|
+
|
|
58
|
+
```bash
|
|
59
|
+
# Fix security issues (RLS, functions)
|
|
60
|
+
/supabase-performance-optimizer --rls --functions
|
|
61
|
+
|
|
62
|
+
# Optimize queries and indexes
|
|
63
|
+
/supabase-performance-optimizer --queries --indexes
|
|
64
|
+
|
|
65
|
+
# Optimize realtime subscriptions
|
|
66
|
+
/supabase-performance-optimizer --realtime
|
|
67
|
+
|
|
68
|
+
# Clean up storage
|
|
69
|
+
/supabase-performance-optimizer --storage
|
|
70
|
+
|
|
71
|
+
# Full optimization (all agents)
|
|
72
|
+
/supabase-performance-optimizer --all
|
|
73
|
+
```
|
|
@@ -0,0 +1,158 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Deep analysis and problem solving with multi-dimensional thinking
|
|
3
|
+
argument-hint: [problem or question to analyze]
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Deep Analysis and Problem Solving Mode
|
|
7
|
+
|
|
8
|
+
Deep analysis and problem solving mode
|
|
9
|
+
|
|
10
|
+
## Instructions
|
|
11
|
+
|
|
12
|
+
1. **Initialize Ultra Think Mode**
|
|
13
|
+
- Acknowledge the request for enhanced analytical thinking
|
|
14
|
+
- Set context for deep, systematic reasoning
|
|
15
|
+
- Prepare to explore the problem space comprehensively
|
|
16
|
+
|
|
17
|
+
2. **Parse the Problem or Question**
|
|
18
|
+
- Extract the core challenge from: $ARGUMENTS
|
|
19
|
+
- Identify all stakeholders and constraints
|
|
20
|
+
- Recognize implicit requirements and hidden complexities
|
|
21
|
+
- Question assumptions and surface unknowns
|
|
22
|
+
|
|
23
|
+
3. **Multi-Dimensional Analysis**
|
|
24
|
+
Approach the problem from multiple angles:
|
|
25
|
+
|
|
26
|
+
### Technical Perspective
|
|
27
|
+
- Analyze technical feasibility and constraints
|
|
28
|
+
- Consider scalability, performance, and maintainability
|
|
29
|
+
- Evaluate security implications
|
|
30
|
+
- Assess technical debt and future-proofing
|
|
31
|
+
|
|
32
|
+
### Business Perspective
|
|
33
|
+
- Understand business value and ROI
|
|
34
|
+
- Consider time-to-market pressures
|
|
35
|
+
- Evaluate competitive advantages
|
|
36
|
+
- Assess risk vs. reward trade-offs
|
|
37
|
+
|
|
38
|
+
### User Perspective
|
|
39
|
+
- Analyze user needs and pain points
|
|
40
|
+
- Consider usability and accessibility
|
|
41
|
+
- Evaluate user experience implications
|
|
42
|
+
- Think about edge cases and user journeys
|
|
43
|
+
|
|
44
|
+
### System Perspective
|
|
45
|
+
- Consider system-wide impacts
|
|
46
|
+
- Analyze integration points
|
|
47
|
+
- Evaluate dependencies and coupling
|
|
48
|
+
- Think about emergent behaviors
|
|
49
|
+
|
|
50
|
+
4. **Generate Multiple Solutions**
|
|
51
|
+
- Brainstorm at least 3-5 different approaches
|
|
52
|
+
- For each approach, consider:
|
|
53
|
+
- Pros and cons
|
|
54
|
+
- Implementation complexity
|
|
55
|
+
- Resource requirements
|
|
56
|
+
- Potential risks
|
|
57
|
+
- Long-term implications
|
|
58
|
+
- Include both conventional and creative solutions
|
|
59
|
+
- Consider hybrid approaches
|
|
60
|
+
|
|
61
|
+
5. **Deep Dive Analysis**
|
|
62
|
+
For the most promising solutions:
|
|
63
|
+
- Create detailed implementation plans
|
|
64
|
+
- Identify potential pitfalls and mitigation strategies
|
|
65
|
+
- Consider phased approaches and MVPs
|
|
66
|
+
- Analyze second and third-order effects
|
|
67
|
+
- Think through failure modes and recovery
|
|
68
|
+
|
|
69
|
+
6. **Cross-Domain Thinking**
|
|
70
|
+
- Draw parallels from other industries or domains
|
|
71
|
+
- Apply design patterns from different contexts
|
|
72
|
+
- Consider biological or natural system analogies
|
|
73
|
+
- Look for innovative combinations of existing solutions
|
|
74
|
+
|
|
75
|
+
7. **Challenge and Refine**
|
|
76
|
+
- Play devil's advocate with each solution
|
|
77
|
+
- Identify weaknesses and blind spots
|
|
78
|
+
- Consider "what if" scenarios
|
|
79
|
+
- Stress-test assumptions
|
|
80
|
+
- Look for unintended consequences
|
|
81
|
+
|
|
82
|
+
8. **Synthesize Insights**
|
|
83
|
+
- Combine insights from all perspectives
|
|
84
|
+
- Identify key decision factors
|
|
85
|
+
- Highlight critical trade-offs
|
|
86
|
+
- Summarize innovative discoveries
|
|
87
|
+
- Present a nuanced view of the problem space
|
|
88
|
+
|
|
89
|
+
9. **Provide Structured Recommendations**
|
|
90
|
+
Present findings in a clear structure:
|
|
91
|
+
```
|
|
92
|
+
## Problem Analysis
|
|
93
|
+
- Core challenge
|
|
94
|
+
- Key constraints
|
|
95
|
+
- Critical success factors
|
|
96
|
+
|
|
97
|
+
## Solution Options
|
|
98
|
+
### Option 1: [Name]
|
|
99
|
+
- Description
|
|
100
|
+
- Pros/Cons
|
|
101
|
+
- Implementation approach
|
|
102
|
+
- Risk assessment
|
|
103
|
+
|
|
104
|
+
### Option 2: [Name]
|
|
105
|
+
[Similar structure]
|
|
106
|
+
|
|
107
|
+
## Recommendation
|
|
108
|
+
- Recommended approach
|
|
109
|
+
- Rationale
|
|
110
|
+
- Implementation roadmap
|
|
111
|
+
- Success metrics
|
|
112
|
+
- Risk mitigation plan
|
|
113
|
+
|
|
114
|
+
## Alternative Perspectives
|
|
115
|
+
- Contrarian view
|
|
116
|
+
- Future considerations
|
|
117
|
+
- Areas for further research
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
10. **Meta-Analysis**
|
|
121
|
+
- Reflect on the thinking process itself
|
|
122
|
+
- Identify areas of uncertainty
|
|
123
|
+
- Acknowledge biases or limitations
|
|
124
|
+
- Suggest additional expertise needed
|
|
125
|
+
- Provide confidence levels for recommendations
|
|
126
|
+
|
|
127
|
+
## Usage Examples
|
|
128
|
+
|
|
129
|
+
```bash
|
|
130
|
+
# Architectural decision
|
|
131
|
+
/ultra-think Should we migrate to microservices or improve our monolith?
|
|
132
|
+
|
|
133
|
+
# Complex problem solving
|
|
134
|
+
/ultra-think How do we scale our system to handle 10x traffic while reducing costs?
|
|
135
|
+
|
|
136
|
+
# Strategic planning
|
|
137
|
+
/ultra-think What technology stack should we choose for our next-gen platform?
|
|
138
|
+
|
|
139
|
+
# Design challenge
|
|
140
|
+
/ultra-think How can we improve our API to be more developer-friendly while maintaining backward compatibility?
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
## Key Principles
|
|
144
|
+
|
|
145
|
+
- **First Principles Thinking**: Break down to fundamental truths
|
|
146
|
+
- **Systems Thinking**: Consider interconnections and feedback loops
|
|
147
|
+
- **Probabilistic Thinking**: Work with uncertainties and ranges
|
|
148
|
+
- **Inversion**: Consider what to avoid, not just what to do
|
|
149
|
+
- **Second-Order Thinking**: Consider consequences of consequences
|
|
150
|
+
|
|
151
|
+
## Output Expectations
|
|
152
|
+
|
|
153
|
+
- Comprehensive analysis (typically 2-4 pages of insights)
|
|
154
|
+
- Multiple viable solutions with trade-offs
|
|
155
|
+
- Clear reasoning chains
|
|
156
|
+
- Acknowledgment of uncertainties
|
|
157
|
+
- Actionable recommendations
|
|
158
|
+
- Novel insights or perspectives
|
|
@@ -0,0 +1,209 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: senior-architect
|
|
3
|
+
description: Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Senior Architect
|
|
7
|
+
|
|
8
|
+
Complete toolkit for senior architect with modern tools and best practices.
|
|
9
|
+
|
|
10
|
+
## Quick Start
|
|
11
|
+
|
|
12
|
+
### Main Capabilities
|
|
13
|
+
|
|
14
|
+
This skill provides three core capabilities through automated scripts:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
# Script 1: Architecture Diagram Generator
|
|
18
|
+
python scripts/architecture_diagram_generator.py [options]
|
|
19
|
+
|
|
20
|
+
# Script 2: Project Architect
|
|
21
|
+
python scripts/project_architect.py [options]
|
|
22
|
+
|
|
23
|
+
# Script 3: Dependency Analyzer
|
|
24
|
+
python scripts/dependency_analyzer.py [options]
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
## Core Capabilities
|
|
28
|
+
|
|
29
|
+
### 1. Architecture Diagram Generator
|
|
30
|
+
|
|
31
|
+
Automated tool for architecture diagram generator tasks.
|
|
32
|
+
|
|
33
|
+
**Features:**
|
|
34
|
+
- Automated scaffolding
|
|
35
|
+
- Best practices built-in
|
|
36
|
+
- Configurable templates
|
|
37
|
+
- Quality checks
|
|
38
|
+
|
|
39
|
+
**Usage:**
|
|
40
|
+
```bash
|
|
41
|
+
python scripts/architecture_diagram_generator.py <project-path> [options]
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
### 2. Project Architect
|
|
45
|
+
|
|
46
|
+
Comprehensive analysis and optimization tool.
|
|
47
|
+
|
|
48
|
+
**Features:**
|
|
49
|
+
- Deep analysis
|
|
50
|
+
- Performance metrics
|
|
51
|
+
- Recommendations
|
|
52
|
+
- Automated fixes
|
|
53
|
+
|
|
54
|
+
**Usage:**
|
|
55
|
+
```bash
|
|
56
|
+
python scripts/project_architect.py <target-path> [--verbose]
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
### 3. Dependency Analyzer
|
|
60
|
+
|
|
61
|
+
Advanced tooling for specialized tasks.
|
|
62
|
+
|
|
63
|
+
**Features:**
|
|
64
|
+
- Expert-level automation
|
|
65
|
+
- Custom configurations
|
|
66
|
+
- Integration ready
|
|
67
|
+
- Production-grade output
|
|
68
|
+
|
|
69
|
+
**Usage:**
|
|
70
|
+
```bash
|
|
71
|
+
python scripts/dependency_analyzer.py [arguments] [options]
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
## Reference Documentation
|
|
75
|
+
|
|
76
|
+
### Architecture Patterns
|
|
77
|
+
|
|
78
|
+
Comprehensive guide available in `references/architecture_patterns.md`:
|
|
79
|
+
|
|
80
|
+
- Detailed patterns and practices
|
|
81
|
+
- Code examples
|
|
82
|
+
- Best practices
|
|
83
|
+
- Anti-patterns to avoid
|
|
84
|
+
- Real-world scenarios
|
|
85
|
+
|
|
86
|
+
### System Design Workflows
|
|
87
|
+
|
|
88
|
+
Complete workflow documentation in `references/system_design_workflows.md`:
|
|
89
|
+
|
|
90
|
+
- Step-by-step processes
|
|
91
|
+
- Optimization strategies
|
|
92
|
+
- Tool integrations
|
|
93
|
+
- Performance tuning
|
|
94
|
+
- Troubleshooting guide
|
|
95
|
+
|
|
96
|
+
### Tech Decision Guide
|
|
97
|
+
|
|
98
|
+
Technical reference guide in `references/tech_decision_guide.md`:
|
|
99
|
+
|
|
100
|
+
- Technology stack details
|
|
101
|
+
- Configuration examples
|
|
102
|
+
- Integration patterns
|
|
103
|
+
- Security considerations
|
|
104
|
+
- Scalability guidelines
|
|
105
|
+
|
|
106
|
+
## Tech Stack
|
|
107
|
+
|
|
108
|
+
**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin
|
|
109
|
+
**Frontend:** React, Next.js, React Native, Flutter
|
|
110
|
+
**Backend:** Node.js, Express, GraphQL, REST APIs
|
|
111
|
+
**Database:** PostgreSQL, Prisma, NeonDB, Supabase
|
|
112
|
+
**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI
|
|
113
|
+
**Cloud:** AWS, GCP, Azure
|
|
114
|
+
|
|
115
|
+
## Development Workflow
|
|
116
|
+
|
|
117
|
+
### 1. Setup and Configuration
|
|
118
|
+
|
|
119
|
+
```bash
|
|
120
|
+
# Install dependencies
|
|
121
|
+
npm install
|
|
122
|
+
# or
|
|
123
|
+
pip install -r requirements.txt
|
|
124
|
+
|
|
125
|
+
# Configure environment
|
|
126
|
+
cp .env.example .env
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
### 2. Run Quality Checks
|
|
130
|
+
|
|
131
|
+
```bash
|
|
132
|
+
# Use the analyzer script
|
|
133
|
+
python scripts/project_architect.py .
|
|
134
|
+
|
|
135
|
+
# Review recommendations
|
|
136
|
+
# Apply fixes
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
### 3. Implement Best Practices
|
|
140
|
+
|
|
141
|
+
Follow the patterns and practices documented in:
|
|
142
|
+
- `references/architecture_patterns.md`
|
|
143
|
+
- `references/system_design_workflows.md`
|
|
144
|
+
- `references/tech_decision_guide.md`
|
|
145
|
+
|
|
146
|
+
## Best Practices Summary
|
|
147
|
+
|
|
148
|
+
### Code Quality
|
|
149
|
+
- Follow established patterns
|
|
150
|
+
- Write comprehensive tests
|
|
151
|
+
- Document decisions
|
|
152
|
+
- Review regularly
|
|
153
|
+
|
|
154
|
+
### Performance
|
|
155
|
+
- Measure before optimizing
|
|
156
|
+
- Use appropriate caching
|
|
157
|
+
- Optimize critical paths
|
|
158
|
+
- Monitor in production
|
|
159
|
+
|
|
160
|
+
### Security
|
|
161
|
+
- Validate all inputs
|
|
162
|
+
- Use parameterized queries
|
|
163
|
+
- Implement proper authentication
|
|
164
|
+
- Keep dependencies updated
|
|
165
|
+
|
|
166
|
+
### Maintainability
|
|
167
|
+
- Write clear code
|
|
168
|
+
- Use consistent naming
|
|
169
|
+
- Add helpful comments
|
|
170
|
+
- Keep it simple
|
|
171
|
+
|
|
172
|
+
## Common Commands
|
|
173
|
+
|
|
174
|
+
```bash
|
|
175
|
+
# Development
|
|
176
|
+
npm run dev
|
|
177
|
+
npm run build
|
|
178
|
+
npm run test
|
|
179
|
+
npm run lint
|
|
180
|
+
|
|
181
|
+
# Analysis
|
|
182
|
+
python scripts/project_architect.py .
|
|
183
|
+
python scripts/dependency_analyzer.py --analyze
|
|
184
|
+
|
|
185
|
+
# Deployment
|
|
186
|
+
docker build -t app:latest .
|
|
187
|
+
docker-compose up -d
|
|
188
|
+
kubectl apply -f k8s/
|
|
189
|
+
```
|
|
190
|
+
|
|
191
|
+
## Troubleshooting
|
|
192
|
+
|
|
193
|
+
### Common Issues
|
|
194
|
+
|
|
195
|
+
Check the comprehensive troubleshooting section in `references/tech_decision_guide.md`.
|
|
196
|
+
|
|
197
|
+
### Getting Help
|
|
198
|
+
|
|
199
|
+
- Review reference documentation
|
|
200
|
+
- Check script output messages
|
|
201
|
+
- Consult tech stack documentation
|
|
202
|
+
- Review error logs
|
|
203
|
+
|
|
204
|
+
## Resources
|
|
205
|
+
|
|
206
|
+
- Pattern Reference: `references/architecture_patterns.md`
|
|
207
|
+
- Workflow Guide: `references/system_design_workflows.md`
|
|
208
|
+
- Technical Guide: `references/tech_decision_guide.md`
|
|
209
|
+
- Tool Scripts: `scripts/` directory
|