ranuts

# ranuts Resolve `ranuts` from the host project, not the plugin cache. Read its `package.json` version and exports before selecting a utility. In a ran checkout use `packages/ranuts/` and identify it as working-tree source; do not assume that source is already available from npm. `package-contract.json` beside this skill records the monorepo version the skill was authored against and states that API facts are **not** bundled here (`bundledApi: false`). Prefer the host's installed `docs/API.md` for that version. If the installed version differs from `authoredAgainst`, say so and do not invent exports from memory or from a newer checkout. Read package-relative `docs/API.md` for generated utility signatures, then relevant sections of `CLAUDE.md` and exported declarations for other subpaths. Prefer the smallest supported public entry. Do not copy a function inventory into the product or invent an export from a newer example. Check each operation's browser, Node or SSR requirements. A package being importable in Node does not mean every function can run without DOM, storage, Canvas or GPU facilities. Verify the actual operation in its intended environment and preserve cleanup, cancellation and error handling. For streaming consumers, preserve content identity and ordering, treat partial tool arguments as text until complete, and verify interruption and stale completion behavior against installed types. For product UI decisions use the sibling [design skill](../design/SKILL.md); for ranui components use the sibling [ranui skill](../ranui/SKILL.md). If documentation is absent, inspect matching declarations/source and state the version gap. Do not silently install, upgrade, or claim that a working-tree capability has shipped.