analogdevicesinc
- 22 skills
- 0 followers
- 10 hours ago last updated
- ▌ Git Merge Release · analogdevicesincMerge release branches into main for libaditof and ADCAM repositories. Use when: updating main with release branch changes, creating PR branches for release merges, rebasing release branches, handling git branch operations for releases (rel-*.*.*, dev-*.*.*), syncing development with release branches.
- ▌ Pyadi Dt CLI · analogdevicesinc bundleUse the pyadi-dt adidtc CLI to inspect, generate, validate, and safely deploy Analog Devices Linux device trees. Trigger for Vivado XSA-to-DTS generation, built-in board profiles, Kuiper support discovery, DTS include analysis, local DTB inspection, live-board property reads, SD-card updates, or pyadi-jif clock updates.
- ▌ Cfs CLI · analogdevicesincProvides guidance on using the CFSUtil command-line tool for CodeFusion Studio. USE FOR cfsutil commands, generating code from .cfsconfig files, generating workspace configuration files and creating CFS workspaces, regenerating projects in a workspace, listing, querying, or exporting SoC data models, installing and managing packages and SDKs, analyzing and querying ELF files, building, profiling, and checking compatibility of AI models, generating workspaces from AI models, updating or restoring the SoC catalog, device tree parsing, pulling Docker images, myAnalog authentication including API keys (creating, listing, and revoking a myAnalog apikey) for headless CI/CD and non-interactive login, serial port info, listing and running workspace tasks, and listing available CFS plugins (with IDs and configuration options).
- ▌ Cfs Docs · analogdevicesinc bundleAnswer questions about CodeFusion Studio (CFS) by reading the relevant documentation. Use whenever someone asks how to install, set up, use, or troubleshoot CFS — including the VS Code extension, cfsutil CLI, System Planner, debug driver installation and hardware connection (J-Link, Olimex, ICE), build/flash/debug workflows, AI model integration, package manager, plugins, or release notes. Good for customers, new hires, and developers who want doc-backed answers without leaving the terminal.
- ▌ No Os Contribute · analogdevicesincContribution rules for the no-OS repository. Read and apply this BEFORE writing a commit, opening a pull request, or finalizing changes to no-OS. Covers required commit trailers (Assisted-by before Signed-off-by), the 50/72 commit-message rule, the path-prefix subject convention, and the astyle/gcc checks maintainers enforce. Triggers whenever you are about to commit or contribute code to no-OS. Also invocable on demand via /no-os-contribute.
- ▌ No Os Driver Readme · analogdevicesincWrite or update a no-OS device driver README.rst following the repo's standard driver-documentation structure. Use when creating documentation for a driver under drivers/<category>/<part>/, updating an existing driver README, or wiring a driver doc into the Sphinx toctree.
- ▌ No Os Project Readme · analogdevicesincWrite or update a no-OS project README.rst following the repo's standard structure and the current CMake/no_os_build.py build conventions. Use when creating documentation for a project under projects/<name>/, updating an existing project README, or aligning a README with the CMake build-guide cross-linking conventions.
- ▌ Scopy Doc Format · analogdevicesincRST 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.
- ▌ External Research · analogdevicesincGuidelines 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.
- ▌ Scopy Style Rules · analogdevicesinc bundleScopy styling system patterns including Style::setStyle, theme colors, section backgrounds, and widget styling. Auto-loads when applying styling to scopy widgets or sections.
- ▌ Scopy Test Format · analogdevicesincTest case conventions for Scopy plugins including UID format, RBP priorities, RST test entry templates, and standard test sequences. Auto-loads when writing test case documentation or automated test scripts.
- ▌ API Quality Checks · analogdevicesincAPI class validation rules for Scopy plugins. Auto-loads when reviewing or editing `*_api.h` / `*_api.cpp` files or running API quality checks.
- ▌ Iiowidget Patterns · analogdevicesinc bundleHow to create IIOWidgets for device attributes using IIOWidgetBuilder. Covers spinbox, combo, checkbox, and read-only patterns. Auto-loads when creating IIOWidgets, mapping attributes, or building plugin UI.
- ▌ Scopy API Patterns · analogdevicesincAPI class conventions for Scopy plugins including ApiObject inheritance, Q_INVOKABLE patterns, and IIOWidgetGroup access. Auto-loads when writing API classes or implementing test automation interfaces.
- ▌ Unit Test Patterns · analogdevicesinc bundleCode 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.
- ▌ Scopy Plugin Patterns · analogdevicesinc bundleStandard scopy plugin patterns including ToolTemplate, refresh buttons, sections, plugin lifecycle, and architecture. Auto-loads when creating plugin scaffolds, tool classes, or section layouts.
- ▌ Scopy Tools Inventory · analogdevicesincCatalog 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.
- ▌ Unit Test Quality Checks · analogdevicesincUnit test validation rules for Scopy plugin IIOWidget tests. Auto-loads when reviewing or writing `*_Unit_test.js` files.
- ▌ Scopy Decision Frameworks · analogdevicesincDecision 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.
- ▌ Scopy Architecture Knowledge · analogdevicesincCore Scopy architecture knowledge including plugin lifecycle, library dependencies, build system, and key design patterns. Loaded by clarify-task and design-task commands.
- ▌ Scopy Component Relationships · analogdevicesincHow 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.
- ▌ Test Automation Quality Checks · analogdevicesincJS automated test validation rules for Scopy plugins. Auto-loads when reviewing or writing test automation scripts in `js/testAutomations/`.