hex-local-dev-loop
Configure Hex local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Hex. Trigger with phrases like "hex dev setup", "hex local development", "hex dev environment", "develop with hex". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hex-local-dev-loop --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Hex Local Dev Loop ## Overview Set up a development workflow for Hex API orchestration with mocked API responses and testing. ## Instructions ### Step 1: Project Structure ``` hex-orchestrator/ ├── src/hex/ │ ├── client.ts # API client │ ├── orchestrator.ts # Pipeline runner │ └── types.ts # TypeScript interfaces ├── tests/ │ ├── fixtures/ # Mock API responses │ └── orchestrator.test.ts ├── .env
What does the hex-local-dev-loop skill do?
Configure Hex local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Hex. Trigger with phrases like "hex dev setup", "hex local development", "hex dev environment", "develop with hex". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hex-local-dev-loop --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.