Edict

How to develop the Edict compiler — architecture, coding patterns, structured error conventions, and how to add new features end-to-end. Use this skill when contributing to the Edict TypeScript codebase, adding new AST node types, implementing new builtins, extending the compiler pipeline, fixing bugs in the validator/resolver/checker/effects/contracts/codegen, or working on the MCP server. Also use when someone asks about Edict's architecture or how the compiler works.

How to write correct Edict JSON AST programs. Covers the AST format, node types, ID conventions, common patterns, and how to interpret and fix structured errors. Use this skill when writing Edict programs, creating example programs, producing JSON ASTs for the Edict compiler, demonstrating language features, or debugging AST validation/type/effect errors. Also use when an agent needs to produce Edict code via MCP tools like edict_validate, edict_check, edict_compile, or edict_run.

How to write and run tests for the Edict compiler. Covers vitest conventions, test directory structure, patterns for testing each pipeline stage, structured error assertions, and coverage expectations. Use this skill when writing tests, fixing failing tests, adding coverage for new features, or understanding the test suite organization. Also use when asked about test patterns, how to test a specific compiler stage, or when investigating test failures.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.