Overview of Context Types

Assembly supports various types of context, each serving different purposes in your development workflow. Understanding these types helps you maximize the value of context in your work.

Project Management Context

Jira & Linear Tickets

  • Ticket descriptions and requirements
  • Related subtasks and blockers
  • Comment threads and discussions
  • Status and priority tracking
  • Team and cycle information
  • Roadmap context

GitHub Issues

  • Issue descriptions
  • Labels and milestones
  • Discussion threads
  • Project board status
  • Related pull requests

GitLab Issues

  • Issue details
  • Epic relationships
  • Time tracking
  • Board positions
  • Merge request links

Code Context

Pull Requests

  • Code changes and diffs
  • Review comments
  • Branch information
  • CI/CD status
  • Linked issues

Source Files

  • Full code content
  • Local file sync
  • Syntax highlighting

Folder Structure

  • Directory layouts
  • File relationships
  • Resource organization

Documentation Context

Google Workspace

  • Google Docs
  • [Coming soon] Google Sheets
  • [Coming soon] Google Slides
  • [Coming soon] Comments and suggestions

Notion

  • [Coming soon] Pages and subpages
  • [Coming soon] Databases
  • [Coming soon] Templates
  • [Coming soon] Team wikis
  • [Coming soon] Project documentation

Web Resources

  • API documentation
  • Technical specs
  • Design documents
  • External references
  • Knowledge bases

Project Context

Repository Overview

  • A special AI generated document that provides a high-level overview of the repository
  • Generated by Assembly to provide a quick summary of the repository

Architecture

  • System diagrams
  • Component relationships
  • Data flows
  • Integration points
  • Infrastructure maps

Team Knowledge

  • Coding standards
  • Best practices
  • Team processes
  • Decision records
  • Meeting notes

Common Context Combinations

Effective development often requires combining multiple types of context to get a complete picture of the task at hand.

Feature Development

Required Context:

  • Project ticket (Jira/Linear)
  • Design documents (Notion/GDocs)
  • Related PRs
  • Architecture diagrams
  • Implementation guides

Optional Context:

  • Team discussions
  • Related features
  • Performance requirements

Bug Resolution

Required Context:

  • Bug ticket
  • Error logs
  • Affected code files
  • Test cases
  • Recent changes

Optional Context:

  • Similar past issues
  • Performance metrics
  • User reports

Next Steps

Learn About Context Retrieval

Discover how to efficiently bring different types of context into your Assembly workspace