By bringfire
Rook — AI bridge for Rhino 3D & Grasshopper. Skills for designing, planning, and executing Grasshopper definitions, 3D road design, and LLM-powered Chirp components via MCP tools.
Extract layer, material, and block organization conventions from a reference Rhino file and write a .rook/conventions.yaml file. Use this skill whenever the user mentions: "capture convention", "extract convention", "save layer template", "create convention file", "layer standards", "what are my conventions", or when /project-setup offers to capture from a reference file. Also use when the user opens a "template" or "standard" file and wants to formalize its structure for reuse across projects.
Build reasoning cascades of Chirp components from natural language design briefs. Creates multiple LLM-embedded Grasshopper components with Reasoning pin fan-out for multi-discipline design coherence. Triggers: "chirp cascade", "reasoning cascade", "design language cascade", "chirp pattern", building multiple Chirp components that share reasoning context, setting up Wasp aggregation with semantic configuration, Wasp grammar authoring, graph-grammar cascade, production rule generation, or any workflow requiring coordinated LLM reasoning across GH components.
Create a single Chirp component on the Grasshopper canvas. Requires a category (planner, interpreter, critic, narrator, classifier, gate, editor) and a design context. Triggers: "chirp component", "add a chirp", "create a chirp planner", "chirp interpreter", "I need a critic", "add a gate", "chirp editor", or any request to create a single LLM-embedded Grasshopper component.
Compare a Rhino file's layer structure against its .rook/conventions.yaml and propose cleanup changes. Audit-first, never destructive without approval. Triggers: "clean layers", "cleanup layers", "fix layers", "organize layers", "layer cleanup", "apply convention", "check layer standards", or when the user has a conventions.yaml and wants to bring a file into compliance.
Collaborative Grasshopper definition design through exploration, Q&A, and incremental validation. Use when the user wants to build a GH definition, parametric model, or visual programming workflow. Triggers on: "design grasshopper", "create GH definition", "build parametric", "grasshopper workflow", or any request for a multi-component Grasshopper definition. Produces a design document that feeds into plan-grasshopper.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
AI agents for Rhino 3D and Grasshopper.
Operate Rhino and Grasshopper by talking to your AI assistant — nearly 400 MCP tools for geometry, analysis, scripting, layers, blocks, documents, vision, BIM, and more.
Rook gives your AI assistant direct, capable access to Rhino 3D and Grasshopper. You describe what you need; Rook does it in your live model. It's not an autopilot that designs for you — it's a collaborator that helps at whatever stage you're in, and it's flexible enough that you decide what that help looks like: heavy geometry and analysis, Python/C# Grasshopper scripts, layer and block management, document-level operations, visualization, and more.
Works with any MCP-capable assistant (Claude Code, Codex, and others) and any model provider (Claude, GPT, or local models) — bring your own key.
Full, step-by-step instructions: https://bringfire.github.io/rook-release/start/install/
Rook also ships as a Claude Code plugin (guided skills + a session hook). After installing, you can manage it via the marketplace:
/plugin marketplace add bringfire/rook-release
/plugin install rook@rook
Rook is local-first and bring-your-own-key — your designs, prompts, and results stay on your machine. See PRIVACY.md.
© 2026 Bringfire Games, LLC. All rights reserved. The source repository remains private. This public repo contains docs, plugin metadata, and release assets. The installer includes runtime implementation files required for the local MCP server and Python-based components to run on your machine.
npx claudepluginhub bringfire/rook-release --plugin rookCore skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Intelligent prompt optimization: injects the right context at the right moment so Claude lands a better first output. Clarifies vague prompts with research-based questions, plus targeted nudges for approach selection, plan readability, workflow routing, background execution, subagent routing, output readability, user-decision questions, and plan-mode assessment
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation