japanese-webdesign
npx skills add https://github.com/ronantakizawa/japanese-webdesign --skill japanese-webdesign
Agent 安装分布
Skill 文档
Japanese Web Design Skill
Overview
Japanese web design follows fundamentally different principles than Western design. What appears “cluttered” to Western eyes is optimized for Japanese cultural values, trust-building, and user expectations.
Market Context:
- Rakuten Ichiba: ¥6+ trillion GMV, 494.8 million monthly visitors
- Yahoo Japan Shopping: 118.2 million monthly visitors
- 60%+ of Japanese web traffic is mobile
- Credit-card-only checkout loses up to 30% of buyers
Reference Files
- reference/component-patterns.md – HTML/CSS component examples (product cards, banners, tables, footers, mobile navigation)
- reference/cultural-context.md – Deep cultural factors (Anshin, demographics, seasons, Keigo levels, numbers to avoid)
Core Principles
å®å¿ (Anshin) – Reassurance Through Information
The most important concept: providing reassurance by eliminating surprises.
- All information visible upfront – hiding creates suspicion
- Complete specifications before purchase decisions
- Multiple confirmation points to prevent mistakes
“If you’re not showing me everything, what are you hiding?” â Common Japanese consumer mindset
ä¸ç®çç¶ (Ichimoku Ryouzen) – Understanding at a Glance
Everything needed should be visible without requiring clicks or navigation.
The Ponchi-e Culture
In Japanese business, Ponchi-e slides pack all relevant details into a single page. This approach directly influences web UI/UX expectationsâno white space goes to waste.
Design Patterns
1. Information Density
| Western Approach | Japanese Approach |
|---|---|
| “Less is more” | “More is trust” |
| Progressive disclosure | Everything visible |
| Clean whitespace | Productive use of space |
| Single call-to-action | Multiple detailed options |
| “Learn more” buttons | Information already present |
Why it works: Kanji characters carry meaning without being sounded out, enabling faster scanning of dense layouts.
Product cards should include: ranking badges, review count, shipping info, full specs, original/sale price, discount %, points, delivery estimates.
2. Bento Box Layouts (å¼å½ç®±ã¬ã¤ã¢ã¦ã)
Modern Japanese design uses modular content blocks inspired by bento boxes:
.bento-grid {
display: grid;
grid-template-columns: repeat(12, 1fr);
gap: 16px;
grid-auto-flow: dense;
}
.bento-item { background: #fff; border: 1px solid #e0e0e0; border-radius: 8px; padding: 16px; }
Best Practice: Limit to 9 or fewer boxes for clarity while maintaining density.
3. Visual Hierarchy (No Uppercase)
Japanese has no uppercase/lowercase. Create hierarchy through:
- Size variation (larger = more important)
- Color backgrounds (colored boxes for sections)
- Borders and frames (æç¢ºãªåºåã)
- Icons and badges
- Bold text (avoid italicsârenders poorly)
4. Trust Signals (ä¿¡é ¼æ§)
Required trust indicators:
- Customer service photo – Staff with headset showing human support available
- ISO/Privacy Mark certifications
- Years in business (嵿¥ââå¹´)
- Customer satisfaction % (ãå®¢æ§æºè¶³åº¦)
- Full company info: address, phone, fax, representative name
- Review count with actual text content
- Shipping badges – ã彿¥åºè·ã(same-day shipping), ãéæç¡æãprominently displayed
5. Form Design: Show Everything First
Japanese users want to see the entire process before starting.
Wrong: Step-by-step wizard hiding fields Right: All fields visible with progress indicator (å ¥åé ç®: 12é ç®ä¸ 0é ç®å ¥åæ¸ã¿)
6. Confirmation Culture (確èª)
Add multiple confirmation points:
- Order summary (注æå 容確èª)
- Explicit confirmation dialog
- Final verification screen (æçµç¢ºèª)
- Completion with detailed next steps
7. Color Usage
Common patterns:
- Bright, saturated colors (red, yellow, orange for attention)
- Section color-coding for organization
- Seasonal colors (æ¡ãã³ã¯ in spring, ç´ è in autumn)
- Blue themes for comparison/information sites (Kakaku.com style)
- Orange/red for e-commerce CTAs and sale badges
:root {
--sale-red: #e60012;
--attention-yellow: #ffeb3b;
--trust-blue: #0066cc;
--kakaku-blue: #002d7a;
--sakura-pink: #fcc;
--category-purple: #6b5b95;
}
Site type color conventions:
- E-commerce: Red/orange accents (Rakuten style)
- Price comparison: Blue headers (Kakaku.com style)
- Portals: Multi-color sections (Yahoo Japan style)
8. Navigation
Show all optionsâavoid hamburger menus:
- Mega navigation with categories + item counts
- Inline popular items and current promotions
- Tab bars for mobile (not hamburger)
9. Category Grids (Kakaku.com Style)
Display categories as icon grids with subcategories inline:
- Icon + category name in colored box
- Subcategories listed below each main category
- Item counts per category (ãã½ã³ã³ 15,234ä»¶)
- Blue/purple color coding for different sections
10. Trending Keywords (人æ°ãã¼ã¯ã¼ã)
Show popular search terms as clickable tag buttons:
- Colored background tags (red for 注ç®, blue for trending)
- Displayed prominently near search bar
- Updated frequently to show freshness
11. Portal Layouts (Yahoo Japan Style)
Multi-column layouts for portal/news sites:
- 3+ columns on desktop
- Service sidebar with icons for each service
- News section with thumbnail + headline
- Topic tabs (çµæ¸, ã¨ã³ã¿ã¡, ã¹ãã¼ã, etc.)
- Weather widget with location
- “NEW” badges (æ°ç) on fresh content
- Login/account section in sidebar
Typography
Font Terminology
- Serif = ææ (Mincho)
- Sans-Serif = ã´ã·ã㯠(Gothic)
Font Stack
Japanese fonts require 7,000-16,000 glyphs (vs. ~230 for English).
body {
font-family: "Hiragino Kaku Gothic ProN", "Hiragino Sans", "Yu Gothic Medium", "Meiryo", "Noto Sans JP", sans-serif;
}
.formal-text {
font-family: "Hiragino Mincho ProN", "Yu Mincho", "Noto Serif JP", serif;
}
Typography Rules
| Guideline | Recommendation |
|---|---|
| Font size | 10-15% smaller than Latin equivalent |
| Line height | 185-200% of font size |
| Line length | ~35 characters optimal |
| Italics | Avoid – renders poorly |
| Bold | Use sparingly, prefer color/size |
E-Commerce Patterns
Product Grid Layout
Dense thumbnail grids are standard:
- Small thumbnails (80-120px) in tight grid
- Price overlay on each thumbnail
- Discount badges (50%OFF, ã»ã¼ã«) as corner ribbons
- Category icons above product sections
- Promotional banners interspersed in grid
Product Pages (ååãã¼ã¸)
Must include:
- Ranking indicators with date/category
- 10-20 product images (not 3-5)
- Exhaustive specifications table
- Shipping details (carrier, timing, costs)
- Full return policy text (not just link)
- Same-day shipping badge if applicable (彿¥åºè·)
Price Display
Always show:
- Original price with label (ã¡ã¼ã«ã¼å¸æå°å£²ä¾¡æ ¼)
- Sale price highlighted
- Discount amount AND percentage
- Tax status (ç¨è¾¼/ç¨æ)
- Points earned
Payment Methods
Include all common options:
- Credit cards (VISA, Master, JCB, AMEX)
- ã³ã³ããæ±ºæ¸ (convenience store)
- PayPay, LINE Pay, 楽天ãã¤
- éè¡æ¯è¾¼ (bank transfer)
- 代é弿 (cash on delivery)
SaaS & B2B Requirements
Key Differences
- Extended trial periods expected
- Detailed documentation required before sales calls
- Formal language (æ¬èª) required
B2B-Specific CTAs
Primary flow: è³æãã¦ã³ãã¼ã (document download) â ç¡æãã©ã¤ã¢ã« â ãåãåãã
Required Content
- Comprehensive feature documentation with screenshots
- Pricing with all tiers, features, and limits visible
- Security certifications (ISO 27001, SOC 2, ISMS)
- Support options with hours (æ¥æ¬èªé»è©±ãµãã¼ã: å¹³æ¥9:00-18:00)
- Extensive FAQ section
Language Formality (æ¬èª)
| Context | Casual (B2C) | Formal (B2B) |
|---|---|---|
| Submit | éä¿¡ãã | éä¿¡ãããã¾ã |
| Error | ã¨ã©ã¼ãçºçãã¾ãã | ã¨ã©ã¼ãçºçãããã¾ããããææ°ã§ãããå度ã試ããã ããã |
Mobile Design
Principles
- Tab bars preferred over hamburger menus
- Information density maintained on mobile
- 2-3 column grids (not single column)
- Smaller font (12px) acceptable
@media (max-width: 768px) {
.product-grid { grid-template-columns: repeat(2, 1fr); gap: 8px; }
.mobile-tab-nav { position: fixed; bottom: 0; display: flex; justify-content: space-around; }
}
Cultural Considerations
Mascot Characters (ãããã£ã©)
Use mascots to:
- Make institutions approachable
- Reduce anxiety about complex processes
- Guide onboarding, errors, and help sections
Seasonal Content (å£ç¯æ)
Update designs for seasons:
- æ¥: Cherry blossoms, graduation
- å¤: Cool blues, festival themes
- ç§: Maple leaves (ç´ è)
- å¬: New Year, Valentine’s
Error Messages
Japanese errors should be apologetic:
// Western: "Invalid email address"
// Japanese: "ã¡ã¼ã«ã¢ãã¬ã¹ã®å½¢å¼ãæ£ããããã¾ããããææ°ã§ãããå度ã確èªãã ããã"
Localization Mistakes to Avoid
- Translation â Localization – translated English loses nuance
- Machine translation – Japanese is too complex
- Informal language – sounds strange to customers
- Wrong Keigo level – damages brand perception
- Credit-card only – loses 30% of buyers
- No Japanese support – deters repeat customers
- Cultural insensitivity – improper imagery causes backlash
Anti-Patterns
Don’t Do This:
- Hide information behind “Learn More”
- Use hamburger menus as primary navigation
- Minimize form fields
- Skip confirmation steps
- Use vague CTAs (“Get Started” â ãè³æãã¦ã³ãã¼ãã)
- Remove trust signals for aesthetics
- Assume minimal = professional
- Use italics for Japanese text
- Rely on machine translation
Cultural Missteps:
- Number 4 (å sounds like æ» = death)
- Number 9 (ä¹ sounds like è¦ = suffering)
- Red ink for names (funeral association)
- Casual language in business contexts
2025 Trends
- Neo-retro design – Y2K meets Showa nostalgia
- Immersive 3D – tailored for precision
- AI personalization – with human touch
- Microinteractions – hover effects, scroll feedback
- Bento layouts – modular, mobile-friendly
- Collapsible sections – managing density
Key insight: Change is gradual. Japanese users adjust slowlyâproven patterns are safer than innovation.
A/B Testing Reality
| Test | Result |
|---|---|
| Rakuten: Clean vs. cluttered | Cluttered converts better |
| Yahoo Japan: Modernized design | Users complained, reverted |
| Amazon Japan: Added MORE info | Sales increased |
Reference Sites
- Rakuten (rakuten.co.jp) – E-commerce benchmark
- Yahoo Japan (yahoo.co.jp) – Portal density
- Kakaku.com – Price comparison
- PayPay – Mobile payment design
- Mercari – Mobile marketplace
- LINE – Super app patterns
Quick Checklist
- All critical information visible without clicking
- Detailed specifications provided
- Trust signals prominent (company info, certifications)
- Multiple confirmation steps
- Full contact information (including fax)
- Reviews with actual text
- Price breakdown with tax (æ¶è²»ç¨10%)
- Multiple payment methods
- Shipping/return policies visible
- Navigation shows all categories
- Mobile maintains density with tab navigation
- Appropriate keigo level
- Seasonal elements if applicable
- Comprehensive FAQ
- Japanese-language support
- Professional localization (no machine translation)
- Typography: no italics, 185-200% line-height
- Numbers 4 and 9 not prominent