# wasp-nest-core

wasp-nest-core is a hook for Claude Code and Codex that validates components and checks file edits. It runs on session starts and tool calls.

- hook · `type=hook` · Claude Code, Codex · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/hooks/claude-hooks.json
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text and 30 script files) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/hooks/wasp-nest-core

## What it does

This hook package connects Wasp Nest workflows to agent lifecycle events. On `SessionStart`, it triggers `register-codex-agents.py` via Python 3 and runs `onboarding-session.mjs` through Node.js. Both startup scripts run with a 10-second timeout.

When the agent issues `Edit` or `Write` operations, the suite intercepts the action. Before writing, `dash-guard.mjs` checks the output. Immediately after file changes apply, `component-validate.mjs` inspects the result with a 30-second timeout limit.

Without working `python3` and `node` binaries in your system environment, these scripts will fail immediately upon invocation.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install wasp-nest-core@wasp-nest
```

2. **Manually: put the files in place**
- File: `.claude/settings.json` — The hooks block: event (PreToolUse, PostToolUse, Stop…) → command. Personal ones go to ~/.claude/settings.json

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/hooks/claude-hooks.json

## When to use it
- register Codex agents when a new session begins
- inspect edit safety before executing `Edit` and `Write` actions
- validate UI components right after the agent writes changes

## Example prompts
- Edit the button component inside `src/Button.tsx`
- Create `src/Card.tsx` and write the initial component structure

## Similar
- [wasp](https://affpapa.org/en/nevibecode/plugins/wasp.md) — plugin · ★ 14 repo stars
- [nodejs-core](https://affpapa.org/en/nevibecode/skills/nodejs-core.md) — skill · 2100 installs
- [deep-agents-core](https://affpapa.org/en/nevibecode/skills/deep-agents-core.md) — skill · 16900 installs
- [iii-core-primitives](https://affpapa.org/en/nevibecode/skills/iii-core-primitives.md) — skill · 4900 installs
- [trader-memory-core](https://affpapa.org/en/nevibecode/skills/trader-memory-core.md) — skill · 3700 installs
- [nemo-relay-migrate-from-flow](https://affpapa.org/en/nevibecode/skills/nemo-relay-migrate-from-flow.md) — skill · 171 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
