canvas-design

Design Community
  • Repo stars 0
  • License Complete terms in LICENSE.txt
  • Author updated Aug 22, 2026, 01:10 AM
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to…
  • 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 “DESIGN PHILOSOPHY CREATION”, “THE CRITICAL UNDERSTANDING”, “HOW TO GENERATE A VISUAL PHILOSOPHY”, “PHILOSOPHY EXAMPLES”, 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 canvas-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 “DESIGN PHILOSOPHY CREATION / THE CRITICAL UNDERSTANDING / HOW TO GENERATE A VISUAL PHILOSOPHY” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write / shell-exec; 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.
Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates
Fluxly category
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Author / version / license
@anthropics · Complete terms in LICENSE.txt
Fluxly token estimate
Lean
Fluxly setup estimate
Guided setup
External API key
No requirement detected
Detected OS requirements
Unspecified
Runtime requirements
Unspecified
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Detected network behavior
Local-only
Install commands
None (reference only)

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

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

Output preview canvas-design.preview
# PHILOSOPHY EXAMPLES

**"Concrete Poetry"** Philosophy: Communication through monumental form and bold geometry. Visual expression: Massive color blocks, sculptural typography (huge single words, tiny labels), Brutalist spatial divisions, Polish poster energy meets Le Corbusier. Ideas expressed through visual weight and spatial tension, not explanation. Text as rare, powerful gesture - never paragraphs, only essential words integrated into the visual architecture. Every element placed with the precision of a master craftsman. **"Chromatic Language"** Philosophy: Color as the primary information system. Visual expre

Discussion

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