Skip to content

j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan/addons/design-system

deepworkplan-addon-design-system

Verified

Optional 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.

FileKindSize
SKILL.mdskill md13.9 KB
SPEC.mdmarkdown21.7 KB
addon.jsonconfig212 B
templates/DESIGN.md.mdmarkdown8.0 KB
templates/agent_prompt_guide.mdmarkdown2.2 KB
templates/design-system-command.mdmarkdown2.7 KB
templates/presets.mdmarkdown6.3 KB

templates/agent_prompt_guide.md

View on GitHub
# Reasoning template — the "Agent Prompt Guide" block

Every `DESIGN.md` ends with a short **Agent Prompt Guide**: a "how to use this file"
block that tells a downstream coding agent to follow the design system. Adapt the
wording to the repo, keep it to a few lines, and reference the repo's real token
names.

---

## Drop-in block (adapt the bracketed parts)

```markdown
## Agent prompt guide

**For coding agents working in this repo:** this `DESIGN.md` is the source of truth
for every interface surface it covers (visual UI, CLI output, outbound messages).
Before generating or editing any user-facing output:

1. **Use the named tokens** in this file (colors, type, spacing, radius — or
   semantic CLI styles and message conventions) — do not introduce ad-hoc values
   outside it.
2. **Respect roles** — pick a color/style by its *role* (e.g. `color.accent` for
   primary actions, the `success` style for completed operations), not by
   eyeballing a value.
3. **Keep integrity** — text pairings must meet the contrast targets in Do's &
   Don'ts; CLI output must stay legible when piped or colorless; rich messages
   keep their plain-text fallback.
4. **Match the documented patterns** — reuse the Button/Input/Card patterns, the
   display helpers (`print_success`, panels, spinners), or the message envelopes
   and voice rules, with their states.
5. **When something isn't covered**, choose the option most consistent with the
   conventions here and note the gap rather than inventing an unrelated style.

Suggested instruction to paste into an agent prompt:
> "Follow `DESIGN.md` strictly. Build [the output] using its tokens, roles, and
>  documented patterns; keep the integrity rules (contrast / degradation /
>  fallbacks) intact."
```

---

## Notes

- Reference the repo's **actual** token/helper names (e.g. `color.accent`,
  `--color-ink`, `oxblood`, `print_success`, `mrkdwn`) so the guidance is
  concrete, not generic — covering every profile present in the file.
- If the repo installed a `/design-system` delegator, you MAY mention it here
  ("run `/design-system` to refresh this file after design changes").
- Keep this block short — its job is to point agents at the rest of the file, not to
  repeat it.
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: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall