j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan/addons/design-system
deepworkplan-addon-design-system
VerifiedOptional DeepWorkPlan addon that gives a repo with a user-facing interface surface a DESIGN.md (under docs/, indexed from AGENTS.md) — a Markdown design-system file any coding agent reads to generate interface output consistent with the repo's OWN conventions. Covers three profiles detected independently from real files — visual-ui (rendered web/mobile/desktop UI), cli-output (styled terminal output — semantic colors, panels, spinners, prompts, TTY/NO_COLOR degradation), and conversational (chat/email messaging — voice and register, message anatomy, per-platform rendering). Reasons about the repo's ACTUAL design source (CSS custom properties, Tailwind config, token files, component styles, a CLI display/theme module, or message-composition helpers) rather than copying a brand file; checks contrast (WCAG AA), color-is-not-the-only-carrier, plain-text fallbacks, and token integrity. A detected interface surface makes the evaluation and offer mandatory (with a clear recommendation), while installation always requires explicit acceptance — no profile is auto-applied, even in trust mode. Never offered for a repo with no interface surface (pure library, headless service, infra-only); never required for baseline conformance; reconciles an existing DESIGN.md instead of clobbering it. Use when the developer wants agents to produce on-brand, consistent interface output — visual UI, terminal output, or outbound messages.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.9 KB |
| SPEC.md | markdown | 21.7 KB |
| addon.json | config | 212 B |
| templates/DESIGN.md.md | markdown | 8.0 KB |
| templates/agent_prompt_guide.md | markdown | 2.2 KB |
| templates/design-system-command.md | markdown | 2.7 KB |
| templates/presets.md | markdown | 6.3 KB |
templates/design-system-command.md
View on GitHub# Template — `/design-system` delegator command (reasoning aid)
This is the **delegator command** the design-system addon **MAY** install into the
target repo's `.agents/commands/design-system.md` **only when the addon is
accepted** during `onboard` Phase 7b (or when the addon is run directly) **and** the
developer wants a one-command way to refresh `DESIGN.md` later. It is a **thin
delegator**: it carries no logic of its own — it routes to the
`deepworkplan-addon-design-system` addon, which holds the real flow.
Installing this command is **optional** (`SPEC.md` §9). Fill the placeholders by
reasoning about the target repo (its real design source and accessibility rules);
do not copy verbatim. Decline the addon → do **not** install this command.
```markdown
---
name: design-system
description: Create or refresh this repo's DESIGN.md (design tokens + rules for AI agents; at docs/DESIGN.md, indexed from AGENTS.md) via the DeepWorkPlan design-system addon.
---
# /design-system
Create or refresh this repository's `DESIGN.md` (at `docs/DESIGN.md`, indexed from
`AGENTS.md`) so coding agents generate interface output — visual UI, terminal
output, or outbound messages — consistent with this repo's **own** conventions.
This command is a **thin delegator** to the DeepWorkPlan
`deepworkplan-addon-design-system` addon — it does not contain the logic itself.
## Steps
1. Invoke the `deepworkplan-addon-design-system` addon (via
`/deepworkplan-addon-design-system` or by reading the addon's `SKILL.md`).
2. Follow the addon's flow: locate this repo's real design source per profile
(<e.g. CSS custom properties in `src/styles/global.css` + a Tailwind `@theme`
block; or the CLI display module; or the message-composition helpers>), reason
out each accepted profile's canonical sections of `DESIGN.md` from that
source, and write or **reconcile** `DESIGN.md` at its location
(`docs/DESIGN.md` for a repo with a `docs/` tree; root otherwise), ensuring
`AGENTS.md` references it.
3. Run the addon's validation step (sections present per accepted profile, values
traceable to the real source, per-profile integrity — WCAG AA contrast /
degradation rules / plain-text fallbacks — and token references resolve).
## Notes
- Profiles in this repo: <fill in — e.g. visual-ui / cli-output / conversational>.
- Design source for this repo: <fill in — e.g. Tailwind config / CSS vars / token file / CLI display module / message helpers>.
- Integrity rules to enforce: <fill in — e.g. WCAG AA + approved/forbidden text colors; NO_COLOR degradation; plain-text fallbacks>.
- Reason about the real tokens — never paste a third-party brand's `DESIGN.md`.
- Reconcile an existing `DESIGN.md`; ask before any destructive change.
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |