hwc-stimulus-fundamentals

Stimulus Fundamentals Implement robust Stimulus controllers with clear lifecycle and state boundaries. Core Workflow Define controller contract first: targets, values, outlets, actions, and expected lifecycle. Keep state transitions in value callbacks when reactive updates are required. Guard callbacks that can run before connect() completes. Use connect()/disconnect() for setup and teardown symmetry. Isolate DOM event handling from business rules; keep controllers composable. Guardrails Prefer declarative action parameters over manual dataset parsing. Use outlets for controller-to-controller communication instead of private internals. Keep target callbacks idempotent; account for repeated connect/disconnect cycles. Use MutationObserver only when DOM-driven reactivity is required. Feature-detect browser APIs before exposing UI affordances. Load References Selectively Open only the file needed for the current request. Value changed callbacks: references/2023-08-29-stimulus-value-changed-callbacks.md Keyboard action filters and hotkeys: references/2023-10-24-stimulus-keyboardevent-101.md MutationObserver-based sorting: references/2023-12-05-stimulus-auto-sorting.md Outlets API communication: references/2023-12-19-stimulus-outlets-api.md Target callback orchestration: references/2024-05-07-stimulus-target-callbacks.md Web Share API integration: references/2025-11-25-stimulus-web-share-api.md Core Web Vitals and lazy-loading fundamentals: references/2024-06-18-fundamentals-core-web-vitals.md Use references/INDEX.md for the full catalog. Escalate to Neighbor Skills Form-centric behavior: use hwc-forms-validation Navigation/history/cache with Turbo: use hwc-navigation-content Turbo Stream/WebSocket orchestration: use hwc-realtime-streaming Media integrations and playback concerns: use hwc-media-content UX feedback/transitions/progress concerns: use hwc-ux-feedback