flix

Generate Flix code using design principles and standard library documentation.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/synapseradio/ai-skills --skill flix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flix
Source: https://github.com/synapseradio/ai-skills/tree/main/skills/flix
Command: npx skills add https://github.com/synapseradio/ai-skills --skill flix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of generating correct Flix code, especially for developers unfamiliar with its unique constraints and idioms, by providing context-aware guidance and anti-hallucination rules.

Core Features & Use Cases

  • Flix Design Principles: Loads and enforces Flix's 41 core design principles to prevent common errors.
  • Stdlib-First Discipline: Guides users to leverage the Flix standard library (api.flix.dev) before resorting to Java interop.
  • Translation References: Provides patterns for translating code from TypeScript, Python, and Rust to Flix.
  • Use Case: When asked to "write a Flix function to parse JSON", this Skill loads relevant documentation on effect systems, stdlib modules for string manipulation, and potential Java interop patterns if no direct Flix equivalent exists, ensuring the generated code adheres to Flix's purity and effect tracking rules.

Quick Start

Use the flix skill to write a Flix function that calculates the factorial of a number.

Frequently Asked Questions about flix

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

FAQPage Schema
How do I write correct Flix code when translating from TypeScript, Python, or Rust?

To write correct Flix code from TypeScript, Python, or Rust, use translation reference patterns that enforce Flix's 41 core design principles and prevent common errors. This ensures generated code adheres to language constraints and purity rules.

What is the best way to parse JSON in Flix without causing effect tracking errors?

Parsing JSON in Flix requires using stdlib-first discipline, loading modules for string manipulation and effect systems before resorting to Java interop. This approach ensures generated code adheres to Flix's purity and effect tracking rules.

Do I need to use Java interop if the Flix standard library lacks a specific function?

You only use Java interop when the Flix standard library lacks a direct equivalent. The skill enforces a stdlib-first discipline, guiding you to leverage Flix's standard library before falling back to Java interop patterns.

How does the Flix effect system work when generating functional programming code?

The Flix effect system works by enforcing purity and effect tracking rules during code generation. It loads relevant design constraints to prevent common errors, ensuring your functional programming code remains correct and compliant.

Why does my generated Flix code violate compiler constraints and how can I fix it?

Generated Flix code violates compiler constraints when ignoring the 41 core design principles. Fix it by loading context-aware guidance and anti-hallucination rules that enforce language principles and standard library usage.