「layout」の検索結果

Polished, business-ready design with modern typography, structured layouts, and a trustworthy visual identity.

日本語の概要は準備中です。原文の説明を表示しています。

Vibrant, personality-driven design with bold colors, playful graphics, and dynamic layouts that balance creativity with structure.

日本語の概要は準備中です。原文の説明を表示しています。

Geometric, structured design with clean typography, neutral colors, precise shapes, and intuitive layouts that stay out of the way.

日本語の概要は準備中です。原文の説明を表示しています。

Contemporary editorial style with serif typography, minimal palettes, and clean layouts for polished digital products.

日本語の概要は準備中です。原文の説明を表示しています。

Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism.

日本語の概要は準備中です。原文の説明を表示しています。

Magazine-inspired editorial layout with refined serif typography, structured grids, and elegant reading experiences.

日本語の概要は準備中です。原文の説明を表示しています。

Forward-looking design with tech-inspired typography, modern layouts, and a sleek, innovation-driven aesthetic.

日本語の概要は準備中です。原文の説明を表示しています。

Current-era minimalist design with bento grids, dark mode support, and high-performance accessible layouts.

日本語の概要は準備中です。原文の説明を表示しています。

Strong visual presence with heavyweight typography, high-contrast colors, and commanding layouts.

日本語の概要は準備中です。原文の説明を表示しています。

Cozy cafe-inspired interface with warm tones, soft typography, and clean layouts for a relaxed browsing experience.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need to reproduce or debug TUI rendering issues (garbled output, broken streaming, layout corruption) by running ralph in a tmux split pane and capturing live output.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "analyze the SERP" or "SERP分析"; maps SERP features, layout, ranking factors, search intent, AI Overviews, and snippet opportunities for a query. Not for keyword demand discovery — use keyword-research. SERP分析/搜索结果

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "plan my paid account structure", "pick Search vs PMax", "lay out ad groups / asset groups", or "audit paid-vs-organic cannibalization"; designs campaign-type selection, ad-group/asset-group layout, targeting + match types, negative/exclusion hygiene, and a paid↔organic overlap audit, and scores the ROAS A (Audience) dimension + structure. Not for computing the final RQS — use ad-account-auditor; not for budget split — use budget-optimizer; not for organic site architecture — use site-structure-optimizer. 付费广告账户结构/广告系列规划/否定关键词

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "build the email HTML", "make this email responsive", "fix dark-mode rendering", or "QA the email across clients"; produces the coded HTML build — a responsive table layout, dark-mode + accessibility pass, a client-render matrix, image-block fallbacks, and a plain-text parity check. Not for writing the copy — use email-creative-builder; not for scoring the email or computing EQS — use email-quality-auditor. 邮件HTML/响应式邮件/暗色模式渲染

日本語の概要は準備中です。原文の説明を表示しています。

Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".

日本語の概要は準備中です。原文の説明を表示しています。

Critique a rendered screen's composition — balance, whitespace, rhythm, and gestalt grouping. Use when a layout feels off but hierarchy is fine. For emphasis and eye flow specifically, use `critique-visual-hierarchy`.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use `law-of-proximity`.

日本語の概要は準備中です。原文の説明を表示しています。

Create a spacing scale from a base unit with rules for when each step applies. Use when standardising padding and margins. For page-level columns and gutters, use `layout-grid`.

日本語の概要は準備中です。原文の説明を表示しています。

Define a responsive grid — columns, gutters, margins, and breakpoint behaviour. Use when establishing page structure. For the spacing scale inside components use `spacing-system`; for cross-device behaviour use `responsive-design`.

日本語の概要は準備中です。原文の説明を表示しています。

Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when creating or organizing theme files and design tokens (theme.ts / theme/), extending an existing theme or styling library (NativeWind, Tamagui, Restyle, Unistyles) in its own idiom, standardizing styles so screens (including AI-generated ones) look consistent and polished, fixing an app that looks AI-generated or generic instead of native (the named native-slop tells), building an in-app component library, or auditing an app for design-system drift (hardcoded colors, spacing, fonts). For platform styling specifics (semantic colors, HIG rules, native controls) use expo-native-ui; for folder layout of a new app use expo-project-structure.

日本語の概要は準備中です。原文の説明を表示しています。

Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, visual effects, gradients, storage, and responsive layout. For routing and navigation, use the expo-router skill; for motion and animation, use the expo-animation skill.

日本語の概要は準備中です。原文の説明を表示しています。

Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.

日本語の概要は準備中です。原文の説明を表示しています。

Skillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/). Use this skill whenever you: build or modify a dashboard page or component in ui/src/, style or layout website pages or custom CSS in website/, create new React components for the dashboard, add pages to the dashboard, fix visual bugs in either frontend, or need to know which design tokens, ss-* classes, components, or patterns to use. Covers the two dashboard styles (Clean / Playful) in light and dark, design tokens, the ss-* class system, component API, page structure, accessibility, keyboard shortcuts, and anti-patterns. Even if the user just says "fix the styling" or "add a card", use this skill to ensure consistency.

日本語の概要は準備中です。原文の説明を表示しています。

Ensure ATS-friendly formatting and create clean scannable layouts

日本語の概要は準備中です。原文の説明を表示しています。