본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Qwik Core Development

Use this skill for packages/qwik/** work. Keep the normal repo-wide instructions from .ruler/AGENTS.md in force.

Fast Path

  1. Identify the touched subsystem before editing: reactive primitives, VNode/client diffing, cursor, QRL/serialization, SSR, hooks, or tests.
  2. Read the smallest relevant source and tests before making changes.
  3. Find the invariant that must stay true across SSR, resume, client render, and serialization when the touched code crosses those boundaries.
  4. After implementation changes, immediately run the closest focused Vitest file with pnpm vitest run <path>. Do not use pnpm test.unit.
  5. 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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

modem-dev/ossrules622026년 9월 21일 업데이트

Use when adding A2UI rendering to any AG-UI-supported framework or custom AG-UI application, scaffolding an AG-UI app that should render A2UI, adapting an AG-UI integration to emit A2UI surfaces, or wiring the AG-UI A2UI middleware/toolkit with a compatible renderer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

modem-dev/ossrules622026년 9월 21일 업데이트

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

modem-dev/ossrules622026년 9월 21일 업데이트

Evaluate an open source project's AGENTS.md and produce a corpus entry for the /agents-md directory. Use when adding a project to the directory, refreshing an existing entry, or running a batch of candidate repositories.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

modem-dev/ossrules622026년 9월 21일 업데이트

Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

modem-dev/ossrules622026년 9월 21일 업데이트

Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad code-quality and process audits, triage, reproduction, and implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

modem-dev/ossrules622026년 9월 21일 업데이트

modem-dev의 스킬 모두 보기

이 스킬의 문제 신고