f5792c40be
Pulled ALL skills from 15 source repositories: - anthropics/skills: 16 (docs, design, MCP, testing) - obra/superpowers: 14 (TDD, debugging, agents, planning) - coreyhaines31/marketingskills: 25 (marketing, CRO, SEO, growth) - better-auth/skills: 5 (auth patterns) - vercel-labs/agent-skills: 5 (React, design, Vercel) - antfu/skills: 16 (Vue, Vite, Vitest, pnpm, Turborepo) - Plus 13 individual skills from various repos Mosaic Stack is not limited to coding — the Orchestrator and subagents serve coding, business, design, marketing, writing, logistics, analysis, and more. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
title, impact, impactDescription, tags
| title | impact | impactDescription | tags |
|---|---|---|---|
| Use contentInset for Dynamic ScrollView Spacing | LOW | smoother updates, no layout recalculation | scrollview, layout, contentInset, performance |
Use contentInset for Dynamic ScrollView Spacing
When adding space to the top or bottom of a ScrollView that may change
(keyboard, toolbars, dynamic content), use contentInset instead of padding.
Changing contentInset doesn't trigger layout recalculation—it adjusts the
scroll area without re-rendering content.
Incorrect (padding causes layout recalculation):
function Feed({ bottomOffset }: { bottomOffset: number }) {
return (
<ScrollView contentContainerStyle={{ paddingBottom: bottomOffset }}>
{children}
</ScrollView>
)
}
// Changing bottomOffset triggers full layout recalculation
Correct (contentInset for dynamic spacing):
function Feed({ bottomOffset }: { bottomOffset: number }) {
return (
<ScrollView
contentInset={{ bottom: bottomOffset }}
scrollIndicatorInsets={{ bottom: bottomOffset }}
>
{children}
</ScrollView>
)
}
// Changing bottomOffset only adjusts scroll bounds
Use scrollIndicatorInsets alongside contentInset to keep the scroll
indicator aligned. For static spacing that never changes, padding is fine.