oppdater-designsystem

Synchronize the oppdater-designsystem skill with the latest FHI Designsystem npm version.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/FHIDev/Fhi.AgentSkills --skill oppdater-designsystem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oppdater-designsystem
Source: https://github.com/FHIDev/Fhi.AgentSkills/tree/main/.claude/skills/oppdater-designsystem
Command: npx skills add https://github.com/FHIDev/Fhi.AgentSkills --skill oppdater-designsystem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The update-designsystem skill ensures the local repository's design-system skill remains aligned with the latest published FHI Designsystem, preventing drift and keeping public API references accurate for downstream AI tooling.

Core Features & Use Cases

  • Version alignment: fetch and verify the latest published version, compare it to the current baseline, and surface drift.
  • Delta planning: outline the sequence of minor-version changes and prepare minimal, evidence-based updates for SKILL.md and version docs.
  • Audit and verification: validate public manifests, theme files, tokens, and component references against the published package.

Quick Start

Update the oppdater-designsystem skill to the latest published version in this repo.

Frequently Asked Questions about oppdater-designsystem

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

FAQPage Schema
How do I sync my local repository with the latest published npm design-system version?

To sync your design-system version, the skill fetches the latest npm version, compares it to the current baseline, and updates SKILL.md along with version delta files to reflect new API changes.

What is the best way to track design-system package revisions and prevent API drift?

Tracking design-system package revisions involves validating public manifests, theme files, and tokens against the published npm package to surface version drift and keep API references accurate for downstream tooling.

How do I plan delta updates for minor design-system version changes?

Planning delta updates requires outlining the sequence of minor-version changes, comparing tag references, and preparing minimal, evidence-based updates for the SKILL.md and version documentation files.

Do I need to manually verify token updates after syncing the design-system skill?

Manual token verification is minimized because the skill performs an audit and validation step against public manifests, theme files, and component references to ensure the local repository matches the published package.

Why does my design-system SKILL.md file show outdated public API references?

Outdated public API references in SKILL.md occur when the local repository drifts from the latest published FHI Designsystem, requiring a synchronization process to update tag references and version delta files.

Can I automate version alignment for the FHI Designsystem across my Skills set?

Automating version alignment is supported by fetching the npm latest version, identifying tag references, and applying package revisions across the Skills set to keep public API changes accurate.