响应式布局网格与断点设计
根据产品内容规划断点、栅格和容器宽度,交付响应规则、设计令牌及样式代码。
完整提示词
<context>
Breakpoints chosen from a list of popular devices age within a year; breakpoints chosen where the content breaks, checked against real viewport analytics, last. Fewer is better: three to five ranges cover most products. Mobile-first `min-width` queries keep the base styles simple. Since container queries are widely supported in current browsers, components should respond to the space they are given rather than the viewport, which leaves page-level breakpoints for page layout only. Gutters and margins belong on the spacing scale. Reading content needs a maximum line length (roughly 60 to 80 characters), so wide screens need max widths, not wider text. Accessibility sets a hard floor: WCAG 1.4.10 Reflow expects content to work at 320 CSS pixels wide, which is what a 1280 pixel window at 400 percent zoom gives you. Native platforms have their own size systems (iOS size classes, Android window size classes) and should map to them rather than copy web breakpoints.
</context>
<task>
Define the layout grid and breakpoints for this product.
<product>
{{product}}
</product>
{{#platforms}}Platforms: {{platforms}}.
{{/platforms}}{{#current}}
<current>
{{current}}
</current>
{{/current}}
1. **Breakpoints.** Propose named ranges (for example `sm`, `md`, `lg`, `xl`) with min widths, and justify each by the content it serves. If analytics are given, show how the ranges fit them; if not, say what to measure.
2. **Grid per breakpoint.** A table of columns, gutter, outer margin and whether margins are fixed or fluid, per range.
3. **Containers and max widths.** Max widths for reading pages, forms, dashboards and full-bleed sections; how content centres; maximum line length for text.
4. **Spacing relationship.** Tie gutters and margins to the spacing scale; if no scale is given, propose one and mark it proposed.
5. **Responsive behaviour.** Rules for common patterns: navigation, sidebars, card grids, data tables, forms, dialogs. Say which should use container queries and which page breakpoints. Confirm every pattern works at 320 CSS pixels wide.
6. **Tokens and code.** Token names for breakpoints, columns, gutters and max widths; a CSS excerpt with custom properties and media and container queries, noting that custom properties cannot be used inside media query conditions, so breakpoints need a preprocessor, build step or duplicated values.
7. **Native platforms.** If iOS or Android are in scope, map the grid to iOS size classes and Android window size classes instead of pixel breakpoints, and report the mapping under Breakpoints.
8. **Design files.** Grid styles to create in the design tool for each breakpoint, and frame widths designers should use for handoff.
</task>
<constraints>
- Do not define breakpoints per device model.
- Do not invent analytics figures or existing values; mark proposals.
- Keep the number of breakpoints as low as the content allows and say why each exists.
{{> output/uncertainty}}
</constraints>
<output_format>
Markdown with the sections from the contract, in order. Breakpoints and grid as tables, code in fenced blocks. End with Open questions.
</output_format>可替换内容
- {{product}}
- {{#platforms}}
- {{platforms}}
- {{/platforms}}
- {{#current}}
- {{current}}
- {{/current}}
- {{> output/uncertainty}}
分类与标签
设计创意、响应式设计、布局栅格、设计系统、设计交付