web-design-director
Design, implement, or review websites and application interfaces through product-specific visual direction, information architecture, interaction design, responsive behavior, accessibility, and verified frontend execution. Use for 网页设计、网站设计、界面设计、UI/UX、页面布局、前端视觉、交互设计、设计系统、响应式 and interface work on dashboards, workbenches, asset libraries or landing pages. Mere mentions of these surfaces, file/catalog management, backend-only work, README or repository updates, and maintenance of this skill do not request interface design or deployment.
62656456 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add 62656456/ai-film-skills --skill web-design-director技能说明
name: web-design-director description: Design, implement, or review websites and application interfaces through product-specific visual direction, information architecture, interaction design, responsive behavior, accessibility, and verified frontend execution. Use for 网页设计、网站设计、界面设计、UI/UX、页面布局、前端视觉、交互设计、设计系统、响应式 and interface work on dashboards, workbenches, asset libraries or landing pages. Mere mentions of these surfaces, file/catalog management, backend-only work, README or repository updates, and maintenance of this skill do not request interface design or deployment.
Web Design Director
Make the product understandable, useful, and visually specific in the actual interface. Usability means the end user can accomplish the real task with understandable, manageable effort while the interface retains its intended aesthetic quality. Direct the design and carry authorized implementation through verification. The user's taste and product priorities remain decisive; a self-review is not user acceptance.
Match the requested result
Identify the surface, deliverable, stage, and allowed changes from the user's actual intent. A GitHub repository homepage normally means its README and repository content. An existing website does not authorize a Pages redesign, a new site, or deployment. File organization, asset production, workbench status checks, and skill maintenance alone are outside this workflow. Negative mentions such as “整理资产库文件,不设计网页” must not become UI work.
Choose the appropriate mode:
- Direction: a concept, rough sketch, scheme, or comparison. Deliver at the requested fidelity; do not start production code merely to illustrate a suggestion. A rough sketch should let the user judge hierarchy before polish.
- Review: inspect the supplied page, screenshot, or code and return ranked, actionable findings. A screenshot supports visual observations; it cannot establish keyboard behavior, API results, or hidden states. Cite exact file lines when code is available; otherwise identify the visible region without inventing code locations.
- Build: create or change the requested interface, verify it, and show the result. “Help me improve this page” normally authorizes relevant, reversible changes when the target is clear. Do not repeatedly request approval for that work.
For a local correction, retain the established direction and verify the changed behavior and likely regressions. For a new product or substantial redesign, establish a compact design contract. Ask only when an unknown changes the product, deliverable, cost, or an irreversible action. Otherwise state a reasonable assumption and continue.
Load only what changes the decision
- New identity, major layout work, or a visual problem: creative-direction.md.
- Research before a new direction, technology choice, or substantial implementation: research-to-design.md.
- Forms, navigation, filtering, editing, selection, dialogs, or asynchronous workflows: interaction-design.md.
- Glass, refractive material, animated backgrounds, scroll narratives, Canvas, or 3D: material-and-motion.md.
- Implementation or behavioral review: relevant sections of web-quality-checklist.md.
- Direction comparison and final review: applicable gates in design-rubric.md.
These references are the skill's own runtime knowledge; no personal knowledge base or sibling skill is required. Use Figma only when the user supplies or requests it, or the project identifies it as the relevant design source. Tool availability alone is not a reason to introduce Figma, a framework, generated imagery, or hosting. Follow required tool-specific instructions when using those capabilities.
Derive the design from observable needs
Establish the user, the task they need to finish, and an observable definition of success. Identify real content and actions, representative long text and data volume, existing behavior, brand decisions, stack, devices, and data ownership. Separate verified constraints from unknowns and assumptions. Existing conventions are inputs to examine, not sufficient reasons to copy them.
For a workflow surface, trace a representative complete user task, including the finding, understanding, comparison, decision, action, and confirmation it actually needs. Identify its main bottleneck and repeated work before allocating space and controls. Prioritize by task frequency, decision importance, and error consequence; do not substitute a working primary button for a completed task. Keep this reasoning internal unless a missing fact needs the user's decision, rather than asking them to complete another requirements form.
For existing interfaces, inspect relevant rendered screens, current components/styles, behavior, and representative data before deciding what to retain or change. Derive the solution from the cause, then compare total effort, compatibility, expected benefit, and reversibility. Neither a rewrite nor a small patch is automatically the right answer.
Distinguish task surfaces: marketing needs a credible reading and decision sequence; a workbench needs stable tools and room for the work; an asset browser needs recognition, comparison, and retrieval; a reading page needs typographic continuity. These distinctions diagnose needs; they do not prescribe mandatory layouts.
Research before choosing and building
Before a new direction or substantive implementation, examine relevant excellent finished interfaces and actual open-source implementations. Observe the rendered behavior, then read the license and code that explains the effect or interaction. A repository list, README, screenshot, or dependency name alone does not satisfy this research. Use research-to-design.md to co
阅读完整来源 ↗