modem-dev/ossrules / public/files/qwik/.ruler/skills/qwik-optimizer-development
qwik-optimizer-development
UnverifiedUse when modifying or reviewing the Qwik optimizer under packages/optimizer, Rust transform code, WASM/NAPI bindings, optimizer snapshots, or optimizer-facing runtime behavior.
Qwik Optimizer Development
Use this skill for packages/optimizer/** and Rust optimizer work. Keep the repo-wide rules from
.ruler/AGENTS.md in force.
Fast Path
- Identify whether the change is Rust transform logic, snapshots, WASM bindings, NAPI bindings, or TypeScript optimizer-facing integration.
- Read the closest Rust source, fixture, snapshot, and runtime helper that consumes the emitted shape before editing.
- Keep transform behavior deterministic: prefer explicit parser/AST cases and stable ordering over source-text heuristics.
- Use Rust-focused verification first; use
pnpm build.fullonly when a full optimizer/WASM rebuild is required. - If a runtime/core change is also involved, load
qwik-core-developmentfor that slice.
Source Map
- Rust optimizer core:
packages/optimizer/core/src/ - Rust fixtures:
packages/optimizer/core/src/fixtures/ - Rust snapshots:
packages/optimizer/core/src/snapshots/ - WASM bindings:
packages/optimizer/wasm/ - NAPI bindings:
packages/optimizer/napi/ - Optimizer package entry points:
packages/optimizer/src/ - Vite/Rollup integration:
packages/qwik-vite/src/
Verification
Use the smallest command that covers the change:
pnpm test.rust
pnpm test.rust.update
pnpm build.full
pnpm vitest run packages/qwik-vite/src/plugins/plugin.unit.ts
pnpm test.rust maps to make test, which runs Cargo tests for
packages/optimizer/core/Cargo.toml. Use pnpm test.rust.update only when snapshot updates are
intentional.
Hard Rules
- Do not hand-edit generated optimizer build output in
dist/,lib/, ortarget/. - Do not update snapshots without understanding the transform behavior change.
- Add or update a transform fixture/snapshot for every optimizer behavior change, including negative cases where the transform must not run.
- Keep optimizer output and runtime JSX/QRL/loader semantics in sync. If a transform changes an emitted attribute, import, segment, or capture shape, inspect the runtime consumer too.
- After touching
packages/optimizer/core/, do not claim verification without Rust test/build evidence or a recorded blocker. - If this skill becomes stale after source inspection, update it before finishing or record why guidance edits were out of scope.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |