Portfolio Case Study

# Portfolio Case Study## UsageUse this DESIGN.md as a reusable design brief for an AI coding agent. Apply it when building a new page, restyling an existing interface, or keeping multiple screens visually consistent.## Design IntentYou are implementing an interface using the **Portfolio Case Study** design language. 把项目背景、过程、结果、视觉资产和个人判断按故事线组织，突出能力证明。Treat information architecture, scan paths, and component grouping as the main design material.## Aliases- 作品集案例- case study layout## Category- 布局与信息组织## Target Platforms- PC 端- 移动端## Summary把项目背景、过程、结果、视觉资产和个人判断按故事线组织，突出能力证明。## Visual DNA- 项目叙事- 过程截图- 结果指标- 章节化## Best Use Cases- 设计作品集- 个人官网- 团队案例- 咨询服务## Avoid When用户只想快速完成任务，或内容没有过程证据。## Anatomy先给结论和成果，再展开问题、方案、取舍和证据；视觉资产服务论证。## Color SystemUse a Seed → Map → Semantic → Alias token architecture. Components must consume named tokens instead of hard-coded colors.### Reference Palette- **reference-1** `#fffaf0`- **reference-2** `#111827`- **reference-3** `#d97706`- **reference-4** `#2563eb`- **reference-5** `#ffffff`### Seed Tokens- **colorBgBase** `#fffaf0` - 页面基础背景.- **colorBgContainer** `#f7f2e9` - 卡片、面板与容器.- **colorFillSecondary** `#ece8e0` - 次级填充与弱状态.- **colorPrimary** `#d97706` - 品牌主操作与选中态.- **colorTextBase** `#111827` - 正文、图标与高对比轮廓.### Primary Scale- **primary-1** `#fbf1e6`- **primary-2** `#f7e1c8`- **primary-3** `#f1cea5`- **primary-4** `#ebb87e`- **primary-5** `#e49d4c`- **primary-6** `#d97706`- **primary-7** `#c16c0a`- **primary-8** `#a9600e`- **primary-9** `#915512`- **primary-10** `#754817`### Neutral Scale- **neutral-1** `#ffffff`- **neutral-2** `#f5f6f6`- **neutral-3** `#ecedee`- **neutral-4** `#d9dadc`- **neutral-5** `#bcbec3`- **neutral-6** `#9b9ea4`- **neutral-7** `#757982`- **neutral-8** `#545963`- **neutral-9** `#323845`- **neutral-10** `#111827`### Semantic Tokens- **colorSuccess** `#16a34a` - 成功、在线、已完成.- **colorSuccessBg** `#e3f4e9` - 成功状态浅背景.- **colorWarning** `#d97706` - 警告、待确认、需关注.- **colorWarningBg** `#faefe1` - 警告状态浅背景.- **colorError** `#d97706` - 错误、危险、阻断.- **colorErrorBg** `#fbf1e6` - 错误状态浅背景.- **colorInfo** `#2563eb` - 信息、链接、进行中.- **colorInfoBg** `#e5ecfd` - 信息状态浅背景.### Alias Tokens- **colorBgLayout** `#faf6ec` - 应用整体画布.- **colorBgElevated** `#f8f4ed` - 弹层、浮层与菜单.- **colorBgSpotlight** `#323845` - Tooltip 与强提示.- **colorBorder** `#d9dadc` - 控件与容器边框.- **colorBorderSecondary** `#ecedee` - 轻分隔线.- **colorText** `#111827` - 一级文本.- **colorTextSecondary** `#5d6067` - 二级文本.- **colorTextTertiary** `#88898c` - 辅助说明.- **colorTextDisabled** `#aeadac` - 禁用文本.- **colorPrimaryHover** `#e49d4c` - 主操作 Hover.- **colorPrimaryActive** `#c16c0a` - 主操作 Active.- **colorPrimaryBorder** `#ebb87e` - 主色边框.- **colorPrimaryBg** `#fbf1e6` - 主色浅背景.- **colorLink** `#d97706` - 链接与可跳转文本.- **colorFocus** `#ebb87e` - 键盘焦点环.- **colorMask** `#0c111c` - Modal 遮罩基础色.Color rules:- Use the palette as design tokens, not random decorative swatches.- Keep primary text and primary actions at accessible contrast.- Use primary-1 through primary-10 for interaction states instead of inventing new brand colors.- Use semantic tokens consistently for success, warning, error, and info; pair color with iconography or text.- Map component styles to Alias Tokens so theme changes do not require component-level color edits.## Typography- Use a restrained system sans or editorial serif/sans pairing only when the product explicitly benefits from publication-like rhythm.- Headlines can be large, but body copy must stay calm: 16-18px on desktop, 15-17px on mobile, line-height around 1.55-1.75.- Use weight changes sparingly; rely on size, spacing, and alignment before adding decoration.## Layout And Spacing- Use generous whitespace: 24-32px section gaps on mobile, 48-96px on desktop depending on content density.- Keep reading widths controlled; avoid full-width paragraphs.- Let spacing create hierarchy before adding borders, shadows, or accent blocks.- Recommended radius: 6-12px radius by default; increase only for expressive or highly tactile components.- Elevation and shadow: Use shadows to separate interactive or elevated surfaces only; avoid stacking many shadow styles.## Component Rules- Components should reinforce the primary information structure rather than introduce a separate decorative style.- Primary actions must be visually obvious and reachable; secondary actions should be quieter but still discoverable.- Cards need a clear title, supporting text or metric, state, and one obvious next action when action is expected.- Forms and filters should use familiar controls, stable dimensions, clear labels, and visible focus states.- Empty, loading, error, and success states must use the same visual language, not generic placeholders.## Interaction And Motion- Use subtle 120-220ms transitions for hover, focus, open, close, and selection states.- Motion should clarify state changes rather than decorate the page.- Respect reduced-motion preferences.## Implementation Recipe1. Start with the real user workflow and page structure; do not make a generic landing page unless explicitly requested.2. Establish layout zones first: navigation, content, controls, feedback, and primary action.3. Apply the color tokens to semantic roles: canvas, surface, text, border, accent, danger, and success.4. Build reusable components that express this style: buttons, cards, inputs, tabs, filters, modals, empty states, and status badges.5. Verify mobile and desktop breakpoints before adding decorative polish.6. Check that the final screen still communicates 项目叙事, 过程截图, 结果指标 without relying on a single color or effect.## Quality Checklist- The screen is immediately recognizable as **Portfolio Case Study**, not a generic Tailwind layout.- The design uses surface, spacing, typography, and component shape together; it does not rely only on colors.- Primary actions and navigation are clear on both mobile and desktop.- Text is readable, controls are stable, and content does not overlap or shift unexpectedly.- Empty, loading, hover, focus, selected, disabled, success, and error states are styled in the same language.- The implementation avoids the known failure mode: 用户只想快速完成任务，或内容没有过程证据。## Anti-Patterns- Do not paste this palette onto an unrelated layout and call it finished.- Do not overuse decorative effects where the user needs to read, compare, or act quickly.- Do not mix this style with unrelated visual languages unless the product explicitly requires a hybrid.- Do not hide important state behind low contrast, blur, tiny text, or animation.## Keywords- portfolio- case study- personal site- editorial## Agent Prompt SnippetImplement the UI in the **Portfolio Case Study** design language. Prioritize 项目叙事, 过程截图, 结果指标. Use the color roles, typography guidance, spacing rules, component rules, and anti-patterns from this DESIGN.md as hard constraints. The result should feel purpose-built for 设计作品集, 个人官网, 团队案例, while avoiding: 用户只想快速完成任务，或内容没有过程证据。