메뉴
React rendering optimization patterns — memoization, derived state, static hoisting, conditional rendering, caching. Use when reviewing or optimizing React component render performance.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/ihj04982/my-cursor-settings --skill react-rendering-optimization명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
Automate browser interactions, test web pages and work with Playwright tests.
Advanced guidelines and best practices for writing tests using Vitest. Apply this skill when generating, reviewing, or refactoring test codes to prevent common pitfalls and ensure high performance.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | react-rendering-optimization |
| description | React rendering optimization patterns — memoization, derived state, static hoisting, conditional rendering, caching. Use when reviewing or optimizing React component render performance. |
Patterns to reduce unnecessary computation and re-creation during React renders.
When an expression is simple and returns a primitive (boolean, number, string), useMemo overhead exceeds the expression cost.
Bad:
const isLoading = useMemo(() => {
return user.isLoading || notifications.isLoading;
}, [user.isLoading, notifications.isLoading]);
Good:
const isLoading = user.isLoading || notifications.isLoading;
Default non-primitive values in memoized components create new instances every render, breaking memo().
Bad:
const UserAvatar = memo(function UserAvatar({ onClick = () => {} }: { onClick?: () => }) {
})
Good:
const NOOP = () => {};
const UserAvatar = memo(function UserAvatar({ onClick = NOOP }: { onClick?: () => void }) {
// ...
})
Extract static JSX outside components to avoid re-creation on every render. Especially helpful for large static SVG nodes.
Bad:
function Container() {
return <div>{loading && <div className="animate-pulse h-20 bg-gray-200" />}</div>;
}
Good:
const loadingSkeleton = <div className="animate-pulse h-20 bg-gray-200" />;
function Container() {
return <div>{loading && loadingSkeleton}</div>;
}
If React Compiler is enabled, it handles this automatically.
Don't create RegExp inside render. Hoist to module scope or memoize.
Bad:
function Highlighter({ text, query }: Props) {
const regex = new RegExp(`(${query})`, 'gi')
const parts = text.split(regex)
return <>{parts.map((part, i) => ...)}</>
}
Good:
const EMAIL_REGEX = /^[^\s@]+@[^\s@]+\.[^\s@]+$/
function Highlighter({ text, query }: Props) {
const regex = useMemo(
() => new RegExp(`(${escapeRegex(query)})`, 'gi'),
[query]
)
const parts = text.split(regex)
return <>{parts.map((part, i) => ...)}</>
}
Warning: Global regex (
/g) has mutablelastIndexstate —regex.test('foo')returnstruethenfalsealternately.
If a value can be computed from current props/state, derive it during render instead of storing in state + syncing with useEffect.
Bad:
const [fullName, setFullName] = useState('');
useEffect(() => {
setFullName(firstName + ' ' + lastName);
}, [firstName, lastName]);
Good:
const fullName = firstName + ' ' + lastName;
Reference: You Might Not Need an Effect
Use a module-level Map to memoize pure functions called repeatedly with the same inputs.
Bad:
{projects.map(project => {
const slug = slugify(project.name) // called 100+ times for same names
return <ProjectCard key={project.id} slug={slug} />
})}
Good:
const slugifyCache = new Map<string, string>()
function cachedSlugify(text: string): string {
if (slugifyCache.has(text)) return slugifyCache.get(text)!
const result = slugify(text)
slugifyCache.set(text, result)
return result
}
Use a Map (not a hook) so it works everywhere: utilities, event handlers, not just components.
Use explicit ternary instead of && when the condition can be 0, NaN, or other falsy values that render visibly.
Bad (renders "0" when count is 0):
<div>{count && <span className="badge">{count}</span>}</div>
Good:
<div>{count > 0 ? <span className="badge">{count}</span> : null}</div>
useMemo wrapping simple primitive expressions