niclaslindstedt

Use whenever you are iterating on the look or layout of a screen — tuning a CSS rule, building a new modal, redesigning a table, hunting a mobile-only regression. Walks an edit / reload / screenshot / inspect loop that uses the Read tool to view PNGs inline at every viewport (desktop, mobile, mobile-landscape, tablet). The harness drives the app through reusable flows (sign in, add sheet, add account, swipe a row) so each iteration only changes the bit that's being designed. Manual playbook — not part of the `maintenance` umbrella.

Use when the user wants to clear out the open Dependabot PRs — "do the dependabot PRs", "update the deps", "merge dependabot". Consolidates every open Dependabot bump into ONE branch + PR, resolves the peer-dependency fallout the bumps trigger (Vite / ESLint / TypeScript / React majors drag transitive tooling with them), gets the full CI chain green, then closes the superseded Dependabot PRs. Manual playbook — not part of the `maintenance` umbrella.

Use when src/data/achievements/catalog.ts is stale relative to a newly-shipped user-facing feature — or when a fresh achievement needs to be added, a trigger predicate rewritten, or the AchievementsModal chrome touched. The achievements modal (src/components/AchievementsModal.tsx) is a fullscreen four-tier (Beginner → Intermediate → Pro → Expert) guided tour where every feature is also an unlockable trophy. This skill describes how to add a new achievement, how to slot it into the right tier, how to phrase it (in English AND Swedish), and how to wire its trigger so the unlock fires when the user does the thing.

Use when about to open a PR (or just after pushing one) to decide whether the change needs a `.changes/unreleased/<unix-ts>-<slug>.md` fragment. Resolves the latest `v*` tag, walks commits and existing fragments since, classifies the current change against the rules in AGENTS.md, and either writes a new fragment, folds the substance into an existing fragment, or labels the PR `no-changelog`.

Use when docs/ may be stale relative to src/ layout, the persisted-data shape, or the Makefile target table — or when the in-app privacy policy at src/components/PrivacyPage.tsx may be stale relative to the storage/encryption/Dropbox claims it restates. Discovers commits that touched those sources of truth since the skill last ran and merges the current shape back into docs/architecture.md, docs/getting-started.md, and the privacy page.

Use when the maintainer (or an agent acting on their behalf) wants to cut a new release of the Budget app. Walks the pre-flight checklist, dispatches the workflow, verifies the deploy, and links to the rollback recipe. Manual playbook — not part of the `maintenance` umbrella.

Use when the user asks for high-value performance optimizations — order-of-magnitude wins in algorithms that matter, not micro-tuning. Surveys the hot paths (reducers, per-render passes, per-keystroke handlers, validators, synthesis pipelines, search indexes), presents candidates with complexity and trigger context for the user to gate the work, and is honest when the codebase has already been tuned and no high-value wins remain.

Use when the user wants comments cleaned up, or whenever you're about to touch a file whose comments narrate history instead of explaining current invariants. Removes or rewrites changelog-style comments ("previously", "the legacy behaviour", "see the plan", "used to re-scan", "K calls × O(R) before this fix", PR-number references, wiring narratives) while preserving comments that explain WHY current code is the way it is — especially "don't try X, it doesn't work" anti-pattern guards.

Use when the user wants to add, update, or remove entries in the CV (src/data/cv.json), or wants recommendations on what to add, remove, or emphasize. Always validates the result against schemas/cv.schema.json before finishing.

Use when the Visual workflow (.github/workflows/visual.yml) is failing on `main` or on a PR. Reproduces the failure, identifies which commit broke each snapshot, decides whether the diff is intentional, re-records baselines if so, and commits the new pixels.

Use when the user wants to clean up the open Dependabot PR queue. Walks the open Dependabot PRs newest-first, merges the green ones, then rebases and fixes the CI-failing ones, pushes, waits for CI, and merges.

Use to bring the whole repo back in sync after a batch of changes. Routes to every update-* skill in deterministic order and aggregates the resulting diff.

Use when this repo may have drifted out of conformance with OSS_SPEC.md. Runs the bash mirror of the oss-spec validator (no Rust toolchain required), walks the violations, and fixes each one until the validator reports zero violations.

Use when the user wants to refresh the `tagline` and/or `description` of one or more companies in `src/data/cv.json` using their declared `sourceUrls`. Fetches each source, synthesizes a tight bilingual tagline + description pair, propagates the change into any matching `experience[].printDescription` (and assignment `printDescription` when the assignment's `clientId` resolves to a company being refreshed), and validates the result.

Use when files under docs/ may be stale. Discovers commits since the last docs sweep and reconciles each docs/*.md file with its sources of truth (component CSS, schemas, search index, design tokens).

Use when the user wants to refresh the hero summary and the click-to-expand long summary in src/data/cv.json. The skill is interactive — it asks two short questions (where you are now / where you are going) before rewriting, so the long summary never hallucinates.

Use when the repository may have drifted out of conformance with OSS_SPEC.md. Runs `oss-spec validate .`, walks the violations, and fixes each one so the self-conformance test keeps passing.

Use when prompts under prompts/ may be stale. Discovers changes to OSS_SPEC.md, the validator, manifest enums, and the ai/fix glue since the last run, and rewrites the affected prompt templates so they stay aligned with their sources of truth.

Use when files under docs/ may be stale. Discovers commits since the last docs update, maps changed source files to affected conceptual documentation, and brings docs/*.md back into sync with the implementation.

Use when README.md may be stale. Discovers commits since the last README update, identifies what changed (CLI flags, subcommands, §19 rules, supported languages, spec version), and updates the affected README sections.

Use when OSS_SPEC.md has been edited. Bumps the spec version field, propagates the new mandate through validate.rs, tests, templates, docs, README, AGENTS.md, and the self-conformance test.

Use when you want to bring every drift-prone artifact in the repo back into sync. Dispatches to all individual update-* skills in the correct order, aggregates their results, and leaves a single combined PR ready to review.

Use when files under man/ may be stale. Discovers commits since the last manpage update, maps changed CLI definitions to affected pages, and updates man/<cmd>.md to match the current clap definitions.

Use when the marketing website may be stale. Discovers commits since the last website update, re-runs the source-extraction script, and updates website/ content so that generated pages match the current README, docs, and spec.

Use when you want to bring every drift-prone artifact in the repo back into sync. Dispatches to all individual update-* skills in the correct order, aggregates their results, and leaves a single combined PR ready to review.

Use when spotifai may have drifted from OSS_SPEC.md. Fetches the latest spec from GitHub, walks its mandates, and fixes each violation so the repository keeps conforming. Runs standalone — it does not shell out to any external validator binary.

Use when files under docs/ may be stale. Discovers commits since the last docs update, maps changed source files to affected conceptual documentation, and brings docs/*.md back into sync.

Use when files under man/ may be stale. Discovers commits since the last manpage update, maps changed CLI definitions to affected pages, and updates man/<cmd>.md to match the current implementation.

Use when LLM prompts under prompts/ may be stale. Discovers changes since the last run and rewrites the affected prompt templates so they stay aligned with their sources of truth.

Use when README.md may be stale. Discovers commits since the last README update, identifies what user-facing surfaces changed, and brings README.md back into sync.

Use when the marketing website may be stale. Discovers commits since the last website update and refreshes source-derived content under website/ so generated pages match the current README, docs, and spec.

Commit staged changes, push the branch, and create or update a PR with a conventional-commit-formatted title. Use after completing a feature or fix.