All skills

Shipwright build system for The Boring JavaScript Stack — Rsbuild-based asset pipeline replacing Grunt, with framework plugins for React/Vue/Svelte, Tailwind CSS, SSR support, and dev server with HMR. Use this skill when configuring builds, managing assets, or debugging the development server.

Use this Skill: https://skilld.dev/gh/sailscastshq/boring-stack/shipwright

This session only. Nothing lands on disk.

rulesasset-pipeline.md

≈641 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Asset pipeline

Tailwind v4

Register pluginTailwindcss() from @rsbuild/plugin-tailwindcss in config/shipwright.js. It runs Tailwind through the webpack integration. All current templates use this path.

/* assets/css/app.css */
@import 'tailwindcss';

@theme {
  --color-brand-500: #6c25c1;
}

Import this stylesheet from assets/js/app.js with import '~/css/app.css'. Preserve the template's existing theme, @config, and source declarations during migration. Keep utility names statically discoverable; use explicit maps for variants rather than constructing fragments such as bg-${color}-500.

Remove @tailwindcss/postcss when switching to the Rsbuild plugin. Delete postcss.config.js only if Tailwind was its only plugin. An older Tailwind v3 app must keep its compatible PostCSS setup until its CSS is deliberately migrated; the Rsbuild Tailwind plugin requires Tailwind v4.

See the Tailwind plugin.

Resource imports and static files

Import an asset to obtain its bundled URL, or use a resource query when the required representation matters:

import logoUrl from '~/images/logo.svg'
import sourceText from './example.js?raw'
import downloadUrl from './example.js?url'

?raw imports text; ?url imports an asset URL. Resource imports must not be transformed as executable page modules. See Rsbuild static assets.

Shipwright copies static files from assets/, excluding JavaScript and stylesheet source directories. A copied assets/images/logo.svg is available at /images/logo.svg. Use imports when you want bundler processing; use a public path for copied assets. JavaScript and CSS source should not be copied into the public directory.

HTML and chunks

Retain shipwright.styles() and shipwright.scripts() in the root EJS view. They use the build manifest to select assets; avoid manually naming output chunks. Keep the template's Inertia root and SSR markup intact.

Dynamic imports can emit companion chunks. Deploy the complete browser output, and, for SSR, the complete private .tmp/ssr/ directory. Verify a production lift, page HTML, and each referenced JavaScript/CSS request after build changes.

Source: SKILL.md on GitHub

1 alert17d4 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    No security issues were detected. The skill provides legitimate documentation and rules for managing the Shipwright build system, covering asset compilation, framework plugins, and development workflows.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    8/8 files flagged

Signed by skilld at dbf6087. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 3 weeks ago
Other metadata
metadata
{
  "author": "sailscastshq",
  "version": "1.1.0",
  "tags": "shipwright, rsbuild, build, vite, assets, tailwind, ssr, hmr, boring-stack"
}

README badge

README badge for sailscastshq/boring-stack/shipwright