免费在 GitHub 公开

qwik-core-development

Use 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.

中文简介正在准备中。当前显示原文说明。

modem-dev/ossrules

查看安装方法

包含的文件（1）

SKILL.md2.4 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

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 use pnpm test.unit.
If touching Rust optimizer code, load qwik-optimizer-development instead 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.update after the focused tests pass.
If this skill or references/core-notes.md is stale after your source inspection, update it before finishing or record why guidance edits were out of scope.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

adding-ty-diagnostics

免费

Use when a user says "add a ty diagnostic", "write this new ty diagnostic", "change a ty error message", "review ty diagnostics", or asks to add, update, or review ty checks, diagnostic messages, subdiagnostics, or concise output behavior.

中文简介正在准备中。当前显示原文说明。