메뉴
Rslib best practices for config, CLI workflow, output, declaration files, dependency handling, build optimization and toolchain integration. Use when writing, reviewing, or troubleshooting Rslib projects.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | rslib-best-practices |
| description | Rslib best practices for config, CLI workflow, output, declaration files, dependency handling, build optimization and toolchain integration. Use when writing, reviewing, or troubleshooting Rslib projects. |
Apply these rules when writing or reviewing Rslib library projects.
rslib.config.ts and defineConfiglib.*), and also leverage Rsbuild configurations (e.g., source.*, output.*, tools.*) as neededtools.rspack or tools.bundlerChain to access Rspack's native configurationstsconfig.json path aliasesrslib to buildrslib --watch to build in watch mode for local developmentrslib inspect to inspect final Rslib/Rsbuild/Rspack configs"type": "module" in package.jsonoutput.target set to 'web' when building component librariesexports field in package.json is correctly configured and matches the actual JavaScript output and declaration files output of different formats (ESM, CJS, etc.)lib.dts: true or detailed configurationslib.dts.tsgo experimental feature with @typescript/native-preview installeddevDependencies in bundle mode and dependencies in dependencies and peerDependencies will be automatically externalized (not bundled) by defaultpackage.json carefully to ensure no missing dependency errors occur when consumers install and use this packagelib.syntax aligned with real compatibility requirements to enable better optimizations@rstest/adapter-rslib for writing tests@rspress/plugin-preview and @rspress/plugin-api-docgen for component previews and API docsDEBUG=rsbuild when diagnosing config resolution or plugin behaviordist/.rsbuild to confirm final Rsbuild/Rspack config, not assumed configDebug 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.