// Guidelines for using Context7, web search, and other research tools to find solutions outside the Scopy codebase. Loaded when the task involves unfamiliar technology or external libraries.
| name | external-research |
| description | Guidelines for using Context7, web search, and other research tools to find solutions outside the Scopy codebase. Loaded when the task involves unfamiliar technology or external libraries. |
Search outside the Scopy codebase when:
Primary source: https://analogdevicesinc.github.io
Use when: Task involves a specific ADI device, IIO driver attributes, hardware capabilities, or register maps.
Use Context7 or web search for:
Use when: Building UI components, choosing between Qt approaches, or using Qt classes not currently in the codebase.
Use web search for:
Use when: Working with IIO device communication, attribute reads/writes, or buffer management.
Use Context7 or web search for:
Use when: Task involves data streaming, signal processing pipelines, or extending gr-util.
Search GitHub for:
Use when: Need a reference implementation to understand an approach.
Use for:
Before recommending any external library or tool, check:
Scopy is LGPL-licensed. Compatible licenses:
When presenting external solutions, use this format:
### External Option: <library/tool name>
- **What it does:** <one sentence>
- **License:** <license name> — <compatible/caution/incompatible>
- **Platforms:** <list>
- **Source:** <URL>
- **Pros:**
- <advantage 1>
- <advantage 2>
- **Cons:**
- <disadvantage 1>
- <disadvantage 2>
- **Integration effort:** <low/medium/high> — <brief explanation>
- **Alternative:** <what we'd build if we don't use this>
Always present "build it ourselves" alongside external options so the user can make an informed choice.
Core Scopy architecture knowledge including plugin lifecycle, library dependencies, build system, and key design patterns. Loaded by clarify-task and design-task commands.
How Scopy libraries depend on each other, plugin commonalities, MessageBroker topics, shared widgets, style system flow, and build system relationships. Loaded when determining component interactions or change impact.
Decision trees for common Scopy architectural choices - plugin vs core, tool vs section, widget type selection, sync vs async, GNU Radio vs direct, package organization, and API exposure. Loaded when making design decisions.
Catalog of all Scopy development tools including package generator, testing tools, CI scripts, format/license scripts, and dev plugin commands. Loaded when analyzing what tools exist for a task.
Code patterns and examples for Scopy IIOWidget unit tests. Covers standard helpers, data-driven testing, and complex multi-step scenarios. Auto-loads when creating or reviewing `*_Unit_test.js` files.
Unit test validation rules for Scopy plugin IIOWidget tests. Auto-loads when reviewing or writing `*_Unit_test.js` files.