What problem does it solve?
Adding new APIs to SkiaSharp requires coordinating C++ analysis, C API bindings, generated interop code, C# wrappers, native rebuilds, tests, and gallery samples across a repository with a git submodule, and mistakes like skipping the native build or editing generated files cause runtime failures.
Core Features & Use Cases
- Add Mode: A 10-phase workflow covering C++ API analysis, C API creation in the skia submodule, binding generation, C# wrapper design, native rebuild, tests, and gallery samples.
- Review Mode: A structured checklist that audits naming, Span overloads, properties vs methods, interop safety, test coverage, and sample quality, with an auto-fix mode for high-confidence issues.
- Use Case: When asked to expose SkFontArguments variation APIs, the skill walks through writing the C API in externals/skia, regenerating SkiaApi.generated.cs, adding Span-based C# wrappers, rebuilding natives, and verifying tests pass.
Quick Start
Ask the assistant to add a new SkiaSharp API wrapping a specific Skia C++ method, or to review an existing API pull request for design correctness.