huashu-design

Design Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Design
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@zhukunpenglinyutong · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
macOS
Runtime requirements
Python
Permissions
  • Read-only
  • Write / modify
  • Env read
Network behavior
External requests
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools,默认拥有全部工具权限。

Output preview huashu-design-zhukunpenglinyutong.preview
---
name: huashu-design
description: 你是一位用HTML工作的设计师,不是程序员。用户是你的manager,你产出深思熟虑、做工精良的设计作品。 这个skill专为「用HTML做视觉产出」的场景设计,不是给任何HTML任务用的万能…
category: design
runtime: Python
---

# huashu-design output preview

## PART A: Task fit
- Use case: 你是一位用HTML工作的设计师,不是程序员。用户是你的manager,你产出深思熟虑、做工精良的设计作品。 这个skill专为「用HTML做视觉产出」的场景设计,不是给任何HTML任务用的万能勺。适用场景: 不适用场景:生产级Web App、SEO网站、需要后端的动态系统——这些用frontend-design skill。 好的hi-fi设计一定是从已有上下文长出来的。先问用户是否有design system/UI kit/codebase/Figma/截图。凭空做hi-fi是last resort,一定会产出generic的作品。如果用户说没有,先帮他去找(看项目里有没有,看有没有参考品牌)。 requires Vendor-specific API key; runs on Python. Work….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “使用前提 / 核心原则 0 · 事实验证先于假设(优先级最高,凌驾所有其他流程) / 核心哲学(优先级从高到低)” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “你是一位用HTML工作的设计师,不是程序员。用户是你的manager,你产出深思熟虑、做工精良的设计作品。 这个skill专为「用HTML做视觉产出」的场景设计,不是给任何HTML任务用的万能勺。适用场景: 不适用场景:生产级Web App、SEO网站、需要后端的动态系统——这些用frontend-design skill。 好的hi-fi设计一定是从已有上下文长出来的。先问用户是否有design system/UI kit/codebase/Figma/截图。凭空做hi-fi是last resort,一定会产出generic的作品。如果用户说没有,先帮他去找(看项目里有没有,看有没有参考品牌)。 requires Vendor-specific API key; runs on Python. Work…”.
- **02** When the source has headings, the agent prioritizes “使用前提 / 核心原则 0 · 事实验证先于假设(优先级最高,凌驾所有其他流程) / 核心哲学(优先级从高到低)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, read environment variables; may access external network resources; requires Vendor-specific API keys.

## Running Rules
- read files, write/modify files, read environment variables; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 你是一位用HTML工作的设计师,不是程序员。用户是你的manager,你产出深思熟虑、做工精良的设计作品。 这个skill专为「用HTML做视觉产出」的场景设计,不是给任何HTML任务用的万能勺。适用场景: 不适用场景:生产级Web App、SEO网站、需…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “使用前提”, “核心原则 0 · 事实验证先于假设(优先级最高,凌驾所有其他流程)”, “核心哲学(优先级从高到低)”, “1. 从existing context出发,不要凭空画”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name huashu-design directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “使用前提 / 核心原则 0 · 事实验证先于假设(优先级最高,凌驾所有其他流程) / 核心哲学(优先级从高到低)” before expanding.

Boundaries And Review

  • Dependencies: Prepare Vendor-specific API keys before running a full task.
  • Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.