- Removed
.mcp.jsonfrom the plugin and gitignored it. A plugin-root.mcp.jsonis applied to every app that installs the plugin, so dev-only MCP servers no longer leak to consumers. Now local-only for each plugin developer.
using-hoist-core-reference: added a snippet-currency check to the preflight. The install snippet now ships with// hoist-ai-snippet: hoist-core-install/v<N>open/close markers so the skill can detect when an app's pasted snippet has drifted from the canonical (e.g. the Gradle API improvements landed in 1.4.4/1.4.5). On stale-snippet detection, the skill walks the user through an in-place refresh that preserves any local hand-edits. Working launchers keep working through the check -- the refresh is non-blocking and surfaced once per session.
using-hoist-core-reference: install snippet re-synced with the canonicalhoist-core/mcp/README.md. Brings in the bash launcher'sjava/JAVA_HOMEfallback for non-interactive MCP-client shells, the auto-emittedbin/.gitignore, and thelayout.buildDirectoryreplacement for deprecated$buildDir. Procedure step 6 rewritten to reflect the auto-scoped ignore -- no more two-stance commit/ignore choice.
using-hoist-core-reference: install snippet resolves the active hoist-core version lazily from the runtime classpath via a Provider. Eliminates the prior fallback that pushed agents to hardcode a version when hoist-core came in transitively via a client plugin.
- Both reference-skill
description:fields shortened to fit under Claude Code's per-skill listing cap. Previous versions exceeded the cap and were being silently truncated, dropping TRIGGER/SKIP detail before reaching the model. Trimmed symbol lists, redundant concept examples, and overspecific carve-outs while preserving the "Why this matters" lead and the TRIGGER/SKIP structure.
- Bug fix:
using-hoist-react-referencelauncher content moved out of SKILL.md fenced code blocks intotemplates/files, copied byte-exact at install. Embedded fenced content was losing a literal$0somewhere in the loading pipeline, yielding broken launchers. Launcher stamp bumped to force refresh of any mangled installs; preflight gains a smoke check. - Narrowed
using-hoist-react-referenceTRIGGER to changes that introduce or modify Hoist API usage, carving out config-only refactors that pass values through a Hoist component to a third-party lib (Highcharts, AG-Grid). - Both reference-skill descriptions: replaced "ALWAYS use this skill when..." with a "Why this matters:" lead citing concrete failure modes.
- Rewrote both reference-skill
description:fields per skill-creator best practices: single-paragraph format, concrete TRIGGER/SKIP blocks with keyword anchors. - Added trigger eval sets for both reference skills, re-runnable via skill-creator.
- CLAUDE.md: softened the eval bar to directional guidance -- the trigger-eval script has a measurement ceiling when simulating skills as slash commands.
using-hoist-react-reference: project-root CLI launchers (bin/hoist-docs,bin/hoist-ts) wrap the@xh/hoistbinaries so agents can invoke them from the harness's default cwd. Eliminates the "must run fromclient-app/" gotcha; the skill owns install.- Both reference skills: once-per-session preflight verifies launcher presence and stamp, with idempotent reinstall on drift. Plugin updates that bump the stamp self-propagate.
onboard-app: no longer wires the hoist-react CLI -- the reference skill installs it lazily.
hoist-upgrade: dropped the auto PR-creation step from Phase 5. The skill stops at the rendered summary; developers can ask the agent to follow up with whatever they want (open a PR, merge directly, etc.). Some environments don't haveghconfigured.using-hoist-react-reference: added a "CLI working directory" section reminding the agent thatnpx hoist-docs/npx hoist-tsmust be run fromclient-app/, not the project root. Agents commonly stumbled on this in practice.
hoist-upgrade: Phase 5 now renders the upgrade report directly in the chat instead of writing adocs/upgrade-reports/*.mdfile into the consuming project. The conversation is the artifact; developers can persist or discard as they prefer. Removed the now-unusedtemplates/upgrade-report.md.
hoist-upgradeandonboard-appare now model-invokable (disable-model-invocation: trueremoved from both). The agent will auto-discover them when developers describe matching intent. Slash-command invocation (/xh:hoist-upgrade,/xh:onboard-app) continues to work as before.
- Added two model-invokable reference skills:
using-hoist-react-reference(TypeScript / React,client-app/) andusing-hoist-core-reference(Groovy / Java, server-side). Both route to MCP tools when available, CLI tools (npx hoist-docs/npx hoist-ts/./bin/hoist-core-*) otherwise, so MCP-blocked enterprise environments stay productive. Each ships with anevals/suite gated at >=90% recall / <=10% false-positive rate. using-hoist-core-referenceis the canonical source for installing or upgrading the hoist-core MCP+CLI tools (installHoistCoreToolsGradle task, project-localbin/launchers).onboard-app: new Phase 3.5 detects whether the hoist-core MCP+CLI tools are installed and offers to install them whenhoistCoreVersion >= 39.0. Phase 1 gained SNAPSHOT-aware version comparison. Verification reframed CLI-first / MCP-opportunistic so MCP-blocked environments don't stall.hoist-upgrade: Phase 3e refreshes project-localbin/hoist-core-*launchers whenhoistCoreVersionis bumped (avoiding stale absolute JAR paths). Surfaces hoist-core MCP+CLI install eligibility when the bump crosses the v39.0 floor. Phase 4 verification reframed CLI-first.- Pre-approved
Bash(./bin/hoist-core-*:*)andBash(./gradlew installHoistCoreTools:*)insettings.jsonso consumers don't get prompt-flooded on the install happy path. - Removed the
feedbackskill -- requiredghauth and outbound toxh/hoist-ai, not viable in target enterprise environments.
- MCP server config moved from the plugin's
.mcp.jsonto per-project.mcp.jsonmanaged by the onboarding skill. Plugin-cache-relative paths weren't resolving in consuming projects; the project now owns the config. onboard-app: added client-plugin detection and an expanded CLAUDE.md template.
- Fixed the plugin MCP config to point at the bundled hoist-react server.
- Added
enabledMcpjsonServersso the hoist-react server is auto-approved on install.
- Initial release. The
xhplugin in thehoist-aimarketplace, with three skills:onboard-app,hoist-upgrade, andfeedback.