Python stubs — active
High-fidelity .pyi definitions, overloads, geometric explanations, units, mutation notes, and RhinoPython examples.
Developer tooling / Rhino + Grasshopper
NexoNest Design Suite
Python and C# stubs that move Grasshopper scripting into modern external editors — with completion, type insight, documentation, and AI-assisted workflows.
Question
Why should coding inside a visual design environment mean giving up the tools of a modern editor?
Response
The suite describes RhinoCommon and Grasshopper APIs in editor-readable stubs, so code can be written externally and still understand the host environment.
Python-first
active verified stub track
C# companion
parallel API direction
Rhino 8
metadata-derived baseline
IDE native
completion, checks and AI context
01
Code outside. Run inside.
Grasshopper’s scripting editors are convenient but isolated. External editors provide navigation, completion, static checks, refactoring, source control, richer documentation, and AI assistance — but only when the editor understands the API.
Design Suite supplies that missing layer without pretending to replace Rhino or Grasshopper.
02
Two complementary tracks
C# companion — developing
A parallel metadata and editor-support direction for C# scripting workflows and API discovery.
Generated baseline
Public Rhino.Geometry types can be regenerated from RhinoCommon assemblies and official XML documentation.
Hand-curated learning layer
Frequently used geometry types receive explanations that teach why an API behaves as it does, not only its signature.
03
Trust requires verification
-
01
Extract
Read the installed RhinoCommon public surface and official documentation.
-
02
Generate
Build a consistent baseline while preserving curated foundation files.
-
03
Explain
Add geometric concepts, pitfalls, units, mutation behaviour, and short examples.
-
04
Verify
Check syntax, exports, public-type coverage, method names, and API drift.
04
What it enables
Better completion
Methods and overloads appear where code is being written.
Earlier feedback
Type and signature mistakes can surface before the script returns to Grasshopper.
AI with real context
Assistants can reason against a described API instead of inventing RhinoCommon members.
Learning in place
The editor becomes a computational-geometry reference during everyday work.
05
Current boundary
Honest status
The Python Rhino.Geometry track is the active implementation. Full namespace coverage, cross-version support, packaging, and the C# companion remain staged work — visible direction, not finished promise.