grasshopper-plugin-development
/grasshopper-plugin-development
Develop or revise C# Grasshopper plug-ins for Rhino, including component contracts, custom data, state and persistence. Use for new components, architecture changes, or diagnosing host integration; use the focused icon, interaction, testing, or release skills for those specific tasks.
- Author
- ChenmingHe0126 ↗
- Repository
- grasshopper-plugin-development ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Develop or revise C# Grasshopper plug-ins for Rhino, including component contracts, custom data, state and persistence. Use for new components, architecture changes, or diagnosing host integration; use the focused icon, interaction, testing, or release skills for those specific tasks.
Original author description
Develop or revise C# Grasshopper plug-ins for Rhino, including component contracts, custom data, state and persistence. Use for new components, architecture changes, or diagnosing host integration; use the focused icon, interaction, testing, or release skills for those specific tasks.
How it works
- Establish the component contract
- Separate computation from the host
- Route only the work needed
- Complete with evidence
SKILL.md preview
--- name: grasshopper-plugin-development description: Develop or revise C# Grasshopper plug-ins for Rhino, including component contracts, custom data, state and persistence. Use for new components, architecture changes, or diagnosing host integration; use the focused icon, interaction, testing, or release skills for those specific tasks. --- # Grasshopper plug-in development Build the requested behavior in the existing plug-in's conventions. Inspect the repository before choosing a project layout, target framework, dependency version, or loading strategy. ## Establish the component contract Read [component-contracts.md](references/component-contracts.md) when adding or changing parameters, custom data, persistent state, or component identity. Establish: - The actual Rhino version, OS, selected .NET runtime, project target frameworks, and SDK references. - Which existing component is the closest host-integration example. - Inputs and outputs, units, item/list/tree access, empty and invalid-data behavior, and when state continues, invalidates, or resets. - Component and assembly identities, archived definitions that must keep loading, and resource naming. For internalised custom values, read [custom Goo persistence](references/custom-goo-persistence.md) before choosing archive ownership and schema. Keep released component GUIDs stable. Changes to parameter order/types or serialization keys require a compatibility decision and a save/reopen check, not just a successful compile. ## Separate computation from the host Use [Moyu patterns](references/moyu-patterns.md) for source-inspected examples and their limitations. Keep algorithms and simulation state independent of Rhino when that improves testability. Let components own input translation and published outputs; let session/display adapters own host callbacks and their lifetime. A stateless component does not need a session abstraction. For iterative computation, establish invalidation and ownership before adding a timer. Bound work where it can actually be interrupted. A wall-clock check between iterations cannot interrupt one long iteration. Do not expose mutable solver buffers as historical results. Decide whether custom Goo duplicates own their data and whether internalised values can survive archive loading. Shared references and immutable-by-convention snapshots need explicit treatment. ## Route only the work needed The following are independently usable companion skills in this collection: - `grasshopper-interaction-display`: custom GH attributes, Rhino display, input, focus, live sessions, DPI, language, and UI persistence. - `grasshopper-testing`: core tests, host integration, document round trips, and actual UI acceptance. - `grasshopper-build-release`: runtime matrix, resources, packaging, and release evidence. - `grasshopper-icons`: function-first icon families and real 24px export. If a companion skill is unavailable, inspect the project's own implementation and authoritative SDK documentation; do not pretend it was loaded or block unrelated work. ## Complete with evidence Run validation appropriate to what changed. Report the resulting behavior, the artifacts changed, the checks actually executed, and any remaining host-only verification. Preserve the user's existing authorization and scope when installing, publishing, or modifying other applications.
Files in this package (5)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/component-contracts.md 6 KB
- references/custom-goo-persistence.md 4 KB
- references/moyu-patterns.md 7 KB
Versions
The database has no other skills named grasshopper-plugin-development.
Database snapshot: 13.11.2026 · package version 1877f2e7e14f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100grasshopper-testing
Validate Grasshopper components and Rhino plugins with pure-core tests, host integration, saved-definition round trips, and real canvas or viewport checks. Use when testing plugin behavior or diagnosing host-specific test failures. - 100grasshopper-build-release
Build, package, or prepare releases of Rhino Grasshopper C# plug-ins. Use for target-runtime compatibility, embedded resources, locked or stale assemblies, version agreement, Yak distributions, dependency layout, and installation checks. - 98rhino-gh-vscode-setup
Create a Grasshopper plug-in project that builds and debugs from VS Code with F5 (Rhino 8, Windows). Use when asked to set up, scaffold or initialise a Grasshopper (.gha) plug-in project, or to make VS Code behave like Visual Studio for Rhino and Grasshopper development, in a folder the user names. - 90execute-grasshopper
Use when the user asks to build or modify a Grasshopper definition through Rook. - 100sofistik-rhino-cdb
Write C# scripts for the Grasshopper C# Script component or the Rhino script editor that read a SOFiSTiK CDB database (*.cdb) through the SOFiSTiK.Analysis.Database assembly - geometry, analysis results, cross sections, tendons and axes. Use this skill whenever the user wants to… - 90design-grasshopper
Use when a Grasshopper request is ambiguous or open-ended and the user needs alternatives, constraints, or acceptance criteria clarified.