fix-int

Fix fl:: integer type mappings in platform-specific int headers.

7.5k|1.8k|Updated Nov 10, 2013
One-click install
npx skills add https://github.com/FastLED/FastLED --skill fix-int
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-int
Source: https://github.com/FastLED/FastLED/tree/main/.claude/skills/fix-int
Command: npx skills add https://github.com/FastLED/FastLED --skill fix-int

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and fix primitive integer type definitions for a specified platform (fl::i8, fl::u8, fl::i16, fl::u16, fl::i32, fl::u32, fl::i64, fl::u64) to ensure correct type mappings across toolchains.

Core Features & Use Cases

  • Research correct primitive type mappings needed for the target platform.
  • Apply fixes to platform-specific int headers under src/platforms/**/int*.h while preserving protected headers.
  • Use in cross-platform embedded projects to guarantee consistent integer widths across compilers.

Quick Start

Provide the target platform as an argument and run the fix-int procedure to update the platform-specific int headers.

Frequently Asked Questions about fix-int

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix platform-specific integer type mappings for embedded cross-platform projects?

To fix integer type mappings, apply platform-specific corrections to header files under src/platforms/**/int*.h, ensuring primitive types like fl::i8 and fl::u32 align correctly across toolchains. You provide the target platform argument to update the headers.

Why do my primitive integer types mismatch across different embedded compilers?

Primitive integer types mismatch across compilers because default type widths vary by platform toolchain. Correcting the platform-specific int headers under src/platforms/**/int*.h guarantees consistent integer widths and resolves these cross-platform mapping discrepancies.

When do I need to update platform-specific int headers in my source tree?

You need to update platform-specific int headers when adding a new target platform or experiencing type width inconsistencies across toolchains. Running the fix procedure targets files under src/platforms/**/int*.h to enforce correct type mappings.

How do I safely modify integer type definitions without breaking protected headers?

To safely modify integer type definitions, apply corrections only to platform-specific int headers under src/platforms/**/int*.h. The process explicitly avoids modifications to protected headers, ensuring system constraints from SKILL.md are enforced during the update.

Can I use this to align fl::i64 and fl::u8 types for a specific target platform?

Yes, you can align fl::i64, fl::u8, and other primitive integer types by providing the target platform as an argument. The procedure researches and applies the correct platform-specific mappings to the relevant header files.

What are the limitations when correcting platform-specific integer type definitions?

A key limitation is that corrections must avoid modifying protected headers entirely. Additionally, you must provide a valid target platform argument and adhere to the strict constraints listed in the SKILL.md file to execute the header updates successfully.