github.com/FastLED/FastLED (link)

commit signals (1023)

source signals (92)

• GEMINI.mdvia gemini

  # READ CLAUDE.md for repo information

• .coderabbit.yamlvia coderabbits

  reviews:
    request_changes_workflow: true
    pre_merge_checks:
      enabled: true
  
    # Per-path natural-language review instructions.
    # See https://docs.coderabbit.ai/getting-started/configure-coderabbit
    path_instructions:
      - path: "src/fl/channels/bus.h"
        instructions: |
          Bus enum additions and parallel-IO peripheral driver rule. Flag any
          PR that adds a new `Bus::X_SPI` enum value (e.g. `Bus::FLEX_IO_SPI`,
          `Bus::OBJECT_FLED_SPI`, `Bus::PARLIO_SPI`, `Bus::LCD_CAM_SPI`) for
   

• .cursorrulesvia cursor

  # FastLED Project Rules for Cursor
  
  ## 🚨 CRITICAL: PYTHON EXECUTION REQUIREMENTS - NO EXCEPTIONS! 🚨
  
  ### MANDATORY COMMAND EXECUTION RULES - ALL AGENTS MUST FOLLOW
  
  **🚨 ABSOLUTELY FORBIDDEN: Direct python/python3 execution**
  - ❌ **NEVER use:** `python3 <command>`
  - ❌ **NEVER use:** `python <command>`  
  - ❌ **NEVER use:** `./python`
  - ❌ **NEVER use:** Direct Python interpreter calls
  
  **✅ MANDATORY: Always use uv run**
  - ✅ **ALWAYS use:** `uv run python <command>`
  - ✅ **ALWAYS use:** `u

• .cursorignorevia cursor

  # Cursor ignore file - excludes files/directories from Cursor's indexing and search
  
  # Build directories
  .build/
  build/
  out/
  
  
  # Cache directories
  .cache/
  __pycache__/
  .pytest_cache/
  .ruff_cache/
  .mypy_cache/
  
  # Temporary directories
  tmp/
  temp/
  ignore/
  
  # Environment
  .venv/
  .env
  
  # Other build outputs
  dist/
  firmware_sizes.csv
  

• .cursordirectoryvia cursor
• CODEX.mdvia codex

  Read `CLAUDE.md` for all agent instructions.
  

• .cursor/mcp.jsonvia unspecified

  {
    "mcpServers": {
      "fastled": {
        "command": "uv",
        "args": ["run", "mcp_server.py"],
        "env": {
          "PYTHONPATH": "."
        }
      }
    }
  } 

• .claude/skills/fix-int/SKILL.mdvia unspecified

  ---
  name: fix-int
  description: Fix integer type definitions for specified platform. Researches correct primitive type mappings and applies fixes to platform-specific int headers.
  argument-hint: <platform>
  disable-model-invocation: true
  context: fork
  agent: fix-int-agent
  ---
  
  Research and fix integer type definitions (fl::i8, fl::u8, fl::i16, fl::u16, fl::i32, fl::u32, fl::i64, fl::u64) for the specified platform.
  
  Platform: $ARGUMENTS
  
  Research the correct primitive type mappings for the target platform and

• .claude/skills/esp32-log-triage/SKILL.mdvia unspecified

  ---
  name: esp32-log-triage
  description: Parse and classify ESP32 serial log output to identify FastLED-related errors, RMT/I2S/SPI driver faults, timing violations, RTOS issues, and crash signatures. Use when debugging unexpected device behavior, boot failures, or LED output problems on ESP32.
  argument-hint: <paste serial log output or describe the symptom>
  context: fork
  agent: esp32-log-triage-agent
  ---
  
  Systematically analyze ESP32 serial log output to identify and classify issues, with special focus on F

• .claude/skills/lint/SKILL.mdvia unspecified

  ---
  name: lint
  description: Run code linting and formatting checks across the codebase. Use after modifying source files to ensure coding standards are met.
  context: fork
  agent: lint-agent
  ---
  
  Run linting and formatting checks across the codebase using `bash lint`.
  
  Report results in a clear, actionable format showing any formatting or linting violations found.
  
  For JavaScript files, also run `bash lint --js`.
  

• .claude/skills/code-review/SKILL.mdvia unspecified

  ---
  name: code-review
  description: Review staged and unstaged code changes for FastLED coding standards violations, span usage mandates, and example quality. Use after making code changes to ensure compliance.
  disable-model-invocation: true
  ---
  
  # Code Review Agent
  
  You are a specialized code review agent for FastLED. Review staged and unstaged changes according to strict rules.
  
  ## Your Task
  1. Run `git diff --cached` to see staged changes
  2. Run `git diff` to see unstaged changes
  3. Review ALL changes aga

• .claude/skills/memory-audit/SKILL.mdvia unspecified

  ---
  name: memory-audit
  description: Audit embedded code for stack overflow risks, heap fragmentation, static allocation patterns, and memory leaks. Use when investigating OOM crashes, optimizing memory usage, or reviewing memory-critical code on constrained devices.
  argument-hint: <file, directory, or component to audit>
  context: fork
  agent: memory-audit-agent
  ---
  
  Audit code for memory safety issues specific to resource-constrained embedded systems.
  
  $ARGUMENTS
  
  ## What This Skill Analyzes
  
  ### Stack Usage

• .claude/skills/gh-healthcheck/SKILL.mdvia unspecified

  ---
  name: gh-healthcheck
  description: Run health check on GitHub Actions workflow with root cause analysis and recommendations. Use for quick CI status overview and pattern analysis.
  argument-hint: [--workflow build.yml] [--run-id <id>] [--detail low|medium|high]
  context: fork
  ---
  
  Analyze GitHub Actions workflow health and provide a comprehensive diagnostic report.
  
  Arguments: $ARGUMENTS
  
  Run the health check tool:
  ```bash
  uv run ci/tools/gh/gh_healthcheck.py $ARGUMENTS
  ```
  
  ## Features
  
  **Root Cause Analy

• .claude/skills/timing-analysis/SKILL.mdvia unspecified

  ---
  name: timing-analysis
  description: Analyze real-time constraints, ISR latency, DMA transfer times, and LED protocol timing for embedded systems. Use when debugging timing-sensitive code, optimizing frame rates, or verifying protocol compliance.
  argument-hint: <component, function, or timing issue to analyze>
  context: fork
  agent: timing-analysis-agent
  ---
  
  Analyze timing-critical code paths for real-time constraint violations and optimization opportunities.
  
  $ARGUMENTS
  
  ## What This Skill Analyzes
  
  ### L

• .claude/skills/code-review-asm-xtensa/SKILL.mdvia unspecified

  ---
  name: code-review-asm-xtensa
  description: Review Xtensa assembly code for ESP32 platforms. Checks for critical errors in inline assembly, ABI compliance, and optimization opportunities. Use after modifying ESP32 assembly or inline asm code.
  disable-model-invocation: true
  context: fork
  agent: code_review_asm_xtensa-agent
  ---
  
  Perform comprehensive manual review of Xtensa assembly code in FastLED ESP32 platforms for correctness, ABI compliance, safety, and performance.
  
  ## What Gets Checked
  
  ### Critical 

• .claude/skills/test/SKILL.mdvia unspecified

  ---
  name: test
  description: Run test suite and report results. Use when running unit tests, integration tests, or verifying code changes pass all tests.
  argument-hint: [test-name] [--cpp] [--clean] [--run platform]
  context: fork
  agent: test-agent
  ---
  
  Run tests using `uv run test.py` with optional arguments.
  
  Arguments: $ARGUMENTS
  
  Use `bash test` wrapper (NEVER bare `python`). Common invocations:
  - `bash test` — run all tests
  - `bash test --cpp` — run only C++ tests
  - `bash test TestName` — run a spe

• .claude/skills/code-review-riscv/SKILL.mdvia unspecified

  ---
  name: code-review-riscv
  description: Review RISC-V assembly code for correctness, ABI compliance, and best practices. Use after modifying RISC-V assembly or inline asm code.
  disable-model-invocation: true
  context: fork
  agent: riscv-review-agent
  ---
  
  Review RISC-V assembly code for correctness, adherence to conventions, and best practices.
  
  The review covers 8 analysis categories:
  1. **Instruction correctness**: Valid syntax, proper operands, immediate ranges
  2. **Register conventions**: ABI compliance, 

• .claude/skills/new-cpp-lint/SKILL.mdvia unspecified

  ---
  name: new-cpp-lint
  description: Create a new C++ lint rule, test it, run it across the codebase, and selectively apply fixes. Usage - /new-cpp-lint <rule description>
  argument-hint: <rule description, e.g. "no raw new/delete — use fl::unique_ptr" or "all functions must use FL_NOEXCEPT">
  context: fork
  agent: cpp-linter-builder-agent
  ---
  
  # Create New C++ Lint Rule
  
  You are creating a new C++ lint rule for the FastLED codebase. The default home for the new rule is the Rust crate `ci/lint_cpp_rs/`; the l

• .claude/skills/embedded-debug/SKILL.mdvia unspecified

  ---
  name: embedded-debug
  description: Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms. Use when debugging device crashes, panics, guru meditation errors, hard faults, or analyzing core dumps.
  argument-hint: <crash output or description of the issue>
  context: fork
  agent: embedded-debug-agent
  ---
  
  Analyze firmware crash output, decode stack traces, and diagnose embedded system failures.
  
  $ARGUMENTS
  
  ## What This Skill Does
  
  1. **Crash Analysis**: Parse p

• .claude/skills/git-historian/SKILL.mdvia unspecified

  ---
  name: git-historian
  description: Search codebase and git history for keywords. Use when investigating code changes, finding where features were added, or tracking down when bugs were introduced.
  argument-hint: <keyword1> [keyword2] [...] [--paths dir1 dir2]
  ---
  
  Search the codebase and git history for the specified keywords.
  
  Arguments: $ARGUMENTS
  
  This command searches both:
  1. Working tree files (current code state)
  2. Git history (last 10 commits' diffs)
  
  Usage examples:
  - `/git-historian LED strip`
  

• .claude/skills/fix-board/SKILL.mdvia unspecified

  ---
  name: fix-board
  description: Automatically diagnose and fix board upload/monitor issues. Runs three-phase device workflow (Compile, Upload, Monitor) and applies fixes.
  disable-model-invocation: true
  context: fork
  agent: fix-board-agent
  ---
  
  Automatically run the three-phase device workflow (Compile, Upload, Monitor), diagnose any failures, and apply fixes.
  
  1. **Compile**: Run compilation using `uv run ci/debug_attached.py` (compile phase only)
  2. **Upload**: Execute upload with automatic port conflict 

• .claude/skills/gh-debug/SKILL.mdvia unspecified

  ---
  name: gh-debug
  description: Debug GitHub Actions build failures by fetching and analyzing workflow logs. Use when CI/CD pipelines fail and you need to identify the root cause.
  argument-hint: [run-id or workflow-url]
  context: fork
  ---
  
  Pull GitHub Actions logs for a workflow run, parse them to identify errors, and provide a clear diagnostic report.
  
  Arguments: $ARGUMENTS
  
  **Primary Method (Recommended)**: Use the Python script for efficient log analysis:
  ```bash
  uv run ci/tools/gh_debug.py $ARGUMENTS
  ```

• .claude/skills/driver-review/SKILL.mdvia unspecified

  ---
  name: driver-review
  description: Review and implement hardware driver code — DMA safety, interrupt correctness, timing constraints, peripheral register usage, channel drivers, and peripheral mock implementations. Use when writing, modifying, or reviewing LED drivers, SPI/I2S/RMT/UART/PARLIO/LCD_CAM peripherals, GPIO configuration, or peripheral mock code.
  disable-model-invocation: true
  ---
  
  # Hardware Driver Review & Implementation Guide
  
  Review and implement hardware driver code changes for embedded-

• .claude/skills/platform-port/SKILL.mdvia unspecified

  ---
  name: platform-port
  description: Guide porting FastLED to new MCU platforms, including int.h types, clockless drivers, SPI implementations, and platform detection. Use when adding support for a new microcontroller family or board.
  argument-hint: <target platform name, e.g., "STM32H7", "RP2040", "nRF52840">
  context: fork
  agent: platform-port-agent
  ---
  
  Guide the process of porting FastLED to a new microcontroller platform.
  
  $ARGUMENTS
  
  ## What This Skill Covers
  
  ### Platform Detection Setup
  - Create plat

• .claude/skills/esp32-arch-review/SKILL.mdvia unspecified

  ---
  name: esp32-arch-review
  description: Review ESP32 FastLED firmware architecture for RTOS safety, DMA correctness, LED driver patterns, memory management, and peripheral safety. Use before merging significant driver changes, new platform ports, or when auditing existing ESP32 FastLED code.
  argument-hint: <file, directory, or component to review>
  context: fork
  agent: esp32-arch-review-agent
  ---
  
  Perform a structured architecture review of ESP32 firmware code, with emphasis on FastLED driver patterns, DMA 

• .claude/skills/tdd-implement/SKILL.mdvia unspecified

  ---
  name: tdd-implement
  description: Implement a feature or fix a bug using strict TDD. Analyzes the requirement, creates tests first, implements minimal code, then refactors. Use for feature requests, bug fixes, or enhancements that need test coverage.
  argument-hint: <feature request, bug description, or issue reference>
  context: fork
  agent: test-writer-agent
  ---
  
  # TDD Implementation — Feature-Driven Test-First Development
  
  You are implementing a feature or fixing a bug using strict Test-Driven Developm

• .claude/skills/esp32-test-plan/SKILL.mdvia unspecified

  ---
  name: esp32-test-plan
  description: Generate a structured multi-layer test plan for FastLED changes targeting ESP32. Covers host unit tests, WASM compile checks, platform compile checks, and hardware validation. Use after defining an implementation contract, before writing any code.
  argument-hint: <feature or change description>
  context: fork
  agent: esp32-test-plan-agent
  ---
  
  Generate a comprehensive test plan for a FastLED ESP32 change, covering all applicable testing layers from host logic to hardware 

• .claude/skills/expert-rmt5/SKILL.mdvia unspecified

  ---
  name: expert-rmt5
  description: ESP-IDF v5.x RMT5 API expert for LED protocols, encoders, and multi-channel control. Use when working with RMT peripheral programming, LED strip control, or migrating from RMT4 to RMT5.
  context: fork
  agent: expert-rmt5-agent
  ---
  
  Get expert guidance on ESP-IDF v5.x RMT (Remote Control Transceiver) peripheral programming.
  
  $ARGUMENTS
  
  ## What This Expert Covers
  
  ### Implementation & Design
  - **LED Strip Control**: WS2812, SK6812, APA106, and custom LED protocols
  - **Encoder

• .claude/skills/address-reviews/SKILL.mdvia unspecified

  ---
  name: address-reviews
  description: Fetch CodeRabbit review comments on the current PR, classify each finding, apply fixes for valid issues, and reply to each thread. Use before attempting gh pr merge when CodeRabbit has posted a review. Blocks merge on unresolved threads. Routes security-critical findings to a human.
  argument-hint: [pr-number, optional — defaults to PR for current branch]
  context: fork
  ---
  
  Address CodeRabbit review comments on a PR end-to-end: fetch, classify, fix, reply, commit, pus

• .claude/skills/ci-fix/SKILL.mdvia unspecified

  ---
  name: ci-fix
  description: Scan all CI builds and tests, find failures, fetch error logs, and fix the code. Prioritizes unit tests, example tests, then uno, attiny85, esp32s3, esp32c6, teensy41. Use when CI is red and you need to diagnose and repair build/test failures.
  argument-hint: [--board <name>] [--all]
  context: fork
  ---
  
  Find and fix CI build and test failures across all platforms.
  
  Arguments: $ARGUMENTS
  
  ## Step 1: Scan builds and get error logs
  
  Run the CI build scanner to discover all failing b

• .claude/skills/feature-contract/SKILL.mdvia unspecified

  ---
  name: feature-contract
  description: Generate a structured implementation contract before making any code changes to FastLED. Defines scope, affected files, API changes, platform impact, risk assessment, and test plan. Use before implementing any feature, bug fix, driver addition, or refactoring.
  argument-hint: <feature or bug description>
  context: fork
  agent: feature-contract-agent
  ---
  
  Generate an implementation contract for a FastLED change. The contract must be reviewed before any code is written.
  
  $

• .claude/skills/tdd/SKILL.mdvia unspecified

  ---
  name: tdd
  description: Guide Test-Driven Development workflow for FastLED. Use when implementing new features or fixing bugs with a test-first approach. Enforces Red-Green-Refactor discipline with FastLED test conventions.
  argument-hint: <feature or bug description>
  context: fork
  agent: test-writer-agent
  ---
  
  # TDD Workflow — Red-Green-Refactor for FastLED
  
  You are guiding a Test-Driven Development cycle. Follow the strict Red-Green-Refactor discipline.
  
  ## Input
  
  $ARGUMENTS
  
  ## Phase 1: RED — Write

• CLAUDE.mdvia claude-code

  # FastLED AI Agent Guidelines
  
  ## Read the Right File for Your Task
  
  **By what you're doing:**
  
  | Task | Read |
  |------|------|
  | Writing/editing C++ code | `agents/docs/cpp-standards.md` |
  | Verifying a peripheral exists on a chip before writing driver code | `agents/docs/peripheral-existence.md` (halt on phantom — do not fabricate missing `<Peripheral>_Type` in vendor headers) |
  | Adding or changing a board USB VID/PID | `agents/docs/usb-vid-pid-registry.md` (it lands in FastLED/boards first — never a

• .github/workflows/claude.ymlvia claude-code

  name: Claude Code
  
  on:
    issue_comment:
      types: [created]
    pull_request_review_comment:
      types: [created]
    issues:
      types: [opened, assigned]
    pull_request_review:
      types: [submitted]
  
  jobs:
    claude:
      # Security: only trigger when the @claude mention comes from a trusted
      # actor (repo OWNER, org MEMBER, or invited COLLABORATOR). Without this
      # gate, any external contributor could open a PR from a fork, comment
      # `@claude please fix` on it, and force the workflow to check out t

• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• .claudedirectoryvia claude-code
• ci/tools/.claudedirectoryvia claude-code

ignorefile signals (3)