← Plugin catalog
Creativity

Devault

HYDRANODE LTD v1.0.1

UI research and design systems

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Search UI screens
  • Analyze design patterns
  • Find similar screens

Cost & access

This plugin does not sell products or process payments. It reads from the library with the user's existing Devault account.

Declared limitations

  • Bulk export is not supported. The plugin has no tool that downloads or lists the whole library, and should say so instead of attempting it.
  • Account and billing changes are out of scope. The plugin only reads, and should point to devault.design instead of acting.
  • An unrelated request. Nothing in it concerns design references, so no Devault tool should be called.

Onboarding example

Find onboarding screens from fintech apps

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 16, 2026.

View package source →

Description

From the marketplace listing

Devault is a library of UI design references: screens from real websites and mobile apps, complete user flows, marketing emails, year-by-year redesigns and original interface concepts, each tagged by platform, industry, screen type and components. With this plugin, ChatGPT and Codex can research that library while you work: - Search screens by description, and narrow by platform, industry, screen type or company. - Analyze a design pattern across the library: how common it is, where it appears and which components go with it. - Have the assistant study a screen at a readable size and describe it, or find screens that look like one you picked. Every screen comes with a link that opens it on devault.design. - Fetch a ready-made design system (palette, contrast grades, type scale, spacing) as DESIGN.md, Tailwind v4, CSS variables, shadcn/ui, design tokens, Figma variables, SwiftUI, Android XML or an image prompt. It is for designers, developers and product teams who want a decision to rest on how shipped products look. Good to know: the plugin only reads, and cannot change anything in your Devault account. Screens are references for study and inspiration; the companies shown are not affiliated with Devault. A search returns one page of results, and the number of images is limited per day. You need a Devault account whose plan includes MCP access.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 16, 2026. Last seen Nov 16, 2026.

Keywords

Files & skills

File archives

Plugin package10 files · 46.2 KBBrowse files →
Skill instructions
apply-design-system2.25 KB

View saved version →

---
name: apply-design-system
description: Find a ready-made design system in Devault's DESIGN.md library and deliver it in the format the user's project needs. Use when the user wants a palette, design tokens, a theme, a DESIGN.md file or a starting visual style for a build, in Tailwind, CSS variables, shadcn/ui, design tokens, Figma variables, SwiftUI or Android.
---

Use this skill when the user wants a design system or tokens to build with,
for example "give me a dark fintech theme for Tailwind" or "I need a DESIGN.md
for a warm editorial site".

## Steps

