plan-gesso-upgrade
Plans update of theme to the next Gesso 5 release
What this skill does
Create a plan to update Gesso to the next upstream release. Write the complete plan to one or more Markdown files. ## 1. Determine the theme and generate the diff **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 bash path/to/plan-gesso-upgrade/scripts/get-gesso-diff.sh > gesso-update-diff.diff ``` ## 2. Review the diff Read `gesso-update-diff.diff` in full to understand what has changed. The changes may include: - npm package version updates - npm packages installed or removed - additions or edits to code - removal of code - updated version number - README or documentation updates ## 3. Create the plan 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. ### Requirements 1. Group related changes together and break the work into multiple phases. 2. Write a plan with to-do items for each phase of work to a Markdown file 3. When the diff includes README changes, include a phase or to-do for updating the theme’s README file. 4. If there are any changes in the diff that you will not implement, explicitly note that at the top of the plan. ### What Not to Include 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. ### Outcome 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.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.