Author, generate, validate and govern AI agent rules, skills, plugins and MCP configuration across 52 coding assistants. Review with verified model evidence, evaluate skills, lock and sign dependencies, and publish bundles. CLI, MCP server and Go API.
This repository also configures its own agents. See what ai-rulez tells them →
Skill Claude CodeCodex
Use when adding a new CLI command, flag, preset, or other user-visible capability, and before opening a pull request for it: covers the plan, tests, docs, schema, wrappers, and final validation steps.
Skill Claude CodeCodex
Use when changing config.toml fields or defaults, include resolution, domain or profile behavior, the JSON schemas in schema/, or the loader, validator and migration code in internal/config and internal/migrate.
Skill Claude CodeCodex
Use when you need to know how ai-rulez loads configuration, generates outputs, runs CRUD subcommands, validates, or serves MCP, and which internal package owns each step, before tracing or changing one of those flows.
Skill Claude CodeCodex
Use when editing files under docs/, zensical.toml, or the generated site/, or when a CLI or config change needs its documentation, examples, onboarding, or migration guidance updated.
Skill Claude CodeCodex
Use when changing the MCP server in internal/mcp, its handlers or tools, [[mcpservers]] configuration, MCP schemas, or the tests and docs for MCP endpoints.
Skill Claude CodeCodex
Use when preparing a release, bumping versions across root.go, package.json and pyproject.toml, or changing the npm and PyPI wrappers in release/, the changelog, or distribution assets.
Skill Claude CodeCodex
Use when you are unsure where code, docs, schemas, wrappers, or tests live in this repository, or need to pick the right directory before adding or moving files.
Skill Claude CodeCodex
Use when writing or fixing tests, updating fixtures under tests/, or adding integration or e2e coverage for generator, migration, CLI flags, or profile behavior.
Skill Claude CodeCodex
cgo conventions for linking Go to a C or Rust static library: import "C" directives, type/string conversion, CString memory management, thread safety, and Go pointer pinning. Load when generating or reviewing cgo bindings that call a C or Rust core from Go.
Skill Claude CodeCodex
ext-php-rs conventions for building PHP 8.2+ native extensions from a Rust core: phpclass/phpfunction macros, Zval conversion, PhpException mapping, php.ini loading, and PHPUnit testing. Load when generating or reviewing ext-php-rs PHP bindings for a Rust library.
Skill Claude CodeCodex
extendr conventions for exposing a Rust core to R: extendr macros and module registration, Robj type mapping, NA handling, rextendr builds, R package scaffolding, and CRAN compliance. Load when generating or reviewing extendr R bindings for a Rust library.
Skill Claude CodeCodex
jni-rs conventions for exposing a Rust core to Java/JVM: JNI export naming, JNIEnv usage, string conversion, exception checks/throws, global references, and library loading. Load when generating or reviewing jni-rs Java/JVM bindings for a Rust library.
Skill Claude CodeCodex
Magnus conventions for building Ruby native extensions from a Rust core: defineclass, TryConvert/IntoValue, exception mapping, GVL handling, TypedData GC integration, and rake-compiler distribution. Load when generating or reviewing Magnus Ruby bindings for a Rust library.
Skill Claude CodeCodex
napi-rs conventions for exposing a Rust core to Node.js: #[napi] macros, napi::Error mapping, auto-generated .d.ts types, async Promises, and CommonJS/ESM output. Load when generating or reviewing napi-rs Node.js bindings for a Rust library.
Skill Claude CodeCodex
PyO3 conventions for exposing a Rust core to Python: pyclass/pymethods, PyErr/PyResult error mapping, GIL release, properties, maturin builds, and pytest. Load when generating or reviewing PyO3 Python bindings for a Rust library.
Skill Claude CodeCodex
Rustler conventions for building Elixir NIFs from a Rust core: nif macros, tagged {:ok,}/{:error,} tuples, dirty schedulers, ResourceArc state, NifStruct derives, and mix compile. Load when generating or reviewing Rustler Elixir NIF bindings for a Rust library.
Skill Claude CodeCodex
vite+ unified TypeScript toolchain conventions: the vp CLI for package/node management, oxlint/oxfmt, type-aware linting, vitest, rolldown/tsdown bundling, task caching, and migration. Load when configuring or reviewing a vite+ TypeScript toolchain.
Skill Claude CodeCodex
wasm-bindgen conventions for compiling a Rust core to WebAssembly for JavaScript: wasm-pack packaging, JsValue mapping, async futures, bundle-size tuning, web-sys/js-sys, and TypeScript defs. Load when generating or reviewing WebAssembly/JS bindings for a Rust library.
Skill Claude CodeCodex
C# code conventions covering .NET 8+/C# 12, nullable reference types, Roslyn analyzers, xUnit, record types, async/await discipline, and dependency security. Load when writing or reviewing C# code.
Skill Claude CodeCodex
Elixir code conventions covering Elixir 1.14+/OTP 25+, pattern matching, mix format, Credo/Dialyzer, ExUnit, ExDoc, OTP process patterns, and dependency security. Load when writing or reviewing Elixir code.
Skill Claude CodeCodex
Go code conventions covering Effective Go, error wrapping, golangci-lint, govulncheck, table-driven tests, interfaces, context usage, modules, and concurrency. Load when writing or reviewing Go code.
Skill Claude CodeCodex
Java code conventions covering Java 17+ records and sealed classes, formatting/static analysis, Maven/Gradle, JUnit 5, exception handling, constructor injection, streams, and security. Load when writing or reviewing Java code.
Skill Claude CodeCodex
PHP code conventions covering PHP 8.2+ strict types, PSR-12 formatting, PHPStan/Psalm static analysis, PHPUnit, Composer dependency management, PSR-4 autoloading, and security. Load when writing or reviewing PHP code.
Skill Claude CodeCodex
Python code conventions covering type hints, Ruff formatting/linting, mypy/pyright, pytest, async I/O, uv packaging, and dependency security scanning. Load when writing or reviewing Python code.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: