bitwarden · withinfocus · Jun 5, 2026 · May 22, 2026 · May 22, 2026 · May 22, 2026
@@ -80,6 +80,18 @@
       "source": "./plugins/bitwarden-delivery-tools",
       "version": "1.3.0",
       "description": "Delivery lifecycle skills for Bitwarden initiatives — initiative funnel navigation, work transitions, tech breakdowns and cross-team signoffs, commits, pull requests, preflight checks, and change labeling."
+    },
+    {
+      "name": "bitwarden-designer",
+      "source": "./plugins/bitwarden-designer",
+      "version": "0.1.0",
+      "description": "Product designer agent for Bitwarden. Holds the design team's Code of Conduct and the 30/60/90 critique framework, and dispatches into the bitwarden-design-tools toolkit for content style, Figma reads, brand application, handoff prep, Design System governance, and the Product and Design Jira workflow."
+    },
+    {
+      "name": "bitwarden-design-tools",
+      "source": "./plugins/bitwarden-design-tools",
+      "version": "0.1.0",
+      "description": "Design toolkit for Bitwarden — non-persona skills for the design lifecycle. Content style guide reference, Figma Dev Mode MCP usage, Bitwarden brand application, design-to-engineering handoff prep, Design System governance, and the Product and Design Jira workflow. Composed by the bitwarden-designer agent and usable standalone."
     }
   ]
 }
@@ -9,16 +9,19 @@
     "appsec",
     "appsettings",
     "architecting",
+    "askable",
     "ASVS",
     "atlassian",
     "Bitwarden",
     "blocklist",
     "blogposts",
+    "bwi",
     "boardId",
     "bwwl",
     "catchable",
     "checkmarx",
     "CLAUDECODE",
+    "CMYK",
     "codeBlock",
     "CODEOWNERS",
     "Confluence",
@@ -33,11 +36,15 @@
     "ECDH",
     "ECIES",
     "editui",
+    "ESL",
     "evals",
     "excalidraw",
+    "EXIF",
     "executesql",
     "exfiltrated",
     "exploitability",
+    "FigJam",
+    "Figma",
     "frontmatter",
     "Gatekeep",
     "Gatekeeping",
@@ -52,6 +59,7 @@
     "hotspot",
     "hotspots",
     "IDOR",
+    "inclusivity",
     "issueIdOrKey",
     "issuelinks",
     "issuetype",
@@ -96,6 +104,7 @@
     "shortlog",
     "shortstat",
     "signoffs",
+    "Solutioning",
     "Smartlinks",
     "sonarcloud",
     "sonarqube",
@@ -114,8 +123,13 @@
     "touchpoint",
     "touchpoints",
     "triaging",
+    "unassigning",
+    "unassigns",
+    "ungroup",
     "unresponded",
     "unsanitized",
+    "userflow",
+    "Userflows",
     "userspace",
     "vnext",
     "vuln",

@@ -11,6 +11,8 @@ A curated collection of plugins for AI-assisted development at Bitwarden. Enable
 | [bitwarden-atlassian-tools](plugins/bitwarden-atlassian-tools/)     | 2.2.5   | Read-only Atlassian access via MCP server with deep Jira issue research skill                                                                               |
 | [bitwarden-code-review](plugins/bitwarden-code-review/)             | 1.11.0  | Autonomous code review agent following Bitwarden engineering standards with GitHub integration                                                              |
 | [bitwarden-delivery-tools](plugins/bitwarden-delivery-tools/)       | 1.3.0   | Delivery lifecycle skills: initiative funnel navigation, work transitions, tech breakdowns and cross-team signoffs, commits, PRs, preflight, labeling       |
+| [bitwarden-designer](plugins/bitwarden-designer/)                   | 0.1.0   | Product designer persona: Code of Conduct and 30/60/90 critique, critique facilitation; dispatches into bitwarden-design-tools                              |
+| [bitwarden-design-tools](plugins/bitwarden-design-tools/)           | 0.1.0   | Design toolkit: content style guide, Figma Dev Mode MCP, Bitwarden brand application, handoff prep, Design System governance, Product and Design Jira       |
 | [bitwarden-devops-engineer](plugins/bitwarden-devops-engineer/)     | 0.1.3   | DevOps engineering assistant: workflow compliance linting, action security auditing, and org-wide CI/CD remediation                                         |
 | [bitwarden-init](plugins/bitwarden-init/)                           | 1.2.0   | Initialize and enhance CLAUDE.md files with Bitwarden's standardized template format                                                                        |
 | [bitwarden-product-analyst](plugins/bitwarden-product-analyst/)     | 0.1.5   | Product analyst agent for creating comprehensive Bitwarden requirements documents from multiple sources                                                     |

