yuhaosimba

Use when the molstar-structure-editor plugin has broken gizmo picking, dragging that rotates the camera instead, stale structure rendering, selection resolution failures, or commit/cancel state issues.

Use when modifying the molstar-structure-editor plugin, extending edit behavior, changing gizmo interaction, or working on Mol* coordinate-driven structure editing in this repository.

Use before claiming a molstar-structure-editor change is complete, fixed, or ready to commit, especially after touching interaction code, coordinate updates, or the example viewer.

Use when modifying XpongeCPP C++ core, Python bindings, topology, force-field parsing, solvation, assign, or SPONGE export code. Enforces Xponge parity-first implementation, flat C++ data structures, strict safety checks, and no ad-hoc topology rules.

Use when migrating, extending, or testing XpongeCPP Assign and Amber GAFF atom typing against original Xponge, especially for mol2 inputs, AssignRule parity, ring markers, bond markers, and 100-molecule validation sets.

Use when planning or executing migration of an Xponge workflow into XpongeCPP, especially Amber protein-ligand-solvent workflows such as 1KV2+B96. Provides the parity checklist, baseline procedure, implementation order, and acceptance criteria.

Use when extending, repairing, or auditing the Packmol Fortran test baseline under pixi and CTest, especially when adding direct interface coverage or refreshing the procedure inventory

Use when replacing Packmol Fortran procedures with C++ implementations, especially during mixed-language migration where interface-level tests must remain the release gate