本文へ移動
cccskills
無料GitHub で公開

qwik-router-development

Use when modifying or reviewing Qwik Router code under packages/qwik-router, including runtime routing, buildtime route generation, middleware, adapters, SSG, markdown/MDX handling, or router tests.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Qwik Router Development

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

Fast Path

  1. Classify the touched router surface before editing: runtime, buildtime, middleware, adapter, SSG, markdown/MDX, or Vite integration.
  2. Read the smallest source file plus the closest *.unit.ts or *.spec.ts file before changing behavior.
  3. For middleware, loader, action, or navigation changes, trace handler ordering and shared state from request creation through response/client consumption before editing.
  4. For unit/spec coverage, run pnpm vitest run <path>.
  5. For browser/router behavior, rebuild first with pnpm build.core.dev, then use the focused Qwik Router e2e command.
  6. If public router API markdown changes are expected, run pnpm api.update after tests pass.

Source Map

  • Runtime: packages/qwik-router/src/runtime/src/
  • Buildtime route generation: packages/qwik-router/src/buildtime/
  • Vite integration: packages/qwik-router/src/buildtime/vite/
  • Middleware: packages/qwik-router/src/middleware/
  • Adapters: packages/qwik-router/src/adapters/
  • SSG: packages/qwik-router/src/ssg/
  • Router e2e tests: e2e/qwik-e2e/tests/qwikrouter/

Verification

Use the closest command that covers the changed surface:

pnpm vitest run packages/qwik-router/src/buildtime/routing/parse-pathname.unit.ts
pnpm vitest run packages/qwik-router/src/runtime/src/client-navigate.unit.ts
pnpm build.core.dev
pnpm playwright test e2e/qwik-e2e/tests/qwikrouter/nav.e2e.ts --browser=chromium --config e2e/qwik-e2e/playwright.config.ts

Do not use --project chromium with e2e/qwik-e2e/playwright.config.ts; this config expects the --browser=chromium flag.

Quality Bar

  • Keep middleware, loader, and action ordering explicit. Do not add broad fallbacks that hide which module owns a request.
  • Add regression tests for the exact route shape or request mode that failed, such as index route, layout loader, page loader, redirect, action, or SPA navigation.
  • When changing serialized route state or loader data, update both server output and client consumption in the same change.
  • Preserve deprecated Qwik City compatibility only when current source still supports it, and keep compatibility warnings/tests intentional.
  • If router work exposes stale guidance here or in .ruler/AGENTS.md, update the guidance before finishing or record why guidance edits were out of scope.

Stop Conditions

  • Stop and inspect the generated API workflow before hand-editing any *.api.md file.
  • Stop and switch to qwik-e2e-verification when most of the work is Playwright setup/debugging.
  • Stop and run pnpm api.update if exported router API changed.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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/ossrules602026年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/ossrules602026年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/ossrules602026年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/ossrules602026年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/ossrules602026年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/ossrules602026年9月21日 更新

modem-dev のスキルをすべて見る

このスキルの問題を報告する