update-web-assets

Refresh vendored Bootstrap, HTMX, Alpine.js, and Bootstrap Icons assets with SHA-256 manifest updates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/neon-law-foundation/navigator --skill update-web-assets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-web-assets
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/update-web-assets
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill update-web-assets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps the web app's third-party front-end libraries current without relying on a CDN, preserving consistent behavior across development, KIND, and production.

Core Features & Use Cases

  • Vendored asset refresh: Updates Bootstrap CSS and JS, HTMX, Alpine.js, and Bootstrap Icons from pinned upstream releases.
  • Manifested integrity checks: Recomputes SHA-256 hashes and keeps web/public/VENDOR.toml in sync with the files on disk.
  • Safe upgrade guidance: Distinguishes minor and patch bumps from major version changes and flags when a design review is required.
  • Use case: Refresh the front-end stack after a security advisory or routine dependency bump while preserving the exact bytes served by the application.

Quick Start

Ask the skill to update the vendored web assets in web/public, refresh the manifest, and verify the files against the repository checks.

Frequently Asked Questions about update-web-assets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update vendored Bootstrap and HTMX files without using a CDN?

To update vendored Bootstrap and HTMX files without a CDN, refresh the assets stored under web/public from pinned upstream releases and recompute their SHA-256 hashes in the VENDOR.toml manifest to ensure local integrity.

What is the safest way to bump minor or patch versions for front-end dependencies like Alpine.js?

The safest way to bump minor or patch versions for front-end dependencies like Alpine.js is to update from pinned upstream URLs, recompute SHA-256 manifest entries, and run verification checks to ensure exact byte parity.

How do I verify the integrity of locally hosted Bootstrap Icons after an upgrade?

To verify the integrity of locally hosted Bootstrap Icons after an upgrade, rewrite their local paths, recompute SHA-256 hashes for the VENDOR.toml manifest, and validate the files against web/tests/vendor_assets.rs.

When do I need a design review before refreshing web assets?

You need a design review before refreshing web assets when upgrading across major version changes, whereas minor and patch release bumps for development, KIND, or production parity can proceed with standard manifest verification.

Does vendoring front-end libraries provide consistent behavior across KIND and production environments?

Vendoring front-end libraries provides consistent behavior across KIND and production environments by serving exact bytes from local files under web/public rather than relying on external CDN resources.