analyze-code
CommandAnalyze code quality, identify issues, and suggest improvements.
Add help content tooltips to existing UI elements.
> /plugin marketplace add nimbalyst/nimbalyst> /plugin install nimbalyst-wiki@nimbalyst
packageVersion: 1.0.0 packageId: core description: Add help content tooltips to existing UI elements.
Add help content tooltip to: {{arg1}}
Add a HelpTooltip to a UI element so users see helpful context on hover. This command handles adding the HelpContent entry, wrapping the element with HelpTooltip, and avoiding duplicate tooltips.
Read `docs/WALKTHROUGHS.md` for the complete guide on the help system architecture.
Find the UI element the user wants to add a tooltip to:
The element needs a `data-testid` attribute:
Add an entry to `packages/electron/src/renderer/help/HelpContent.ts`:
'my-feature-button': {
title: 'Feature Name', // 2-5 words, describes what it is
body: 'Description of what this feature does and why it is useful.', // 1-2 sentences
shortcut: KeyboardShortcuts.myFeature.action, // Optional - only if there's a keyboard shortcut
},Guidelines:
Import and wrap the element:
import { HelpTooltip } from '../../help';
<HelpTooltip testId="my-feature-button">
<button data-testid="my-feature-button" onClick={handleClick}>
Feature
</button>
</HelpTooltip>**CRITICAL**: Check if the element has a `title` attribute - this creates duplicate tooltips!
// BAD: Duplicate tooltips <HelpTooltip testId="my-button"> <button title="Click me" data-testid="my-button">Click</button> </HelpTooltip> // GOOD: No duplicate <HelpTooltip testId="my-button"> <button aria-label="Click me" data-testid="my-button">Click</button> </HelpTooltip>
For elements like dropdowns or popovers that have their own popup, use the inline help pattern instead:
import { getHelpContent } from '../../help';
const helpContent = getHelpContent('my-feature-button');
// Inside your existing tooltip:
{helpContent && (
<div className="tooltip-help-section">
<div className="tooltip-help-title">{helpContent.title}</div>
<div className="tooltip-help-body">{helpContent.body}</div>
</div>
)}For a group of related controls (like the LayoutControls), wrap the entire group with one HelpTooltip:
<HelpTooltip testId="layout-controls">
<div className="layout-controls" data-testid="layout-controls">
<button aria-label="Option 1">...</button>
<button aria-label="Option 2">...</button>
</div>
</HelpTooltip>1. `packages/electron/src/renderer/help/HelpContent.ts` - Add help content entry 2. The component file containing the target element - Add HelpTooltip wrapper
| Mistake | Solution | | --- | --- | | Leaving `title` attribute | Convert to `aria-label`, remove `title` | | Hardcoding tooltip text | Always use HelpContent registry | | Missing `data-testid` | Add descriptive `data-testid` to element | | Wrapping element with existing popup | Use inline help pattern instead | | Generic test IDs like `btn-1` | Use descriptive IDs like `file-tree-filter-button` |
Nimbalyst - The open-source visual workspace for Claude Code, Codex, and OpenCode. Run multiple coding agents in parallel, edit their work visually in markdown, mockups, and diagrams, and track tasks. Free, MIT-licensed desktop app for macOS, Windows, Linux, with mobile companion for iOS and Android.
Analyze code quality, identify issues, and suggest improvements.
Audit recent AI coding sessions to find repeated mistakes, speed losses, and missed Nimbalyst tool usage — then propose harness…
Triage pnpm audit findings and produce a prioritized, supply-chain-cautious package-update plan, then apply approved batches
Survey recently triaged GitHub issues, propose the ones safe to fix without a product decision, and fan the selected ones out to…
Gather details and draft an actionable bug report for developers.
Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or…