guidewire-local-dev-loop

Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time. Use when standing up Guidewire Studio against a local InsuranceSuite instance, attaching an IntelliJ remote debugger to runServer, distinguishing changes that hot-reload from changes that force restart, or building a GUnit-driven TDD cycle for rule logic. Trigger with "guidewire studio", "gosu hot reload", "gosu debugger", "gunit", "guidewire runServer".

Ir para a instalação

Repositório: jeremylongshore/claude-code-plugins-plus-skills
Última atividade na origem: 17 de julho de 2026 às 22:18
Idioma detectado do SKILL.md: inglês
Estrelas: 2.604
Forks: 378

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill guidewire-local-dev-loop

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

3 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

clerk-core-workflow-a

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

2026-07-23

clerk-core-workflow-b

Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".

2026-07-23

clerk-enterprise-rbac

Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".

2026-07-23

Ver todas deste repositório

name	guidewire-local-dev-loop
description	Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time. Use when standing up Guidewire Studio against a local InsuranceSuite instance, attaching an IntelliJ remote debugger to runServer, distinguishing changes that hot-reload from changes that force restart, or building a GUnit-driven TDD cycle for rule logic. Trigger with "guidewire studio", "gosu hot reload", "gosu debugger", "gunit", "guidewire runServer".
allowed-tools	Read, Write, Edit, Bash(gradle:), Bash(java:), Bash(jdb:*), Grep, Glob
version	1.25.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw
tags	["guidewire","gosu","studio","hot-reload","gunit","debugging"]

Guidewire Local Dev Loop

Overview

Run a local InsuranceSuite instance and iterate on Gosu rule logic in seconds, not minutes. The single biggest productivity killer in Guidewire development is paying the 5–15 minute gradle runServer cold-start cost on every change because the developer does not know which edits hot-reload and which force a restart.

Three production problems this skill prevents:

Restart cascade — developer changes a Gosu rule, restarts runServer, waits 8 minutes, finds the rule was wrong, repeats. A full day disappears in restarts.
Silent stale code — Studio claims it hot-reloaded a class but the running JVM is still executing the old bytecode (common when interfaces change). Tests pass against stale code.
GUnit drift — unit tests for Gosu rules diverge from the rules themselves because the cycle to run a single test through Studio is too slow; developers stop writing them.

Prerequisites

JDK 17 (for Cloud release 202503+)
Guidewire Studio installed (IntelliJ-based, distributed by Guidewire)
Local InsuranceSuite configuration zone (PolicyCenter, ClaimCenter, or BillingCenter)
≥16 GB RAM on the dev machine — runServer + Studio + the JVM debug agent need headroom
Sample data loader configured for the chosen product (e.g., PersonalAuto for PC)

Instructions

Build the inner loop in this order. Every step targets one of the three productivity killers above.

1. Start runServer once, keep it warm

Cold start takes 5–15 minutes; treat it as a session investment.

# Start in dev mode with debug agent on 8088, leaves the server attached to the terminal
./gradlew runServer -Pdebug=true -PdebugPort=8088 -Dgw.servermode=dev

gw.servermode=dev enables the hot-reload paths inside the JVM. debugPort=8088 exposes the JDWP debug agent — attach IntelliJ to it once and leave it. Restart only when the what hot-reloads table below says you must.

2. What hot-reloads, what does not

Memorize this table — it determines whether the next edit costs 0 seconds or 8 minutes.

Change type	Hot-reload?	Action
Gosu method body in an existing class

Symptom	Cause	Solution
Code change "saved" but breakpoint fires on old line numbers	hot-reload silently failed (interface change, plugin registry edit)	restart runServer; do not chase phantom bugs
`gradle runServer` hangs at `Starting server` for >20 min	full database rebuild from a recent schema change	check logs in `logs/PolicyCenter.log`; if schema migration is running, wait it out; if hung, `dropAndCreateDatabase`
GUnit test passes locally, fails in CI	dev database carries stale data the test depends on	tests must self-fixture (`@Before` loads needed entities); never trust ambient sample data
IntelliJ debugger drops every few minutes	runServer crashed and auto-restarted under a launcher	check `logs/PolicyCenter.log` for OOM; raise `-Xmx` in `gradle.properties`
Hot reload works on Day 1, stops working after a `git pull`	merged change touched the plugin registry without your local picking it up	restart; rebase pulls do not always invalidate the plugin cache
`ClassCastException` on a class you just edited	binary-incompatible change to a non-interface class (e.g., changed a public field type)	restart; field-type changes are interface-equivalent for the JVM
Breakpoint set in Gosu, never hits	the rule path is not actually exercised by the test action	verify in `logs/PolicyCenter.log` that the rule fired; common cause is rule conditions filtering out the test data
Studio shows red error markers everywhere after pulling main	dependency cache stale	`./gradlew clean compileGosu` (don't `clean` the whole project — it nukes runServer's database)

guidewire-local-dev-loop

Opções de instalação

Revise os arquivos de origem

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

3. Attach the IntelliJ debugger once per session

4. GUnit cycle for rule TDD

5. Sample data isolation per session

Output

Examples

Example 1 — Pure rule edit, zero restart

Example 2 — Interface change, controlled restart

Example 3 — TDD cycle on a new validation rule

Error Handling

See Also

Resources

guidewire-local-dev-loop

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

3. Attach the IntelliJ debugger once per session

4. GUnit cycle for rule TDD

5. Sample data isolation per session

Output

Examples

Example 1 — Pure rule edit, zero restart

Example 2 — Interface change, controlled restart

Example 3 — TDD cycle on a new validation rule

Error Handling

See Also

Resources