Index of every page on this site: llms.txt
Avatar for Chelis Lang

Chelis Lang

The Chelis Programming Language

9 skills 5 Synced

chelis-lang/chelis

Turtles all the way down

9 skills 5
npx skilld add chelis-lang/chelis --all
  • Use for Chelis IR, backend, and autodiff work where numerical correctness matters. Focuses on evaluator-vs-backend agreement, compile-run harnesses, tolerances, and finite-difference checks.

  • Use when writing downstream Chelis Surf or Deep programs, validating Chelis examples, or authoring Reef shell packages that depend on the bundled chelis-std runtime. Not for modifying the Chelis compiler repository itself.

  • Use when changing or validating Chelis CLI behavior. Focuses on corpus-based testing for chelis fmt, surf, deep, check, eval, build, and tide, plus machine-facing output invariants.

  • Use when adding, moving, or validating Chelis example programs, and before writing any Surf (`.ch`) source, including fixtures and probes. Carries the Surf style rules, the parse-breaking spellings, and the Deep AST contract; preserves the executable-vs-illustrative split and keeps example-related tests honest.

  • Use when picking up, resolving, addressing, fixing, working, tackling, triaging, or closing out one or more GitHub issues (tickets, bug reports, feature requests) in chelis or a shell repo, whether referenced by number (#N) or URL or handed as a batch, and even when a PR already exists. Claims each issue via assignee (gh issue edit --add-assignee @me) before branching or writing any code so others can see it is in progress, scopes the work from the full issue thread (body and every comment), and links the PR with honest Closes/Part-of wording.

  • Use when changing or validating Chelis toolchain install, version routing, or the reef orchestration surface — chelisup (install/default/shim), the chelisup.sh bootstrap and its private-repo `gh` auth, chelis reef setup, and reef doctor. Covers the shim resolution order, the store layout, the shim-corruption trap, and the offline test seams.

  • Use when deciding whether a Chelis phase is actually complete. Applies the repo’s completion standard, checks manual gates, examples, docs, and phase-specific acceptance criteria before any completion claim.

  • Run a compliant Chelis red-team round, or send a local repair back to the standing reviewer for verification before push. A round starts with a fresh local subagent working an inline brief against the pushed head, then keeps that reviewer alive through the local repair loop. Anything else is not a red team.

  • Use when changing Chelis language behavior, CLI behavior, or compiler semantics. Keeps code, tests, examples, and active specs in sync in one change set.

Skills published by Chelis Lang. Checked GitHub just now