Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →octanejs/octane-core-extend
Change Octane's runtime, compiler, scheduler, reconciler, SSR, or hydration engine. Use before editing packages/octane/src. Covers the observable contract, hot-path analysis, and the performance evidence required before handoff.
Passed 19 of 21 test cases with the skill, and 8 of 21 without it.
and 10 more in the full report
11 fixed8 passed either way2 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to fix a bug in Octane's Vite plugin that handles SSR module hot-reloading and asset injection during dev server startup. Which directory in the repository owns this code?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies packages/vite-plugin-octane/* as the owning location for Vite plugin behavior. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this when changing core runtime, compiler, AST/TSRX transforms, SSR, hydration, or public octane APIs.
AGENTS.md.rulesync/rules/core-engineering.mdREADME.mddocs/differences-from-react.mdBefore editing, write down:
concise-code.Assume framework-fundamental code is performance-sensitive until the call graph
shows otherwise. Use the performance-audit skill alongside this skill whenever
the change can affect per-component, per-render, per-node, compiler-output, SSR,
hydration, scheduling, reconciliation, or bundle costs.
No exceptions, and not only for bug fixes. Core code multiplies across every Octane application, so each change ships with a test that would catch the regression it could introduce.
test cases passed, vs 8 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.