// Enforce locked docs, boundary rules, and safety guardrails for any Zireael change.
Review C code for compliance with Zireael standards. Use before committing or when reviewing PRs.
Write readable C with proper comments, named constants, and consistent style per CODE_STANDARDS.md.
Write readable C with proper comments, named constants, and consistent style per CODE_STANDARDS.md.
Write readable C with proper comments, named constants, and consistent style per CODE_STANDARDS.md.
Maintain stable C ABI and versioned binary formats (drawlist + event batches).
Maintain portable CMake builds and deterministic unit/golden/fuzz/integration tests.
| name | zireael-spec-guardian |
| description | Enforce locked docs, boundary rules, and safety guardrails for any Zireael change. |
| metadata | {"short-description":"Spec + boundary compliance"} |
Use this skill first for any task in this repo, especially when:
After guardian checks, run zireael-code-style for any code edit/review.
README.md — GitHub-facing overviewdocs/00_INDEX.md — internal reading pathdocs/CODE_STANDARDS.md — code style and commentsKey locked docs:
docs/SAFETY_RULESET.mddocs/LIBC_POLICY.mddocs/ERROR_CODES_CATALOG.mddocs/VERSION_PINS.mddocs/GOLDEN_FIXTURE_FORMAT.mdsrc/core, src/unicode, src/util MUST NOT include OS headerssrc/platform/win32/ and src/platform/posix/#ifdef _WIN32 only in platform backends0 = OK, negative ZR_ERR_* codesdocs/00_INDEX.md)docs/VERSION_PINS.md)zr_limits_t)#ifdef leaked into core/unicode/utildocs/ERROR_CODES_CATALOG.md