update

Refresh Rust workspace dependencies and vendored web assets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies periodic maintenance by coordinating a full Rust dependency refresh with a safe, vendored front-end asset update, so the Navigator workspace stays current without mixing unrelated changes.

Core Features & Use Cases

  • Coordinated dependency refresh: Updates semver-compatible Rust crates across the workspace and keeps the lockfile in sync.
  • Vendored frontend maintenance: Refreshes Bootstrap, HTMX, Alpine, Bootstrap Icons, and Noto Serif assets that are served locally from web/public/.
  • Safety and verification: Preserves the no-CDN invariant, checks pinned asset hashes, and keeps crate and asset changes in separate commits.
  • Use Case: Use this Skill when a monthly maintenance sweep or security advisory requires both backend crate updates and frontend asset bumps.

Quick Start

Use the update skill to refresh the workspace crates and vendored web assets, then verify the changes pass the required tests before committing them separately.

Frequently Asked Questions about update

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

FAQPage Schema
How do I safely update Rust workspace dependencies and vendored web assets together?

To safely update Rust workspace dependencies and vendored web assets together, apply semver-compatible cargo updates and refresh frontend assets, then commit crate and asset changes separately to keep changes isolated.

What is the best way to refresh vendored Bootstrap and HTMX assets without using a CDN?

Refreshing vendored Bootstrap and HTMX assets without a CDN involves downloading the assets locally, verifying pinned asset hashes, and placing them in the web public directory to preserve the no-CDN invariant.

How do I update a Rust lockfile when responding to a security advisory?

Updating a Rust lockfile during a security advisory response requires running semver-compatible cargo updates across the workspace to refresh affected crates and keep the lockfile synchronized.

Can I mix frontend asset bumps and Rust crate updates in the same commit?

Mixing frontend asset bumps and Rust crate updates in the same commit is not recommended; the update process requires separate commit discipline to keep crate and asset changes cleanly isolated.

Does this maintenance process verify pinned asset hashes for vendored frontend libraries?

Yes, the maintenance process verifies pinned asset hashes for vendored frontend libraries like Bootstrap, HTMX, and Alpine to ensure integrity and preserve the no-CDN invariant.

When do I need to run a coordinated Rust dependency and frontend asset refresh?

A coordinated Rust dependency and frontend asset refresh is needed during periodic maintenance sweeps, such as monthly updates, or when a security advisory requires both backend crate updates and frontend asset bumps.