@@ -0,0 +1,23 @@
+{
+  "name": "bitwarden-design-tools",
+  "version": "0.1.0",
+  "description": "Design toolkit for Bitwarden — non-persona skills for the design lifecycle. Content style guide reference, Figma Dev Mode MCP usage, Bitwarden brand application, design-to-engineering handoff prep, Design System governance, and the Product and Design Jira workflow. Composed by the bitwarden-designer agent and usable standalone.",
+  "author": {
+    "name": "Bitwarden",
+    "url": "https://github.com/bitwarden"
+  },
+  "homepage": "https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-design-tools",
+  "repository": "https://github.com/bitwarden/ai-plugins",
+  "keywords": [
+    "design-tools",
+    "content-style-guide",
+    "ux-writing",
+    "figma",
+    "figma-mcp",
+    "design-handoff",
+    "design-system",
+    "brand",
+    "branding",
+    "accessibility"
+  ]
+}
@@ -0,0 +1,20 @@
+# Changelog
+
+All notable changes to the `bitwarden-design-tools` plugin will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-05-22
+
+### Added
+
+- Initial release. `bitwarden-design-tools` is the toolkit half of the design plugin pair — non-persona skills for the design lifecycle, composed by the `bitwarden-designer` agent and usable standalone.
+- Six skills:
+  - `content-style-guide` — Bitwarden's product content style guide for GUI copy. Ported from the `designer-agent-skills` branch in `bitwarden/clients`, with progressive disclosure into `references/grammar-mechanics.md` and `references/accessibility-rules.md`.
+  - `using-figma` — read and inspect Figma designs via the Dev Mode MCP server. Read-only scope by `allowed-tools`; per-job-to-be-done tool selection across the read surface, with setup notes in `references/setup.md` and per-tool reference deferred to Figma's canonical docs.
+  - `applying-bitwarden-branding` — apply Bitwarden brand standards (logo, color, typography, iconography, capitalization) grounded in [bitwarden.com/brand](https://bitwarden.com/brand/) and the [bitwarden/brand](https://github.com/bitwarden/brand) repository. Full palette and asset inventory in `references/color-palette.md` and `references/brand-assets.md`.
+  - `preparing-design-handoff` — the end-of-In-Design gate / checklist. Confirm the Figma file is Ready-for-Dev (sections aligned to stories, tokens library-bound, strings annotated, edge states covered) and that the Jira state is aligned (Figma linked to the Epic's Design field, sections marked Ready for Dev, EM transitions the Epic).
+  - `evolving-design-system-components` — propose new patterns or modify existing components per the published governance process. Figma conventions in `references/figma-conventions.md`.
+  - `navigating-design-jira-process` — final designs attached to tickets, the 30/60/90 critique cadence tracked in Figma, status transitions on engineering epics and stories, and the one-off engineering story flow (link Figma to the story's Design field, unassign, comment that the design is ready).
+- Required cross-plugin dependency on `bitwarden-atlassian-tools` for Confluence access to the canonical design-team process pages.
@@ -0,0 +1,87 @@
+# Bitwarden Design Tools Plugin
+
+## Overview
+
+Design toolkit for Bitwarden — the non-persona half of the design plugin pair. Six skills covering content style, Figma Dev Mode MCP usage, Bitwarden brand application, design-to-engineering handoff prep, Design System governance, and the Product and Design Jira workflow. Composed by the `bitwarden-designer` agent and usable standalone (designers, design-adjacent engineers, PMs running a handoff).
+
+This plugin ships skills only — no agent. The persona half lives in [`bitwarden-designer`](../bitwarden-designer/), which dispatches into these skills by name.
+
+## Skills
+
+| Skill                               | What It Does                                                                                                                                                                                                                                                                                                                                             |
+| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `content-style-guide`               | Bitwarden's product content style guide for GUI copy — voice, tone, AP-style-with-exceptions grammar, sentence case in UI, no ampersands, and accessibility-first language at a U.S. 7th-grade reading level. Lean SKILL.md with detailed rules split across `references/grammar-mechanics.md` and `references/accessibility-rules.md`.                  |
+| `using-figma`                       | Read and inspect Figma designs via the Dev Mode MCP server. Per-job-to-be-done tool selection for read tools (`get_design_context`, `get_metadata`, `get_screenshot`, `get_variable_defs`, `search_design_system`, `get_libraries`), with Code Connect and write tools documented in their own subsections. Foundational — most other skills compose it. |
+| `applying-bitwarden-branding`       | Apply Bitwarden brand standards — logo usage, color palette, typography, iconography, and capitalization rules. Grounded in [bitwarden.com/brand](https://bitwarden.com/brand/) and the [bitwarden/brand](https://github.com/bitwarden/brand) repository. Full palette and asset inventory in `references/`.                                             |
+| `preparing-design-handoff`          | The end-of-In-Design gate / checklist. Confirm the Figma file is Ready-for-Dev (sections aligned to stories, tokens library-bound, strings annotated, edge states covered) and that the Jira state is aligned (Figma linked to the Epic's Design field, sections marked Ready for Dev, EM transitions the Epic).                                         |
+| `evolving-design-system-components` | Propose a new UI pattern or modify an existing Component Library component per Bitwarden's published governance process — design-team alignment, Core vs. Recipe/Snowflake with UI Foundation, Figma branching and property conventions, review gates, merge timing. Figma conventions in `references/figma-conventions.md`.                             |
+| `navigating-design-jira-process`    | Move design work through Bitwarden's Product and Design Jira workflow — final designs attached to tickets, the 30/60/90 critique cadence tracked in Figma, status transitions, and the one-off engineering story flow.                                                                                                                                   |
+
+## Cross-Plugin Integration
+
+| Plugin                      | How It's Used                                                                                                                                                                                                                                              |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `bitwarden-designer`        | Primary consumer. The designer persona dispatches into every skill here by name. Either plugin works standalone, but the pair is the intended shape.                                                                                                       |
+| `bitwarden-atlassian-tools` | Required. The Confluence-grounded skills here (`preparing-design-handoff`, `evolving-design-system-components`, `navigating-design-jira-process`) assume `get_confluence_page` is available to fetch the canonical pages directly when prepping real work. |
+
+All cross-plugin skills are required.
+
+## External Dependency: Figma Dev Mode MCP Server
+
+The `using-figma` skill assumes the user has installed and authenticated Figma's Dev Mode MCP server in their client. This server is **Figma's own product**, not bundled. It comes in two flavors (desktop, which requires a Dev or Full Figma seat on a paid plan, and remote). Setup details live in `skills/using-figma/references/setup.md`.
+
+If the Figma MCP tools aren't available in the session, the `using-figma` skill stops and asks the user to install before continuing. Other skills continue to function — they only compose `using-figma` when a Figma URL is in play.
+
+## Installation
+
+```bash
+/plugin install bitwarden-design-tools@bitwarden-marketplace
+```
+
+Most users will also want the persona half and the Atlassian access:
+
+```bash
+/plugin install bitwarden-designer@bitwarden-marketplace
+/plugin install bitwarden-atlassian-tools@bitwarden-marketplace
+```
+
+## Usage
+
+The skills here activate based on the task at hand — they can be invoked through the `bitwarden-designer` agent or standalone:
+
+```
+Review this copy: "Click here to learn more about export."
+```
+
+```
+Read this Figma frame and list the variables it uses: <figma URL>
+```
+
+```
+Is this banner on-brand? #175DDC headline, green CTA, Inter font.
+```
+
+```
+Walk me through the end-of-In-Design gate for the new vault filter project — is the Figma ready and the Jira state aligned?
+```
+
+```
+We keep building variations of this segmented selector — should it become a core component?
+```
+
+```
+PM created the epic, designs are at 60%. Walk me through the Jira choreography so engineering sees the right state.
+```
+
+## References
+
+- [bitwarden.com/brand](https://bitwarden.com/brand/) — brand guidelines hub.
+- [bitwarden/brand](https://github.com/bitwarden/brand) — brand assets repository.
+- [Weekly Design Critique & Etiquette (Quick Guide)](https://bitwarden.atlassian.net/wiki/spaces/PROD/pages/2329542659)
+- [Product Design Review Guidelines](https://bitwarden.atlassian.net/wiki/spaces/PROD/pages/469925913)
+- [Creating new design patterns](https://bitwarden.atlassian.net/wiki/spaces/PROD/pages/665780251)
+- [Modifying an existing Design System component](https://bitwarden.atlassian.net/wiki/spaces/PROD/pages/1804206168)
+- [Product and Design Jira Process](https://bitwarden.atlassian.net/wiki/spaces/PROD/pages/1828094078)
+- [Component Library](https://bitwarden.atlassian.net/wiki/spaces/PROD/pages/293109785)
+- [Figma Dev Mode MCP Server — Guide](https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Dev-Mode-MCP-Server)
+- [Figma Dev Mode MCP Server — Tools and Prompts](https://developers.figma.com/docs/figma-mcp-server/tools-and-prompts/)