wunderui-screen
Build React Screens with WunderUI
Generated screens often miss UI states, responsive layouts, and consistent design tokens. This skill guides WunderUI component selection, screen assembly, and validation within the selected plan.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "wunderui-screen" from https://skillstore.io/skills/wunder-ui-wunderui-screen.md and its manifest at https://skillstore.io/api/skills/wunder-ui-wunderui-screen/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「wunderui-screen」を使用しています。 Build a profile settings screen on the Free plan.
期待される結果:
- Illustrative result: a settings screen using free form and feedback components.
- Loading, empty, and error states are available through a development status control.
- The completion report identifies changed files, selected components, defaults, and validation results.
「wunderui-screen」を使用しています。 Create a Free-plan revenue overview without paid charts.
期待される結果:
- Illustrative result: metric cards, trend indicators, and progress bars replace chart regions.
- Loading placeholders, an empty overview, and retryable errors remain available.
- The report notes that paid charts and the full app shell require an appropriate paid plan.
セキュリティ監査
中リスクAll 62 static findings are false positives involving documentation, JavaScript syntax, expected project reads, or public metadata requests. A semantic finding identifies plan enforcement that defaults to Pro and permits imports with unknown licensing metadata. No evidence found of malicious prompt injection, credential collection, or data exfiltration.
確認済みのセキュリティ上の懸念 (1)
リスク要因
🌐 ネットワークアクセス (5)
📁 ファイルシステムへのアクセス (14)
⚙️ 外部コマンド (34)
🔑 環境変数 (2)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/wunder-ui-wunderui-screen/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/wunder-ui-wunderui-screen?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/wunder-ui-wunderui-screen?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wunder-ui-wunderui-screen/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/wunder-ui-wunderui-screen.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
wunder-ui. (2026). wunderui-screen security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wunder-ui-wunderui-screen/audits/1BibTeX形式の引用
@techreport{wunder-ui-wunder-ui-wunderui-screen-2026,
author = {wunder-ui},
title = {wunderui-screen security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/wunder-ui-wunderui-screen/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wunderui-screen security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "wunder-ui"
date-released: "2026-10-10"
url: "https://skillstore.io/skills/wunder-ui-wunderui-screen/audits/1"
identifiers:
- type: other
value: "skillstore:wunder-ui-wunderui-screen:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Build Product Dashboards
Assemble a responsive dashboard with plan-appropriate metrics, data regions, actions, and reviewable loading, empty, and error states.
Prototype Settings Screens
Create a Free-plan settings screen using forms, feedback components, design tokens, and invented sample data.
Review Screen Consistency
Check existing screen files for token violations, deep imports, missing state indicators, and known paid components before project validation.
これらのプロンプトを試す
Build a WunderUI profile settings screen on the Free plan. Use invented data, design tokens, and loading, empty, and error states.
Build a sales dashboard on my WunderUI Pro plan. Find matching blocks, verify component props, and add responsive layouts and reviewable UI states.
Adapt my analytics screen for WunderUI Free. Replace paid components with documented free alternatives, preserve UI states, and explain the lost functionality.
Review [screen files] for my confirmed WunderUI plan. Verify component signatures, tokens, motion, and every data region. Run checks, typecheck, and build.
ベストプラクティス
- Confirm the plan explicitly and verify component entitlements before accepting suggestions or importing blocks.
- Read real component signatures and use design tokens before implementing each screen region.
- Review each UI state on mobile and desktop, then run source checks, typecheck, and build.
回避
- Treating a successful regex check as proof of runtime correctness or license compliance.
- Copying paid component designs by hand to bypass plan restrictions.
- Using real personal data, guessed props, or hardcoded motion and color values in generated screens.