Menu
Enforces immutable runtime/tooling policy for projects bootstrapped from this starter pack.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Tool specifications and interfaces for the NELA language toolchain. Covers surface language (NELA-S) interpreter, type checking, compiler (NELA-S → NELA-C interaction nets), serialization, legacy code migration, and LLM context optimization. Load when implementing any NELA toolchain component.
Practical guidance to write valid NELA-S files. Use this skill in new projects created from the starter pack.
Reusable LLM-first header and section metadata standard for NELA-S source files. Defines the section index format, per-section metadata blocks, synchronization rules, and validation workflow. Load when creating or refactoring any .nela file.
Mathematical foundations for NELA language design. Primary theory: Interaction Nets (Lafont 1990) — local graph rewriting, NOT automata theory. Supporting theories: Linear Logic (resource semantics), Dependent Type Theory (verification). Von Neumann CA is historical background only — do not use it to guide language design decisions. Load this skill before designing any NELA language construct, rewrite rule, or type system component.
| name | nela-runtime-immutable |
| description | Enforces immutable runtime/tooling policy for projects bootstrapped from this starter pack. |
| applyTo | *.py,tools/*.py,Makefile |
This skill is repository-template specific.
The starter pack itself contains only authoring assets under .github/.
Apply this policy only after runtime/tool files are copied into the target project.
If runtime/tool files were copied from the starter pack, they must not be modified during normal feature work.
Protected paths:
*.pytools/*.pyMakefileNELA-S project logic must evolve in .nela sources.
Host/runtime infrastructure should remain stable and versioned as a fixed base.
Only modify protected files when the user explicitly requests a runtime/tooling change in the current prompt.
Before editing protected files:
.nela files.