npx claudepluginhub forumone/f1-genai-starter --plugin gesso-upgraderThis skill is limited to using the following tools:
Create a plan to update Gesso to the next upstream release. Write the complete
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Create a plan to update Gesso to the next upstream release. Write the complete plan to one or more Markdown files.
1a. Determine which Gesso theme is installed.
Inspect the theme’s package.json. The name field identifies the flavor:
"name": "gesso" → Gesso (standard). Use the forumone/gesso repo for the diff."name": "guswds" → Gesso USWDS. Use the forumone/gesso-uswds repo for the diff.1b. Generate the diff.
Run the get-gesso-diff.sh script. It detects the theme from package.json
and fetches the diff from the correct GitHub repo. Write the script output to
gesso-update-diff.diff.
The script lives in the scripts/ directory next to this SKILL.md file. Locate
this SKILL.md using a glob search for **/plan-gesso-upgrade/SKILL.md, then
derive the script path from that location.
bash path/to/plan-gesso-upgrade/scripts/get-gesso-diff.sh > gesso-update-diff.diff
Read gesso-update-diff.diff in full to understand what has changed.
The changes may include:
Create a plan to apply all changes in the diff to the current theme. The plan will be executed by another agent.
Your plan should also account for other changes in the theme that result from the changes in the diff.
EXAMPLE: A renamed Twig function must be updated in every file that it is used, including Twig files that are unique to this theme
When the diff includes changes to the upstream README, include in the plan a
phase or step to update the theme’s README (e.g. README.md in the theme
directory). The plan should specify which sections or information from the
upstream README to merge or apply, and how to preserve theme-specific content.
Do not add or remove npm packages unless they are added, removed, or have a version number change specifically in the diff. The theme's package.json does not have to be identical to the upstream package.json.
If a file was modified in the diff, not added, and the file does not exist in the theme, do not create it. Note that change as a change you will not implement.
When finished, your Markdown files must include all the information another agent needs to fully implement the changes.
You must tell the user where to find the plan files when finished.