React component patterns, hooks, naming conventions, and the query-language translation system for Graph Explorer.
64
47%
Does it follow best practices?
Impact
96%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.kiro/skills/react/SKILL.mduseMemo, useCallback, and React.memo are unnecessary in most cases and should be avoided unless profiling shows a specific needsrc/modules/ contain all related components, hooks, and utilitiesGraphViewer.tsx)use prefix (e.g., useGraphData.ts)The translation system is not used for locale/language translations. Instead, it swaps UI labels based on the active connection's query language. Each query language (Gremlin, openCypher, SPARQL) has its own JSON file in src/hooks/translations/ that maps keys to display strings (e.g., "node-type" → "Node Label" in Gremlin vs "Class" in SPARQL).
Key files:
src/hooks/useTranslations.ts — useTranslations() hook returns a t function scoped to the current query enginesrc/hooks/translations/gremlin-translations.jsonsrc/hooks/translations/openCypher-translations.jsonsrc/hooks/translations/sparql-translations.jsonUsage:
const t = useTranslations();
// t("node-type") → "Node Label" (Gremlin) or "Class" (SPARQL)Key naming conventions:
node-type, edge-connections)node-expand.no-selection-title)30587b0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.