Claude Design skills on GitHub are the quiet leverage point for legal-tech builders nobody is covering. Anthropic launched Claude Design on April 17, 2026, and the same open-source pattern that shipped the Cowork legal plugin, published via the knowledge-work-plugins GitHub repo in February 2026 — applies to design. Per Anthropic's Claude Design documentation, the tool supports loadable skills: reusable prompt configurations that codify a design pattern. A skill that codifies "how our firm builds an intake form" or "our standard conflict-check dashboard layout" can be loaded once and reused across every future internal tool. For legal-tech builders publishing tools, skills are also a distribution channel. This walks through what skills actually are, how to build one for a legal-tech use case, and where to publish them. Pricing pulled from the Anthropic pricing page.

What a Claude Design skill actually is

A Claude Design skill is a reusable prompt configuration that captures a specific design pattern and can be invoked by name in any future Claude Design session. Per the Anthropic skills documentation, skills bundle together: a prompt template that describes the pattern, the design tokens or brand guidelines the pattern uses, any reference components or screenshots, and the instructions for how the pattern should adapt to different inputs.

For legal tech, useful skills cluster into three categories:

- Pattern skills. A skill that codifies a recurring UI pattern, "three-column triage dashboard," "client intake form with conflict question," "audit log with date filter and CSV export." Invoke the skill, pass it a context ("this is for an NDA triage tool"), and get a starting layout that already follows the pattern. - Brand skills. A skill that encodes a firm's design system, colors, typography, spacing, component styles. Invoke the skill at the start of any new build to anchor the output in the firm's brand. The Claude Design system integration for law firm brand covers this in detail. - Component-library skills. A skill that contains a curated set of pre-built components (form fields, buttons, navigation patterns, modals) that Claude Design uses as building blocks. Speeds up new builds because the components are already styled and behaviorally correct.

Skills are stored as configurations Claude can load, not as compiled libraries. They're text-based, version-controllable, and shareable. A skill written by one firm's legal-ops team can be forked and adapted by another firm without proprietary licensing concerns, assuming the original is published openly. The Claude Design for legal operations 2026 anchor frames where skills fit in the broader build pattern.

Walking through a representative skill build: "Legal Internal Tool Pattern", a generic skill for any internal tool a law firm wants to ship. The skill bundles design tokens, common UI patterns, and the conventions a firm wants every tool to follow.

Step 1: Define the pattern scope. Pick a bounded use case. Don't try to build a skill that handles every possible tool. Build one for "single-screen intake form" or "three-column triage dashboard" or "audit log with filters." Bounded skills are easier to maintain and produce more consistent output.

Step 2: Encode the design tokens. Reference your firm's design system (per Claude Design system integration for law firm brand). The skill inherits the firm's brand by default, every tool built with the skill looks like the firm.

Step 3: Write the pattern prompt. Describe the pattern in plain English: what fields, what layout, what behaviors, what disclaimers if relevant. For a legal-specific skill, include language about attorney-client disclaimers, conflict-check questions, and any compliance touches that should appear on every tool of this type.

Step 4: Include reference components. Attach screenshots or HTML examples of well-built versions of the pattern. The skill uses these as anchoring points when generating new builds. For an intake form skill, include a screenshot of an existing well-built intake form (yours or a public example). For a triage dashboard skill, include a wireframe of the desired layout.

Step 5: Test the skill on a representative build. Generate three or four sample tools using the skill. Check that each output is consistent, follows the pattern, and incorporates the design tokens correctly. Iterate the skill until outputs are reliably on-brand and on-pattern.

Step 6: Save and version the skill. Save the skill in Claude Design's skill library for casual invocation, and also commit the skill configuration to your firm's GitHub for version control. When the pattern evolves (firm rebrand, new compliance requirement, design refresh), update the skill in one place.

For a legal-ops team building two or three skills covering their most-common internal-tool patterns, the upfront skill-building investment is 8-16 hours total. The payoff: every future build of a tool matching one of those patterns starts from the skill instead of a blank prompt, saving 2-6 hours per new build.

Publishing skills publicly versus privately

Skills can live anywhere from "private to one user" to "public on GitHub." The question of where to publish has practical implications:

Private skills (firm-internal). The most common pattern. The skill lives in a private GitHub repo or in Claude Design's skill library scoped to your firm's Claude Team or Enterprise account. All firm staff can invoke the skill; nobody outside the firm sees it. This is the right default for skills containing firm-specific brand assets, internal-process patterns, or any patterns the firm considers competitive moat.

Public skills (open-source). Some legal-tech patterns are generic enough that there's no competitive harm in publishing them publicly, and there's reputational upside. A well-built "Legal Internal Tool Pattern" or "Attorney Directory Pattern" published on GitHub becomes a discoverability asset for your firm or your legal-tech practice. Other firms fork it, contribute back, and your firm's name shows up in legal-tech conversations.

The middle path: anonymized public skills. Build the skill privately with firm-specific tokens, then publish a stripped-down version with placeholder tokens. The public version captures the pattern; the private version retains the firm's brand. This is the same pattern Anthropic uses for its open-source Cowork legal plugin, the public skill is generic; firm-specific configuration happens locally.

For most law firms, the right play is a mix: keep brand and process-specific skills private; publish generic patterns publicly. The legal-tech community is small enough that contributing useful public skills earns visibility. The Claude Design for legal operations 2026 anchor covers the broader stack of internal-tool building, of which skills are one layer.

Honest assessment of the current state: the public ecosystem of legal-tech-specific Claude Design skills is small. Anthropic published its Cowork legal plugin in February 2026 with /review-contract and /triage-nda commands, which are technically Cowork plugins rather than Claude Design skills, but represent the same open-source publishing pattern. As of April 28, 2026, public Claude Design skills targeted at legal use cases are largely not yet published.

This is opportunity, not gap. The first firm to publish a useful legal-tech skill repo earns the discoverability win. A repo containing 5-10 skills covering common internal-tool patterns (intake forms, triage dashboards, audit logs, attorney directories, conflict-check dashboards) becomes the default reference for any firm or legal-tech builder starting from Claude Design.

For legal-tech vendors, skills are also a distribution channel. A vendor that publishes a Claude Design skill matching its product's UI patterns gives prospective customers a working starting point. The customer builds a free in-house version using the skill, hits the limits, and converts to the vendor's full product when the in-house build runs out of capacity. This is the same pattern as open-source-then-commercial software (think Vercel/Next.js, Supabase, Resend) applied to legal-tech.

For in-house legal-tech teams at law firms, skills are a way to externalize practice. A senior in-house legal-tech engineer publishes a public skill, the legal-tech community sees it, conferences invite the engineer to speak, the firm's legal-tech reputation grows. Investment: a few hours per skill. Return: brand asset that compounds over years. The Claude Design system integration for law firm brand covers the design-tokens layer that makes skills consistent.

The Bottom Line: The verdict: Claude Design skills are the highest-leverage way to encode repeating internal-tool patterns. Build skills for your firm's most-common build patterns (intake form, triage dashboard, audit log) and every future build starts from the skill instead of a blank prompt. For private firm patterns, keep skills in a private repo. For generic legal-tech patterns, publish to GitHub publicly — the legal-tech community is small enough that useful public skills earn real visibility. Either way, version-control the skills so they survive firm rebrands and process changes.

AI-Assisted Research. This piece was researched and written with AI assistance, reviewed and edited by Manu Ayala. For deeper takes and the perspective behind the research, follow me on LinkedIn or email me directly.