Skip to main content

Research Commands

Research commands in AIKit enable you to gather external information from documentation, code examples, and community resources.

Available Commands

CommandDescriptionUse Case
/researchDeep research on a topic with documentationLearnings, examples, and best practices
/analyze-projectAnalyze project structure, architecture, and patternsUnderstand codebase organization
/review-codebaseReview codebase for quality issues, patterns, and improvementsConduct code review
/designDesign architecture, features, or workflows following AIKit design principles
/brainstormBrainstorm ideas, solutions, or approaches for problemsGenerate multiple creative solutions

Command Reference

/research

See: /research**

/analyze-project

See: /analyze-project**

/review-codebase

See: /review-codebase**

/design

See: /design**

/brainstorm

See: /brainstorm**

How to Use Research Commands

1. Define Research Question

# Clear, specific question
/research "What are JWT best practices for token refresh?"

2. Execute Research

AIKit will:

  • Search official documentation
  • Find community resources
  • Identify multiple approaches
  • Compare solutions
  • Document findings with evidence

3. Evaluate Options

AIKit provides:

  • Comparison table of different approaches
  • Pros and cons for each
  • Recommendations based on your project context

4. Save Findings

Save research to memory for future reference:

> memory_update("research/jwt-refresh", finded approach: sliding window pattern")

Research Workflow

graph LR
    A[Research Question] --> B[Documentation Research]
    A --> C[Community Resources]
    B --> D[Code Analysis]
    C --> E[Evaluation]
    D --> F[Decision]
    E --> G[Findings Saved]
    C --> H[Documentation Update]

Research Categories

Technical Research

  • Library/framework documentation
  • API documentation
  • Implementation patterns
  • Best practices
  • Code examples
  • Architecture patterns

Project Research

  • Codebase analysis
  • Pattern identification
  • Architecture review
  • Documentation review
  • Test coverage analysis

Market Research

  • Competitor analysis
  • Industry trends
  • Best practices in similar projects
  • User needs assessment

Best Practices

Before Researching

✅ DO:

  • Define clear research question
  • Set research goals
  • Identify authoritative sources
  • Note constraints and requirements

❌ DON'T:

  • Research vague topics
  • Skip official documentation
  • Use only community resources
  • Ignore your project context

During Researching

✅ DO:

  • Verify information currency
  • Cross-reference multiple sources
  • Note publication dates
  • Consider project context

❌ DON'T:

  • Accept first source as truth
  • Use outdated information
  • Skip critical thinking
  • Ignore alternative approaches

After Researching

✅ DO:

  • Summarize key findings
  • Provide evidence-backed recommendations
  • Save to memory for future reference
  • Note conflicting information
  • Document your reasoning

❌ DON'T:

  • Leave findings undocumented
  • Forget to note conflicting approaches
  • Make recommendations without evidence
  • Skip follow-up actions