limiara-platform-engineering
Use when working on Limiara's Rust platform kernel, plugin architecture, Contacts plugin, tenancy/RLS security, Wasm plugin sandboxing, service-plugin protocol, or React plugin shell.
SKILL.mdskills/limiara-platform-engineering/SKILL.md
GitHubLimiara platform engineering skill
When to use
Use this skill for changes that affect:
- platform kernel crates or app boundaries;
- native, Wasm, or external service plugin contracts;
- Contacts or future business-domain plugins;
- tenant isolation, PostgreSQL RLS, permissions, audit, outbox/inbox, entitlements, or identity/session flows;
- the React plugin shell or plugin UI contribution model;
- Docker Compose, Kubernetes packaging, CI, or operational runbooks.
Required mental model
Limiara is a modular monolith first. The kernel is domain-neutral, while business domains are plugins. First-party native plugins may be statically linked, but they still use explicit manifests, permissions, capabilities, migrations, events, UI contributions, lifecycle state, and audit records.
Implementation checklist
- Inspect
IMPLEMENTATION_PLAN.md,README.md, relevant ADRs, and plugin manifests before changing code. - Confirm whether the change belongs in the kernel, a plugin, runtime support, frontend shell, or operations/docs.
- Preserve tenant isolation:
- keep
tenant_idon tenant-scoped data; - use forced RLS for PostgreSQL tables;
- set
app.tenant_idtransaction-locally only after membership verification; - avoid cross-plugin private table access.
- keep
- Preserve security boundaries:
- permissions authorize users;
- capabilities constrain plugins;
- entitlements gate commercial features but never authorize users;
- Wasm defaults deny filesystem, environment, secrets, database, and network access.
- Emit audit records and outbox events in the same transaction as business mutations once persistence is wired.
- Keep API errors stable and safe: use problem-style responses with machine-readable codes.
- Update docs/ADRs when changing an architectural boundary.
Validation commands
Run these when the environment has dependency access:
cargo build --workspace --locked
cargo fmt --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked
pnpm install --frozen-lockfile
pnpm typecheck
pnpm test
pnpm build
If the registry or proxy blocks dependency resolution, document the exact failure rather than claiming success.