Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

jai-language

Estrelas1

Forks0

Atualizado19 de junho de 2026 às 20:51

Comprehensive Jai programming language reference and cheat sheet. Use when working with Jai code, tree-sitter-jai grammar development, or answering questions about Jai syntax and semantics. Covers declarations, types, control flow, directives, metaprogramming, and all language features. Trigger: user mentions 'Jai', 'Jai language', 'tree-sitter-jai', or asks about Jai syntax.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

corruptmemory

corruptmemory/claude-stuff

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

26 arquivos

SKILL.md

readonly

name	jai-language
description	Comprehensive Jai programming language reference and cheat sheet. Use when working with Jai code, tree-sitter-jai grammar development, or answering questions about Jai syntax and semantics. Covers declarations, types, control flow, directives, metaprogramming, and all language features. Trigger: user mentions 'Jai', 'Jai language', 'tree-sitter-jai', or asks about Jai syntax.

Jai Language Reference

Complete reference for the Jai programming language by Jonathan Blow.

The Jai compiler distribution at ~/jai/jai/ contains the authoritative source:

how_to/ — 80 .jai files across subdirectories covering all features
examples/ — Real-world programs
modules/ — Standard library

See references/cheatsheet.md for the full language cheat sheet. See compendium/ for compilable code samples demonstrating every language feature (19 files). See references/build-variables-recipe.md for the canonical metaprogram recipe for custom compile-time build variables (#placeholder knobs module + Message_Import-scoped add_build_string) — including the beta 0.2.029 gated-#load bug the naive per-file injection hits. Use this recipe whenever a metaprogram needs to feed constants into target code.

Compendium verification requirement

Every compendium .jai file must compile without errors or warnings against the current Jai compiler. When updating the skill for a new Jai release:

Bump version headers in the cheatsheet and all compendium files.
Reconcile changelog changes with skill content (removed features, new syntax, etc.).
Compile every compendium file with ~/jai/jai/bin/jai-linux <file>.jai and confirm zero errors.
Clean up build artifacts (rm -rf .build in the compendium directory).

Do not mark a version as verified until compilation is confirmed. The compendium is a "known good" corpus — if it doesn't compile, the version stamp is a lie.

Mais deste repositório

mesmo repositório

interface-first

corruptmemory/claude-stuff

Design around contracts, not implementations. Use when: (1) building multi-step features where placeholders would otherwise accumulate, (2) expensive or stateful objects need mock and real implementations (databases, caches, external services), (3) scaling fault lines exist where in-proc vs. remote implementations should be swappable, (4) test mocks need to verify behavior through observation hooks, (5) designing a system that may need to scale from single-process to distributed without a rewrite, (6) the user mentions 'interface first', 'mock implementation', 'store interface', 'transaction boundary', 'scaling fault line', 'single binary', 'deployment topology', or 'test contract'. Primarily Go, but applicable to any language with interface-like constructs (Rust traits, Java/Scala interfaces).

2026-04-201

actor-pattern

corruptmemory/claude-stuff

Apply the actor pattern for thread-safe state management. Use when: (1) multiple threads/goroutines need shared mutable state, (2) replacing mutex-locked structs or atomic patterns, (3) building a service layer that owns in-memory state plus persistence, (4) application has distinct operational modes (setup, running, error) requiring a coordinator that manages sub-actors, (5) the user mentions 'actor pattern', 'goroutine event loop', 'channel-based state management', or 'actors managing actors'. Supports Go, Jai, C, Rust, Odin, and Zig.

2026-04-201

tree-sitter-grammar

corruptmemory/claude-stuff

Comprehensive tree-sitter grammar development guide covering the JavaScript DSL, precedence systems, conflict resolution, external scanners, state explosion mitigation, and best practices distilled from studying 17 reference grammars and the official documentation. Use when building or modifying tree-sitter grammars, debugging parse errors, optimizing parser generation, or understanding tree-sitter internals. Trigger: user mentions 'tree-sitter', 'grammar.js', 'parser generation', 'tree-sitter conflicts', 'external scanner', 'state explosion', or asks about tree-sitter grammar development.

2026-02-221

emacs-ts-mode

corruptmemory/claude-stuff

Comprehensive guide for building Emacs tree-sitter major modes. Covers the full treesit.el API, font-lock rules, indentation, navigation, imenu, and best practices distilled from studying 17+ production modes. Use when creating or modifying an Emacs tree-sitter mode (*-ts-mode), working with treesit-font-lock-rules, treesit-simple-indent-rules, or any Emacs tree-sitter integration. Trigger: user mentions 'ts-mode', 'tree-sitter mode', 'treesit', 'font-lock-rules', 'indent-rules', or asks about Emacs tree-sitter major mode development.

2026-02-141

config-extraction

corruptmemory/claude-stuff

Extract subsystem-specific config structs from a monolithic/global configuration using the strangler fig pattern. Each subsystem gets a focused config struct and a pure conversion function, breaking the dependency on the global config package. Use when: (1) multiple packages import a central config struct and cherry-pick fields, (2) you want to decouple a subsystem so it no longer imports the config package, (3) config has cross-referencing lookups (e.g. account name → key) that should be pre-resolved, (4) the user mentions 'extract config', 'decouple config', 'config refactor', or 'strangler fig config'.

2026-02-121

go-web-scaffold

corruptmemory/claude-stuff

Scaffold a new Go web application with single-binary architecture, templ HTML templates, htmx interactivity, chi router, vendored frontend assets, embedded static files, TOML config with reflection-based gen-config, and a central build.sh script. Use when the user wants to create a new Go web project, HTTP API, dashboard, or web application from scratch. Trigger phrases: 'new Go project', 'scaffold', 'start a new web app', 'create a Go web server'.

2026-02-121

name	jai-language
description	Comprehensive Jai programming language reference and cheat sheet. Use when working with Jai code, tree-sitter-jai grammar development, or answering questions about Jai syntax and semantics. Covers declarations, types, control flow, directives, metaprogramming, and all language features. Trigger: user mentions 'Jai', 'Jai language', 'tree-sitter-jai', or asks about Jai syntax.

Jai Language Reference

Complete reference for the Jai programming language by Jonathan Blow.

The Jai compiler distribution at ~/jai/jai/ contains the authoritative source:

how_to/ — 80 .jai files across subdirectories covering all features
examples/ — Real-world programs
modules/ — Standard library

Compendium verification requirement

Every compendium .jai file must compile without errors or warnings against the current Jai compiler. When updating the skill for a new Jai release:

Bump version headers in the cheatsheet and all compendium files.
Reconcile changelog changes with skill content (removed features, new syntax, etc.).
Compile every compendium file with ~/jai/jai/bin/jai-linux <file>.jai and confirm zero errors.
Clean up build artifacts (rm -rf .build in the compendium directory).

Do not mark a version as verified until compilation is confirmed. The compendium is a "known good" corpus — if it doesn't compile, the version stamp is a lie.