1. Work out two things: the feel the user wants (for example "dark saas
   dashboard" or "warm editorial") and the format. The formats are
   `design-md`, `tailwind`, `css`, `shadcn`, `tokens`, `figma`, `swiftui`,
   `android` and `image-prompt`. If the user's stack makes the format obvious,
   use it. Otherwise ask, or use `design-md`.
2. Call `get_style` with `query` set to the feel and `format` set to the
   format. If the user named an exact system, or pasted a link to a page under
   devault.design/design-md, pass its slug as `style` instead.
3. If the user wants to choose from several, call `list_styles`, with a
   `category` if they named one, and show the names and taglines. Fetch the one
   they pick with `get_style`.
4. To look at the design the system was derived from, call `get_screen_image`
   with the `view_token` from the `get_style` result. The image is for you:
   describe it, and point the user to the system's page (`url`) to see it.

## What to deliver

- The system's name, one line on its character, and its page (`url`).
- The `content` exactly as returned, in a code block, ready to paste. Do not
  rename tokens or change colour values.
- The contrast results that matter (`contrast`): which text colours pass on
  which surfaces, and any pair that fails.
- If `alternatives` came back, name one or two in case the first is not right.

## Rules

- Do not invent a system, a token or a contrast grade. Use what the tool
  returned.
- If nothing matches the query, say so and suggest a broader phrase.
- When you apply the system to the user's code, keep the token names from the
  export so that a later export stays compatible.
- An explicit instruction from the user takes priority over these steps.

Referenced files: 1 — file references are metadata, not package contents.

get-started1.85 KB

View saved version →

---
name: get-started
description: Introduce the Devault plugin and get a first result. Use when the user has just installed or connected Devault, asks what Devault can do here, or asks how to start.
---

Use this skill when the user is new to the Devault plugin or asks what it can do.

1. Say in two or three sentences what Devault is: a library of UI design
   references (screens from real websites and apps, user flows, marketing
   emails, redesign histories and original concepts), and a library of
   ready-made design systems.
2. Offer three things to try, in the user's own field if you know it:
   - Find references: "Find onboarding screens from fintech apps."
   - Study a pattern: "How do apps design paywalls?"
   - Get a design system: "Get a dark dashboard design system as Tailwind tokens."
3. If the user picks one, or has already asked for something specific, do it
   straight away with the matching tool: `search_screens`, `analyze_pattern`
   or `get_style`.

What to know before the first call:

- Devault works with the user's own Devault account. If a tool reports that
  the account is not connected, or that its plan does not include these tools,
  say so plainly and stop. Do not suggest a way around it.
- Every tool only reads. Nothing here changes the user's account.
- `search_screens` returns one page of results. To see different results,
  change the query or the filters; there is no next page.
- Images are counted per day. Fetch a larger image with `get_screen_image`
  only for the screens worth a closer look.
- The images the tools return are for you to look at. The user does not see
  them. Describe what a screen shows and link it by its `url`, which opens the
  screen on devault.design; do not say that a screen is shown above.

Do not describe a screen you have not retrieved, and do not say that the
companies shown endorse Devault or work with it.

Referenced files: 1 — file references are metadata, not package contents.

research-ui-patterns3.2 KB

View saved version →

---
name: research-ui-patterns
description: Research how real products design a screen, flow or pattern using Devault's library, and report findings with the screens that support them. Use when the user asks how apps or websites handle something (onboarding, paywalls, checkout, empty states, pricing pages), wants UI references or examples, or wants a design decision grounded in real products.
---

Use this skill for questions such as "how do fintech apps handle onboarding?",
"show me paywall examples" or "what do good empty states have in common?".

## Steps

1. Pin down the subject: the pattern or screen type, and any platform (`ios`,
   `android`, `web`, `email`), industry or company the user named. If the
   request is too broad to search, for example "show me good design", ask one
   question to narrow it.
2. If you plan to filter by industry or screen type and are not sure of the
   value, call `list_taxonomy` once and use a value it returns.
3. For "how do products do X" questions, call `analyze_pattern` with the
   pattern as a short phrase, for example "paywall". Its statistics give the
   overall picture: how many screens, which platforms and industries, which
   components appear with the pattern, and the split between light and dark.
4. Call `search_screens` for specific examples. Use two to five keywords, not
   a sentence, and put constraints in the filters (`platform`, `industry`,
   `screen_type`, `brand`) instead of the query. If nothing matches, drop a
   word or a filter and try once more.
5. Look closer only where it helps. Call `get_screen_image` with a result's
   `view_token` for the two to four screens that matter most. A token works
   once and for five minutes; call `get_screen` with the `screen_id` for a
   fresh one. For tall captures such as emails and landing pages, pass
   `section` (`top`, `middle` or `bottom`).
6. To widen the search from one good example, call `get_similar_screens` with
   its `screen_id`.
7. For a single company, `get_brand_overview` shows what the library holds
   before you search with `brand`.

## What to report

- Start with the answer: the two to four things the examples have in common,
  or the main ways they differ.
- Support each point with screens you retrieved: the title, the company, and
  what to notice, each linked to its page (`url`).
- The images the tools return are for you to look at. The user does not see
  them, so describe what a screen shows and link it; do not say that a screen
  is shown above or attached.
- When you used `analyze_pattern`, give its numbers as returned.
- If the user said what they are building, end with what this suggests for
  their design.

## Rules

- Cite only screens returned in this conversation. Never invent a screen, a
  company's design or a statistic.
- If the library has little or nothing on the subject, say so.
- The screens are references for study. Do not present them as templates to
  copy, and do not say the companies shown are affiliated with Devault.
- Do not try to list or export the library. Each search is one page of
  results by design.
- If a tool says a limit was reached, tell the user and carry on with what you
  already have.
- An explicit instruction from the user takes priority over these steps.

Referenced files: 1 — file references are metadata, not package contents.

Release notes

First release: search and pattern analysis over Devault's UI references, detailed looks at individual screens, similar-screen lookup, and ready-made design systems in nine export formats.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
HYDRANODE LTD
Keywords
See keywords
Getting started skill
./skills/get-started/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Search UI screens
  • Analyze design patterns
  • Find similar screens
  • Study screens in detail
  • Fetch design systems

Package observed Nov 16, 2026.

Technical details
First seen
Nov 16, 2026 · 18:00 UTC
Last seen
Nov 16, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6ac3fb22bd1481919a5b86821560dbc3

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.