From contextune
Efficiently research topics using parallel agents via Contextune's /ctx:research command. Use when users ask to research, investigate, find information about topics, compare options, or evaluate libraries/tools. Activate for questions like "research best X", "what's the best library for Y", or "investigate Z".
npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin shakestzd-contextuneThis skill uses the workspace's default tool permissions.
Efficiently research topics using parallel agents via Contextune's `/ctx:research` command.
Orchestrates multi-agent research across web, codebase, and community sources for broad, mixed, or ambiguous analyze/investigate requests needing evidence synthesis.
Conducts structured research on best practices, technology evaluations, comparisons via source discovery, multi-tool gathering, synthesis, and cited reports.
Conducts deep research on topics, compares technologies, investigates libraries, and searches GitHub issues using gh CLI and Gemini AI synthesis.
Share bugs, ideas, or general feedback.
Efficiently research topics using parallel agents via Contextune's /ctx:research command.
This skill should be used when the user:
When activated, this skill executes the /ctx:research command which:
Spawns 3 parallel Haiku agents (~$0.07, 1-2 minutes):
Returns comprehensive research including:
/ctx:research [user's query]
Important: Pass the user's query verbatim to capture intent.
The command runs in background. You'll receive results from all 3 agents simultaneously.
Present results in this structure:
## Research Findings: [Topic]
### Summary
[1-2 sentence overview of landscape]
### Top Options
#### 1. [Option Name] ⭐ Recommended
- **Pros**: [key advantages]
- **Cons**: [key drawbacks]
- **Best for**: [use cases]
- **Adoption**: [community size, maturity]
#### 2. [Option Name]
[same structure]
#### 3. [Option Name]
[same structure]
### Implementation Examples
[Code snippets or links if available]
### Migration Considerations
- [Key steps to adopt]
- [Potential challenges]
- [Time/effort estimation]
### Recommendation
[Clear recommendation based on user's context]
User Query:
research best React state management libraries
Your Action:
/ctx:research best React state management libraries 2025
Expected Output After Agents Complete:
## Research Findings: React State Management (2025)
### Summary
The React state management landscape has matured significantly, with Zustand and Jotai emerging as modern alternatives to Redux, optimized for React 18+ features.
### Top Options
#### 1. Zustand ⭐ Recommended
- **Pros**:
- Minimal boilerplate (~1KB)
- TypeScript-first design
- No providers needed
- React 18 concurrent mode support
- **Cons**:
- Smaller ecosystem than Redux
- Less established patterns for large apps
- **Best for**: New projects, simple-medium complexity, teams wanting minimal setup
- **Adoption**: 40K+ GitHub stars, growing rapidly
#### 2. Jotai
- **Pros**:
- Atomic state model
- Excellent TypeScript inference
- Built for React 18
- **Cons**:
- Steeper learning curve (atomic concepts)
- Newer, less community content
- **Best for**: Complex state requirements, fine-grained reactivity
- **Adoption**: 15K+ stars, backed by Poimandres team
#### 3. Redux Toolkit
- **Pros**:
- Mature, massive ecosystem
- Excellent DevTools
- Industry standard
- **Cons**:
- More boilerplate
- Provider setup required
- **Best for**: Large teams, existing Redux codebases, need for middleware
- **Adoption**: 60K+ stars (core Redux), widely used in enterprise
### Recommendation
For your project, I recommend **Zustand** because:
- Modern codebase starting fresh
- Team values simplicity over complexity
- Don't need advanced middleware ecosystem
- Want TypeScript-first experience
Migration from existing useState: ~2-4 hours for typical app.
/ctx:research command for seamless executionIf /ctx:research fails:
/ctx:configure for setup