docs: update skills with testing and state migration patterns

Author: weeco

frontend/.claude/skills/code-standards/SKILL.md

@@ -40,6 +40,13 @@ Most issues are auto-fixed:
 bun x ultracite fix
 ```
 
+## Console Logging
+
+- **Never** use `console.log`, `console.debug`, or `console.info` in production code
+- Only use `console.error` and `console.warn` for actionable errors
+- For debug logging, wrap in `if (IsDev) { ... }`
+- Don't use `biome-ignore` to suppress console warnings - remove the logs instead
+
 ## Rules
 
 See `rules/` directory for detailed guidance.

frontend/.claude/skills/code-standards/rules/no-legacy.md

@@ -88,6 +88,15 @@ When modifying files with legacy patterns:
 3. **Keep changes minimal** if just fixing bugs
 4. **New features** must use modern patterns
 
+### MobX → React State: Check Side-Effects
+
+When converting observables to React state, automatic behaviors must become explicit:
+- MobX observable arrays auto-update UI when mutated
+- React state requires explicit `setState()` calls
+- Clearing, resetting, or initializing state needs manual handling
+
+**Checklist**: List all observable mutations → add equivalent `setState` calls.
+
 ## Legacy Locations
 
 - MobX stores: `src/state/` (do not add new files)

frontend/.claude/skills/testing/SKILL.md

@@ -40,6 +40,14 @@ bun run test:coverage     # Coverage report
 
 - `.test.ts` = unit (Node.js), `.test.tsx` = integration (JSDOM)
 - Always use `test-utils/test-utils.tsx` for React component tests
+- Test that features are fully wired: UI elements must connect to actual functionality
+
+### Feature Completeness Testing
+
+When implementing interactive features (buttons, forms, etc.):
+- Verify event handlers call the correct functions with proper parameters
+- Test that AbortSignals, callbacks, and other "plumbing" are passed through
+- Don't assume UI presence means functionality works - test the connection
 
 ## When to Use This Skill