vibekit
Add @randroids-dojo/vibekit (https://github.com/Randroids-Dojo/VibeKit) as a dependency and look up per-module usage patterns. Optional companion to the spiral skill; replaceable with a different shared-library skill if a project prefers another component source. Slash commands /vibekit-add and /vibekit-cookbook live under commands/.
What this skill does
# VibeKit
`@randroids-dojo/vibekit` is the in-house reusable-component library this workspace's game projects share. The default entry exposes framework-agnostic client modules (virtual-joystick, editor-history, confetti, rng, math, storage); the `./server` subpath exposes Node-only helpers (kv, sign, rate-limit) locked to `@upstash/redis` + `node:crypto`.
This skill is the bootstrap-and-cookbook layer for VibeKit. It is intentionally optional and lives alongside `spiral` (structural-discipline scaffold) and `randroid:loop` (research / implement loops) the same way: spiral defers to randroid:loop for execution; spiral defers to *this* skill for VibeKit-specific bootstrap and component usage. A project that prefers a different shared library swaps this skill out without touching spiral's gate, ledger, or loop machinery.
## When to invoke
- **`/vibekit add`**: from inside a project repo. Adds `@randroids-dojo/vibekit` as a `github:` tag-pinned dependency in `package.json`, and prints (does not auto-write) the matching `DEPENDENCY_LEDGER.md` entry to paste into the project's spiral ledger.
- **`/vibekit cookbook`**: surfaces the per-module usage cookbook (`docs/cookbook.md` in this skill). Use when wiring up a specific module (joystick, storage, kv, sign, ...) or when the kit's own README isn't enough and you want the "how to compose this in a Next.js / React project" view.
## How this skill relates to spiral
- **Spiral** defines the Dependency Upgrade Gate, the ledger format, and the upgrade procedure (read CHANGELOG, branch, bump, type-check, test, build, smoke, PR with `chore(deps):` title). It does not know about any specific dep. See `plugins/spiral/templates/DEPENDENCY_LEDGER.md`.
- **VibeKit** (this skill) supplies the worked example for the spiral ledger and the cookbook for wiring up each module. A project that uses VibeKit gets a richer ledger entry (with import snippets) and a cookbook reference; a project that prefers a different shared library follows the same spiral procedure with that library's own skill.
- **Randroid loop command** is the slice executor. It reads spiral's ledgers + AGENTS.md, picks the next slice, branches, implements, opens a PR. When a slice is "bump VibeKit from vX to vY" it follows spiral's procedure; this skill's cookbook tells it which migration patterns are common per module.
## Composition
```
spiral (methodology + scaffold + Dependency Upgrade Gate)
├─ defers execution to randroid:loop
└─ defers VibeKit-specific bootstrap + cookbook to vibekit (this skill)
```
Replace any leg without affecting the others.
## Architecture
```
vibekit/
├── SKILL.md # This file
├── README.md # Human-facing one-pager
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── commands/
│ ├── vibekit-add.md # /vibekit add slash command
│ └── vibekit-cookbook.md # /vibekit cookbook slash command
├── docs/
│ └── cookbook.md # Per-module usage cookbook
└── scripts/
└── add.sh # Bootstrap into a target repo
```
## What's in the kit
The kit lives at https://github.com/Randroids-Dojo/VibeKit. Releases are cut by release-please on every push to its `main`; tags follow `vX.Y.Z`. Pre-1.0 the kit treats every `feat:` as a patch via `bump-patch-for-minor-pre-major`, so any patch tag may carry signature changes; consumers read the CHANGELOG between pinned and target.
Default entry (`@randroids-dojo/vibekit`):
- `virtual-joystick`. Float-where-you-tap touch joystick state.
- `editor-history`. Generic `EditorHistory<T>` undo / redo stack.
- `confetti`. Pure particle simulation for celebration overlays.
- `rng`. Seeded Mulberry32 PRNG plus `range`, `pick`, `gauss`.
- `math`. `TAU`, `clamp`, `lerp`, `inverseLerp`, `remap`, `smoothstep`, `wrapAngle`.
- `storage`. Defensive zod-validated `localStorage` helpers with cross-tab + same-tab change events.
Server entry (`@randroids-dojo/vibekit/server`, Node-only):
- `kv`. `getKv` cached singleton (null on missing env), `readKv<T>` zod-validated, `writeKv` with optional TTL, `removeKv`, `resetKvForTesting`.
- `sign`. HMAC-SHA256 `signToken` / `verifyToken` with constant-time comparison.
- `rate-limit`. `incrementWithExpiry` fixed-window primitive (returns post-increment count).
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.