fluxly Search skills… ⌘K 中文 Publish

design-system-patterns

Design Community
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating…
  • 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 “When to Use This Skill”, “Core Capabilities”, “1. Design Tokens”, “2. Theming Infrastructure”, 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 design-system-patterns 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 “When to Use This Skill / Core Capabilities / 1. Design Tokens” 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; 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
88 / 100 · heuristic scan, not runtime safety proof
Author / version / license
@wshobson · no license declared
Fluxly token estimate
Lean
Fluxly setup estimate
Plug-and-play
External API key
No requirement detected
Detected OS requirements
Unspecified
Runtime requirements
Unspecified
Detected file/system behavior
  • Read-only
  • Write / modify
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 design-system-patterns.preview 
# Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

Discussion

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