modem-dev/ossrules / public/files/qwik/.ruler/skills/qwik-core-development
qwik-core-development
UnverifiedUse when modifying or reviewing Qwik core package code under packages/qwik, especially reactive primitives, signals, VNodes, cursor behavior, QRLs, optimizer-facing runtime behavior, or Qwik core tests.
Qwik Core Development
Use this skill for packages/qwik/** work. Keep the normal repo-wide instructions from .ruler/AGENTS.md in force.
Fast Path
- Identify the touched subsystem before editing: reactive primitives, VNode/client diffing, cursor, QRL/serialization, SSR, hooks, or tests.
- Read the smallest relevant source and tests before making changes.
- Find the invariant that must stay true across SSR, resume, client render, and serialization when the touched code crosses those boundaries.
- After implementation changes, immediately run the closest focused Vitest file with
pnpm vitest run <path>. Do not usepnpm test.unit. - If touching Rust optimizer code, load
qwik-optimizer-developmentinstead of treating the change as TypeScript-only.
When to Load Detailed Notes
Read references/core-notes.md only when the task involves:
- async signals, computed signals, polling, or signal invalidation;
- QRL creation,
$transform behavior, or serialization issues; - VNode, cursor, or DOM diff behavior;
- Qwik core tests that use
$(),retryOnPromise, or private runtime state; - an unfamiliar pattern in
packages/qwik/src/core.
Do not load the reference for simple docs, package metadata, formatting, or unrelated monorepo work.
Core Reminders
- Prefer existing Qwik runtime patterns over new abstractions.
- Keep state ownership explicit. For serialized or streamed data, update emit and consume paths together and add a round-trip or regression test.
- Preserve compatibility deliberately. If deprecated input remains accepted, test both deprecated and current behavior.
- Use
$-suffixed functions and$()in tests when a QRL boundary is expected. - Avoid manual QRL construction unless nearby code already does it for the same reason.
- Keep tests focused and close to the behavior that changed; add e2e coverage only when browser, streaming, navigation, or integration timing is the behavior under test.
- If the change affects public API, run
pnpm api.updateafter the focused tests pass. - If this skill or
references/core-notes.mdis stale after your source inspection, update it before finishing or record why guidance edits were out of scope.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |