api-quality-checks
API class validation rules for Scopy plugins. Auto-loads when reviewing or editing `*_api.h` / `*_api.cpp` files or running API…
RST documentation conventions for Scopy plugins including heading styles, toctree syntax, image placeholders, and attribute table format. Auto-loads when writing RST documentation for Scopy plugins.
$ npx -y skills add analogdevicesinc/scopy --skill scopy-doc-format --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/scopy-doc-formatContext preview
The summary Claude sees to decide when to auto-load this skill.
RST documentation conventions for Scopy plugins including heading styles, toctree syntax, image placeholders, and attribute table format. Auto-loads when writing RST documentation for Scopy plugins.
name: scopy-doc-format description: RST documentation conventions for Scopy plugins including heading styles, toctree syntax, image placeholders, and attribute table format. Auto-loads when writing RST documentation for Scopy plugins.
Top-level title (80 = characters) ================================================================================ Section heading (dashes) --------------------------------- Subsection heading (tildes) ~~~~~~~~~~~~~~~~~~
The underline must be **at least as long** as the heading text.
.. _<plugin>: # Main doc file .. _<plugin>_index: # Index file .. _<plugin>_advanced: # Advanced doc file
Labels must be unique across the entire documentation tree.
.. toctree:: :maxdepth: 2 <plugin> <plugin>_advanced
Do NOT use `.. figure::` or `.. image::` directives. Use this comment format:
.. AN_IMAGE_WILL_BE_HERE Screenshot: <exact description of what to capture> e.g. "The RX Chain section showing hardware gain and sampling rate controls"
Place one placeholder:
- **Attribute Name:** One sentence description of what this attribute controls. - **Another Attribute:** Description without wiki links.
.. _<plugin>_index: <Device Name> ======================================== Overview -------- <One paragraph about the plugin.> Features -------- - **Feature 1:** Description Supported Devices ------------------- - **<Device Family>** (list variants) Getting Started --------------- **Prerequisites** - Hardware requirement - Scopy version X.Y or later .. toctree:: :maxdepth: 2 <plugin> <plugin>_advanced
When adding a new plugin, update `scopy/docs/plugins/index.rst`:
API class validation rules for Scopy plugins. Auto-loads when reviewing or editing `*_api.h` / `*_api.cpp` files or running API…
Guidelines for using Context7, web search, and other research tools to find solutions outside the Scopy codebase. Loaded when the…
How to create IIOWidgets for device attributes using IIOWidgetBuilder. Covers spinbox, combo, checkbox, and read-only patterns.…
API class conventions for Scopy plugins including ApiObject inheritance, Q_INVOKABLE patterns, and IIOWidgetGroup access.…
Core Scopy architecture knowledge including plugin lifecycle, library dependencies, build system, and key design patterns. Loaded…
How Scopy libraries depend on each other, plugin commonalities, MessageBroker topics, shared widgets, style system flow, and…