Menu

Individual skill

dev-design-context

Establish or update persistent product and visual design guidance in .design-context.md. Use for initial design setup, a deliberate design-direction reset, or explicit 设计上下文 requests. Discover existing users, components, tokens, assets, and constraints before asking about material gaps. Does not implement UI; ordinary UI work does not require repeating this setup.

plugins/Jason-chen-coder/dev-skills/skills/dev-design-context/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Dev Design Context

Persist the project-specific design decisions future UI work needs. Read [references/dev-baseline.md](references/dev-baseline.md). This skill writes design guidance, not application code, mockups, or implementation reviews.

## Establish what is already known

Read existing `.design-context.md`, product/brand documentation, representative screens, reusable components, design tokens, and actual assets. Inspect relevant paths rather than cataloging every style declaration. Distinguish deliberate conventions from isolated inconsistencies or legacy accidents.

Capture the audience and their recurring tasks, product context, visual hierarchy, typography, color roles, layout density, component patterns, asset identity, supported devices, and interaction/accessibility constraints where evidenced. Reference source paths so future agents can find authoritative tokens and components rather than duplicating them.

An existing valid design context usually needs no update. An absent `.design-context.md` does not block implementation when existing instructions, code, or supplied designs already establish the direction.

## Resolve material gaps