aa489c7eb8
Add detailed landing page development plan in docs/frontend_landing_plan.md: - Complete landing page structure (Hero, Problem/Solution, Features, Demo, CTA) - Design guidelines from downloaded skills (typography, color, motion, composition) - Security considerations (XSS prevention, input sanitization, CSP) - Performance targets (LCP <2.5s, bundle <150KB, Lighthouse >90) - Responsiveness and accessibility requirements (WCAG 2.1 AA) - Success KPIs and monitoring setup - 3-week development timeline with daily tasks - Definition of Done checklist Download 10+ frontend/UI/UX skills via universal-skills-manager: - frontend-ui-ux: UI/UX design without mockups - frontend-design-guidelines: Production-grade interface guidelines - frontend-developer: React best practices (40+ rules) - frontend-engineer: Next.js 14 App Router patterns - ui-ux-master: Comprehensive design systems and accessibility - ui-ux-systems-designer: Information architecture and interaction - ui-ux-design-user-experience: Platform-specific guidelines - Plus additional reference materials and validation scripts Configure universal-skills MCP with SkillsMP API key for curated skill access. Safety first: All skills validated before installation, no project code modified. Refs: Universal Skills Manager (github:jacob-bd/universal-skills-manager) Next: Begin Sprint 3 landing page development
59 lines
2.0 KiB
Markdown
59 lines
2.0 KiB
Markdown
---
|
|
title: Use Lazy State Initialization
|
|
impact: MEDIUM
|
|
impactDescription: wasted computation on every render
|
|
tags: react, hooks, useState, performance, initialization
|
|
---
|
|
|
|
## Use Lazy State Initialization
|
|
|
|
Pass a function to `useState` for expensive initial values. Without the function form, the initializer runs on every render even though the value is only used once.
|
|
|
|
**Incorrect (runs on every render):**
|
|
|
|
```tsx
|
|
function FilteredList({ items }: { items: Item[] }) {
|
|
// buildSearchIndex() runs on EVERY render, even after initialization
|
|
const [searchIndex, setSearchIndex] = useState(buildSearchIndex(items))
|
|
const [query, setQuery] = useState('')
|
|
|
|
// When query changes, buildSearchIndex runs again unnecessarily
|
|
return <SearchResults index={searchIndex} query={query} />
|
|
}
|
|
|
|
function UserProfile() {
|
|
// JSON.parse runs on every render
|
|
const [settings, setSettings] = useState(
|
|
JSON.parse(localStorage.getItem('settings') || '{}')
|
|
)
|
|
|
|
return <SettingsForm settings={settings} onChange={setSettings} />
|
|
}
|
|
```
|
|
|
|
**Correct (runs only once):**
|
|
|
|
```tsx
|
|
function FilteredList({ items }: { items: Item[] }) {
|
|
// buildSearchIndex() runs ONLY on initial render
|
|
const [searchIndex, setSearchIndex] = useState(() => buildSearchIndex(items))
|
|
const [query, setQuery] = useState('')
|
|
|
|
return <SearchResults index={searchIndex} query={query} />
|
|
}
|
|
|
|
function UserProfile() {
|
|
// JSON.parse runs only on initial render
|
|
const [settings, setSettings] = useState(() => {
|
|
const stored = localStorage.getItem('settings')
|
|
return stored ? JSON.parse(stored) : {}
|
|
})
|
|
|
|
return <SettingsForm settings={settings} onChange={setSettings} />
|
|
}
|
|
```
|
|
|
|
Use lazy initialization when computing initial values from localStorage/sessionStorage, building data structures (indexes, maps), reading from the DOM, or performing heavy transformations.
|
|
|
|
For simple primitives (`useState(0)`), direct references (`useState(props.value)`), or cheap literals (`useState({})`), the function form is unnecessary.
|