smarkwal

Add or modify visual styles in the PictureTriage JavaFX application. Covers the CSS token system, JavaFX-specific CSS properties, pseudo-classes, how to apply styles from Java code, and how to trace which files use a given CSS selector. Triggers: style, CSS, color, spacing, font, button appearance, layout padding, visual, JavaFX CSS.

Update library versions or Gradle plugin versions in the PictureTriage project. Covers the full safe update workflow: check for new versions, edit build.gradle.kts, regenerate the lockfile, and verify the build. Triggers: update dependency, upgrade library, bump version, check for updates, new version.

Review and update project documentation for accuracy against the current codebase. Use when adding a class, renaming a type, changing workflow phases, updating dependencies, or modifying the package structure. Covers README.md, ARCHITECTURE.md, copilot-instructions.md, and SKILL.md files. Triggers: review docs, update documentation, update README, review ARCHITECTURE, sync docs, documentation review, doc sync, stale docs, inaccurate docs, docs out of date.

Write or review unit tests in the PictureTriage project. Use when adding tests for service classes, domain types, or utility classes. Covers test structure, naming, JUnit 5 conventions, and what can/cannot be tested without JavaFX. Triggers: unit test, write test, add test, test coverage, JUnit.

Find and remove unused code in the PictureTriage project. Use when agent changes have left behind orphaned Java classes, methods, or fields, or unused CSS style rules in application.css. Triggers: cleanup, dead code, unused code, orphaned code, stale code, remove unused.

Audit and remove dead code from the codebase. Use for: finding unused Java parameters, fields, methods, imports; unused CSS classes/rules; unused JS exports or functions; removing leftover symbols after refactors; cleaning up after feature removal. Produces a report first, then removes each item after confirmation.

Review documentation files for consistency with the codebase. Use for: checking README.md, copilot-instructions.md, and other markdown docs for outdated class names, package names, method names, config keys, build commands, source layout, tech stack versions, and missing or incorrect information; also detect duplicated information across docs and suggest deduplication with a canonical source. Reports all inconsistencies and asks for confirmation before fixing.

Review and update the JarHC project documentation under website/docs/. Use this whenever the user wants to review documentation, update or rewrite a docs page, check whether documentation is stale or out of date relative to the code, verify that a report-section page still matches its analyzer, or add a new documentation page. Also use it after changing source code (analyzers, command line options, dependencies) that the documentation describes, to find and refresh the affected pages. It can run a freshness check that flags pages whose sources changed after their last review.