c24165b8bc
에이전트 8종(대화형/프로그래머 C·S/디자이너/설계자/기획자/QA/PD/PM)에게 [공통 기본 능력 + 롤별 Specialty] 2층으로 지식을 주입하기 위한 재분류. 문서 내용·포맷은 무수정, 폴더 이동만 (6,372개 문서 수 보존 확인). - Topic_Programming → Domain_Programming (내부 구조 보존) - Topic_Graphic → Domain_Design - Topic_Business → Domain_Product - Topic_General → Domain_General - _Common 신설: Math(구 Topic_Math_Specialty), Reasoning(구 General/From_Thinking & Reasoning), Reasoning_Creativity(구 General/From_창의성), Communication(Poetic_Blog_Writing + From_writing) - 타 도메인의 From_* 폴더는 유지 (출처 표기일 뿐, 이미 도메인에 맞게 분류된 문서) - 빈 폴더 정리 (memory/procedures) - 에이전트→폴더 매핑은 workspace의 .astra/agent-knowledge-map.json (9개 에이전트) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
5.3 KiB
5.3 KiB
id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
| id | title | category | status | canonical_id | aliases | duplicate_of | source_trust_level | confidence_score | verification_status | tags | raw_sources | last_reinforced | github_commit | tech_stack | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| wiki-2026-0508-모바일-퍼스트-mobile-first | 모바일 퍼스트(Mobile-First) | 10_Wiki/Topics | verified | self |
|
none | A | 0.9 | applied |
|
2026-05-10 | pending |
|
모바일 퍼스트(Mobile-First)
매 한 줄
"매 작은 화면부터 design — 큰 화면 의 progressive enhancement". Luke Wroblewski (2009)가 제창, smallest viewport 기준 baseline CSS, larger breakpoint 의
min-widthmedia query 의 progressive enhancement. 매 2026 의 mobile traffic 60%+ 환경의 default approach.
매 핵심
매 vs Desktop-first
| Mobile-first | Desktop-first | |
|---|---|---|
| Baseline | smallest viewport | largest viewport |
| Media query | min-width (up) |
max-width (down) |
| Mindset | progressive enhancement | graceful degradation |
| Default 2026 | ✓ | (legacy) |
매 3원칙 (Wroblewski)
- Constraints force focus — small screen 매 essential content prioritize.
- Capabilities expand — touch, GPS, camera 의 leverage.
- Progressive enhancement — base 의 small + add 의 large.
매 응용
- Performance budget — mobile network slow → minimal payload first.
- Touch-first UX — 44×44px tap target (Apple HIG), 48×48dp (Material).
- Content hierarchy — most important top, fold concept abandoned.
💻 패턴
1. CSS mobile-first media query
/* base — mobile (< 640px implicit) */
.container {
padding: 1rem;
font-size: 14px;
}
.grid {
display: grid;
grid-template-columns: 1fr;
gap: 1rem;
}
/* tablet ≥ 640px */
@media (min-width: 640px) {
.container { padding: 2rem; font-size: 16px; }
.grid { grid-template-columns: repeat(2, 1fr); }
}
/* desktop ≥ 1024px */
@media (min-width: 1024px) {
.grid { grid-template-columns: repeat(3, 1fr); gap: 2rem; }
}
2. Tailwind mobile-first utilities
// base 의 mobile, sm:/md:/lg: 의 enhancement
export function Card() {
return (
<div className="p-4 sm:p-6 lg:p-8">
<h2 className="text-xl sm:text-2xl lg:text-3xl">Title</h2>
<div className="grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-3 gap-4">
<Item />
<Item />
<Item />
</div>
</div>
);
}
3. Container queries (modern 2026)
.card-container {
container-type: inline-size;
container-name: card;
}
.card { display: flex; flex-direction: column; }
@container card (min-width: 400px) {
.card { flex-direction: row; }
}
4. Responsive image (srcset)
<img
src="hero-mobile.webp"
srcset="hero-mobile.webp 480w, hero-tablet.webp 1024w, hero-desktop.webp 1920w"
sizes="(min-width: 1024px) 1920px, (min-width: 640px) 1024px, 100vw"
alt="Hero"
loading="lazy"
/>
5. Viewport meta + safe area
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
.app {
padding-top: env(safe-area-inset-top);
padding-bottom: env(safe-area-inset-bottom);
}
6. Touch-friendly tap targets
button, a {
min-width: 44px;
min-height: 44px;
padding: 0.75rem 1rem;
/* Apple HIG: 44×44pt minimum */
}
7. Performance: critical CSS inline
<head>
<style>/* critical above-fold CSS, < 14KB */</style>
<link rel="preload" href="main.css" as="style" onload="this.rel='stylesheet'">
</head>
매 결정 기준
| 상황 | Approach |
|---|---|
| New project 2026 | mobile-first default. |
| Legacy desktop site | gradual migration via container queries. |
| Internal tool (desktop only) | desktop-first 도 OK 매 — but mobile-first 매 future-proof. |
| Component library | container queries > viewport media queries (component reusability). |
기본값: Tailwind mobile-first utilities + container queries 매 component-level.
🔗 Graph
- 변형: 컨테이너 쿼리 (Container Queries)
- 응용: CSS_Architecture_and_Styling
- Adjacent: Core Web Vitals Optimization (INP, LCP, CLS)
🤖 LLM 활용
언제: 새 web project, e-commerce, content site, public-facing app, PWA. 언제 X: desktop-only enterprise tool 의 absolute desktop-first 가 효율적인 case (rare).
❌ 안티패턴
max-width만 의 의존: 매 reverse mobile-first defeats purpose.- 고정 px 의 layout: rem/em/% 의 use.
- Hover-only interactions: touch 의 hover 없음 — tap fallback 필수.
- Fold obsession: 매 mobile 의 scrolling natural — fold 없음.
- Tap target < 44px: thumb miss-tap.
🧪 검증 / 중복
- Verified (Wroblewski "Mobile First" 2011, Google Web.dev 2026, MDN responsive design).
- 신뢰도 A.
- Canonical 매 모바일 퍼스트(Mobile-First) — 매 모바일 우선주의 (Mobile-First) 디자인, 모바일 퍼스트 및 다양한 디바이스 환경을 위한 반응형 레이아웃 구축 redirect 매 here.
🕓 Changelog
| 날짜 | 변경 |
|---|---|
| 2026-05-08 | Phase 1 |
| 2026-05-10 | Manual cleanup — canonical full content + 7 patterns (CSS, Tailwind, container queries) |