docs: teach the skills the configuration they are meant to prove

.agents/skills/code-check/SKILL.md

@@ -8,7 +8,7 @@ allowed-tools: "Bash(just check:*), Bash(just clippy:*), Bash(just check-unused-
 
 Code validation and linting for the `nx-std/nx-object` crate. Optimized for **minimum wall-clock time to first error**: cheapest signal first, auto-fix before hand-fix.
 
-The repository holds a single crate, so there is no per-crate selection to make. What varies here is the **feature set**: the crate is `no_std` with default features and pulls in `std` through `filesystem-support`, so a change can compile in one configuration and fail in the other.
+The repository holds a single crate, so there is no per-crate selection to make. What varies here is the **feature set**: the crate carries every format and `std` by default, and drops to `alloc` or to bare `no_std` on demand, so a change can compile in one configuration and fail in the other.
 
 ## When to Use This Skill
 
@@ -34,16 +34,16 @@ The recipes take the flags rather than baking them in, so the same two invocatio
 | Configuration | Flags                                                       |
 |---------------|--------------------------------------------------------------|
 | `std`         | `--all-targets --all-features`                               |
-| `no-std`      | `--no-default-features --target aarch64-unknown-none`        |
+| `no-std`      | `--no-default-features --features all-formats,alloc --target aarch64-unknown-none` |
 
 `--all-targets` belongs to the `std` set only: on a bare-metal target the test and bench targets fail to build outright, because they link the libtest harness and want a `#[panic_handler]`.
 
 Run the `std` set always. Add the `no-std` set when any of these is true:
 
 | Signal                     | Meaning                                                                          |
 |----------------------------|----------------------------------------------------------------------------------|
-| **Feature-gated code edit**| A file under `src/raw/` or `src/read/`, or any code not behind `filesystem-support`. |
-| **New import**             | Any `use` added outside a `filesystem-support` gate. `std` is unavailable there.  |
+| **Feature-gated code edit**| A file under `src/raw/`, `src/read/` or `src/write/`, or any code not behind a `std` gate. |
+| **New import**             | Any `use` added outside a `std` gate. `std` is unavailable there.                |
 | **Feature or gate change** | `[features]` in `Cargo.toml`, or a `#[cfg(feature = ...)]` added, moved, or removed. |
 | **New dependency**         | A dependency added, or an existing one's `default-features`/`features` changed.   |
 
@@ -73,7 +73,7 @@ Runs `cargo check` with whatever flags you pass. **Default Stage 1 command.**
 
 Examples:
 - `just check --all-targets --all-features` — the `std` configuration
-- `just check --no-default-features --target aarch64-unknown-none` — the `no-std` configuration
+- `just check --no-default-features --features all-formats,alloc --target aarch64-unknown-none` — the `no-std` configuration
 
 ### Lint Rust Code with Auto-fix
 ```bash
@@ -84,7 +84,7 @@ Runs `cargo clippy` with whatever flags you pass. **Default Stage 2 command.**
 Examples:
 - `just clippy --all-targets --all-features --fix --allow-dirty --allow-staged` — standard auto-fix pass
 - `just clippy --all-targets --all-features` — residue pass (after `--fix`) to surface remaining warnings
-- `just clippy --no-default-features --target aarch64-unknown-none -- -D warnings` — the `no-std` lint CI runs
+- `just clippy --no-default-features --features all-formats,alloc --target aarch64-unknown-none -- -D warnings` — the `no-std` lint CI runs
 
 #### Auto-fix semantics
 
@@ -104,7 +104,7 @@ Before considering a task complete: all checks MUST pass AND all clippy warnings
 ### Example Workflows
 
 **Common case (write-layer edit):**
-Edits in `src/write/...`, which is behind `filesystem-support`.
+Edits in `src/write/...`, which is behind `alloc`.
 
 1. Format changes: use `/code-format`.
 2. **Stage 0** — probe `mcp__ide__getDiagnostics`. If available, call with each edited file's `file://` URI. Fix reported issues.
@@ -121,10 +121,10 @@ Edits in `src/raw/...`, which compiles in every configuration.
 2. **Stage 0** — probe `mcp__ide__getDiagnostics`; fix surfaced issues.
 3. **Stage 1** — run both configurations → fix errors → repeat until both are clean:
    - `just check --all-targets --all-features`
-   - `just check --no-default-features --target aarch64-unknown-none`
+   - `just check --no-default-features --features all-formats,alloc --target aarch64-unknown-none`
 4. **Stage 2** — `just clippy --all-targets --all-features --fix --allow-dirty --allow-staged`, hand-fix the
    residue, then lint the other configuration:
-   `just clippy --no-default-features --target aarch64-unknown-none`
+   `just clippy --no-default-features --features all-formats,alloc --target aarch64-unknown-none`
 5. Re-run `/code-format` if `--fix` changed source.
 6. Done when: zero errors AND zero warnings in both configurations.
 

.agents/skills/code-review/SKILL.md

@@ -69,8 +69,8 @@ Verify backwards compatibility is maintained:
 - Public API: existing functions, types, and trait signatures must not break consumers
 - Cargo `[features]`: removing or renaming a feature breaks consumers, and moving an item behind a gate is the
   same break in a quieter form
-- `no_std` support: an item that was reachable without `filesystem-support` must stay reachable, and nothing
-  ungated may start requiring `std`
+- `no_std` support: an item that was reachable without `std` must stay reachable, and nothing ungated may
+  start requiring `std` or an allocator
 - On-disk format compatibility for the formats the crate reads and writes: a file written by the previous
   version must still parse, and a file this version writes must still load on the console
 

.agents/skills/code-test/SKILL.md

@@ -25,7 +25,7 @@ The repository holds a single crate, so scope is a question of features and of w
 | Behavior change ready to land                           | `just test --all-features`                  |
 | Feature gate, `Cargo.toml`, or dependency change        | `just test --all-features`                  |
 
-Most of the test suite lives behind `filesystem-support`, so a run without `--all-features` exercises very little. Use the narrow forms to iterate, and finish with `--all-features`.
+Most of the test suite lives behind `alloc` and `std`, so a run without `--all-features` exercises very little. Use the narrow forms to iterate, and finish with `--all-features`.
 
 ## Available Commands