القائمة
Rspack best practices for config, CLI workflow, type checking, CSS, bundle optimization, assets and profiling. Use when writing, reviewing, or troubleshooting Rspack projects.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Debug Rstack ecosystem CI failures and attribute the real source PR or downstream change. Always use this skill when the user mentions Rspack eco-ci, rstack-ecosystem-ci, a suite turning red, a downstream regression, a green-to-red pivot, canary bisect, @rspack-canary/core, or daily eco-ci triage — even if they only ask "why is this suite failing", "which PR broke it", or "is this Rspack's fault". Use it to avoid over-blaming the first Rspack commit that appears red in status data.
Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement.
Create or update draft GitHub release notes, or output organized Markdown when draft creation is unavailable. Use for release notes, draft releases, release PR checks, npm staged publishing checks, and optional highlights.
Generate or maintain Rspress documentation for a project. Use whenever the user wants to create a new Rspress v2 docs site, add docs for user-facing feature work or PRs, maintain a dedicated Rspress docs project in a monorepo, or prevent stale Rspress v1 scaffolds/version drift before documentation work. For full v1-to-v2 migration, hand off to the rspress-v2-upgrade skill.
Audit and modernize RstackJS/Rspack ecosystem repositories to the current shared infrastructure baseline: Rslib ESM or dual builds, Rslint recommended rules, Rstest test tooling, Node 20+ support where appropriate, TypeScript 6 and tsgo where compatible, concise README/AGENTS docs, release workflow cleanup, unused dependency removal, and infra PR commit conventions. Use when updating rstackjs repositories, copying infra patterns from maintained exemplars, or reviewing package/tooling consistency.
Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style.
استنادا إلى تصنيف SOC المهني
| name | rspack-best-practices |
| description | Rspack best practices for config, CLI workflow, type checking, CSS, bundle optimization, assets and profiling. Use when writing, reviewing, or troubleshooting Rspack projects. |
Apply these rules when writing or reviewing Rspack projects.
rspack.config.ts and defineConfigentry values for multi-page applicationsprocess.env.NODE_ENV only when neededtest, include, exclude, resourceQuery)If @rspack/cli is installed:
rspack dev for local developmentrspack build for production buildrspack preview only for local production previewts-checker-rspack-plugin for integrated dev/build type checkstsc --noEmit/vue-tsc --noEmit as an explicit script stepChoose one strategy:
type: 'css' | 'css/auto' | 'css/module') for modern setupscss-loader + CssExtractRspackPlugin for webpack migration compatibilitystyle-loader for pure style-in-JS runtime injection scenariosOptional:
builtin:lightningcss-loader when goals are syntax downgrade + vendor prefixingsass-loader/less-loader for preprocessing Sass/Less files@tailwindcss/webpack for Tailwind CSS integrationimport() for non-critical code pathstarget aligned with real compatibility requirementspublicpublic files by absolute URL pathasset, asset/resource, asset/inline, asset/source) over legacy file-loader/url-loader/raw-loader--cpu-prof) when JavaScript-side overhead is suspectedRSPACK_PROFILE=OVERVIEW and analyze trace output for compiler-phase bottlenecksbabel-loader, PostCSS, terser) with Rspack built-ins when feasible.map files to public servers/CDNs when production source maps are enabled