What problem does it solve? Flix compiler errors like parse failures, type unification errors, and non-exhaustive matches can be cryptic, especially when caused by language-specific pitfalls such as reserved words, misplaced Java imports, or missing Float32 suffixes. This Skill maps error output to a curated list of known pitfalls and produces concrete fixes. ## Core Features & Use Cases - Error-to-pitfall matching: Compares messages from flix check, flix test, or make against nine documented pitfalls (reserved words, import placement, Channel API, Java exception types, record update syntax, effect propagation, pattern exhaustiveness, literal type inference, Float32 suffixes). - API signature verification: Consults the engine's docs/api-digest.md (via make api Q=<name>) to confirm correct signatures before grepping source. - General diagnostic fallback: When no known pitfall matches, reads the error location, greps for type definitions and unresolved symbols, and proposes a fix verified with /verify. - Use Case: A build fails with Expected ',' before '=' on a record field named spawn; the Skill identifies the reserved-word pitfall and suggests renaming to start. ## Quick Start Run the compile-fix skill on this Flix compiler error output and tell me the cause and the fix.
