You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Improve labels and descriptions on hover for mechanical diagrams #41
When generating mechanical/engineering diagrams (e.g. car axle visualizations), the labels and descriptions are static and can clutter the diagram. Hover interactions would make the diagrams cleaner while keeping information accessible.
Current behavior
All labels (e.g. "axle shaft", "splits torque", "vehicle load") are always visible
Legend items at the bottom take up space
Descriptive text is static
Proposed improvement
Show concise labels by default, reveal detailed descriptions on hover
Add hover tooltips to diagram components (wheels, differential, axle shafts)
Consider collapsible legend or hover-triggered legend highlights
Improve label positioning and readability for complex diagrams
Context
This came up when testing mechanical/engineering diagram generation — the widget renderer produces good visualizations but the information density could be better managed with interactive hover states.
Hi, I'd like to work on this issue. I checked the current SVG diagram guidance in apps/agent/skills/svg-diagrams/SKILL.md and its MCP counterpart; both currently favor static side annotations.
I propose a focused update to those guides: keep short part labels visible, reveal longer explanations on hover and keyboard focus, and provide a tap/click path for touch devices. I would include a small working diagram pattern and check it in a browser for pointer, keyboard, and narrow-screen use. This should improve generated mechanical diagrams without changing the sandbox renderer.
Activity
ArianMoeini commentedon Oct 3, 2026
Hi, I'd like to work on this issue. I checked the current SVG diagram guidance in
apps/agent/skills/svg-diagrams/SKILL.mdand its MCP counterpart; both currently favor static side annotations.I propose a focused update to those guides: keep short part labels visible, reveal longer explanations on hover and keyboard focus, and provide a tap/click path for touch devices. I would include a small working diagram pattern and check it in a browser for pointer, keyboard, and narrow-screen use. This should improve generated mechanical diagrams without changing the sandbox renderer.
Does that match the direction you want for #41?