/SKILL.md
Provides guidance for designing websites optimized for Japanese audiences, including cultural UX principles, information density patterns, bento layouts, trust signals, and localization best practices. Use when building e-commerce sites, landing pages, SaaS products, or any web application targeting Japanese users.
npx skillsauth add ronantakizawa/japanese-webdesign japanese-webdesignInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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:
The most important concept: providing reassurance by eliminating surprises.
"If you're not showing me everything, what are you hiding?" — Common Japanese consumer mindset
Everything needed should be visible without requiring clicks or navigation.
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.
| 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.
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.
Japanese has no uppercase/lowercase. Create hierarchy through:
Required trust indicators:
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項目入力済み)
Add multiple confirmation points:
Common patterns:
:root {
--sale-red: #e60012;
--attention-yellow: #ffeb3b;
--trust-blue: #0066cc;
--kakaku-blue: #002d7a;
--sakura-pink: #fcc;
--category-purple: #6b5b95;
}
Site type color conventions:
Show all options—avoid hamburger menus:
Display categories as icon grids with subcategories inline:
Show popular search terms as clickable tag buttons:
Multi-column layouts for portal/news sites:
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;
}
| 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 |
Dense thumbnail grids are standard:
Must include:
Always show:
Include all common options:
Primary flow: 資料ダウンロード (document download) → 無料トライアル → お問い合わせ
| Context | Casual (B2C) | Formal (B2B) | |---------|--------------|--------------| | Submit | 送信する | 送信いたします | | Error | エラーが発生しました | エラーが発生いたしました。お手数ですが、再度お試しください。 |
@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; }
}
Use mascots to:
Update designs for seasons:
Japanese errors should be apologetic:
// Western: "Invalid email address"
// Japanese: "メールアドレスの形式が正しくありません。お手数ですが、再度ご確認ください。"
Key insight: Change is gradual. Japanese users adjust slowly—proven patterns are safer than innovation.
| Test | Result | |------|--------| | Rakuten: Clean vs. cluttered | Cluttered converts better | | Yahoo Japan: Modernized design | Users complained, reverted | | Amazon Japan: Added MORE info | Sales increased |
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.