📦

wunderui-screen

Name: wunderui-screen
Author: wunder-ui

Inhaltsrevision r1 Mittleres Risiko 🌐 Netzwerkzugriff📁 Dateisystemzugriff⚙️ Externe Befehle🔑 Umgebungsvariablen

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.

Unterstützt: Claude Codex Code(CC)

📊 72 Angemessen

Maintain this Skill? Claim it 📊 72 Angemessen

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/wunder-ui-wunderui-screen.md Signiertes manifest GET /api/skills/wunder-ui-wunderui-screen/manifest Signiertes lockfile GET /api/skills/wunder-ui-wunderui-screen/lockfile

Testen

„wunderui-screen“ wird verwendet. Build a profile settings screen on the Free plan.

Erwartetes Ergebnis:

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“ wird verwendet. Create a Free-plan revenue overview without paid charts.

Erwartetes Ergebnis:

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.

Sicherheitsaudit

Mittleres Risiko

v1 • 10.10.2026 Versionsbericht öffnen

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.

Gescannte Dateien

305

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Bestätigte Sicherheitsbedenken (1)

Mittel

scripts/screen.mjs:17-18 scripts/screen.mjs:113-114 scripts/screen.mjs:139-140 SKILL.md:22

Plan Restrictions Fail Open

Missing plan configuration defaults to Pro, and Core is not restricted separately. Free checks accept unknown component tiers when design metadata is unavailable or incomplete.

The code restricts only Free and rejects only known Pro tiers, despite instructions to determine the user plan first. This permits licensing violations.

Risikofaktoren

🌐 Netzwerkzugriff (5)

package.json:17 scripts/screen.mjs:25 scripts/screen.mjs:54 scripts/screen.mjs:11 scripts/screen.mjs:20

📁 Dateisystemzugriff (14)

references/layouts.md:7 scripts/screen.mjs:12 scripts/screen.mjs:17 scripts/screen.mjs:24 scripts/screen.mjs:119 scripts/screen.mjs:121 scripts/screen.mjs:124 scripts/screen.mjs:129 scripts/screen.mjs:131 scripts/screen.mjs:135 scripts/screen.mjs:136 scripts/screen.mjs:137 scripts/screen.mjs:141 scripts/screen.mjs:144

⚙️ Externe Befehle (34)

🔑 Umgebungsvariablen (2)

scripts/screen.mjs:20 scripts/screen.mjs:20

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

https://skillstore.io/skills/wunder-ui-wunderui-screen/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/wunder-ui-wunderui-screen/security.svg)](https://skillstore.io/skills/wunder-ui-wunderui-screen?utm_source=security_passport_badge)

HTML-Badge

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

Einbettungskarte

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

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

wunder-ui. (2026). wunderui-screen security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wunder-ui-wunderui-screen/audits/1

BibTeX-Zitat

@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-Score

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

Wartbarkeit

Inhalt

Gemeinschaft

Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

Create a Simple Settings Screen

Build a WunderUI profile settings screen on the Free plan. Use invented data, design tokens, and loading, empty, and error states.

Build a Responsive Dashboard

Build a sales dashboard on my WunderUI Pro plan. Find matching blocks, verify component props, and add responsive layouts and reviewable UI states.

Adapt a Screen for Free

Adapt my analytics screen for WunderUI Free. Replace paid components with documented free alternatives, preserve UI states, and explain the lost functionality.

Audit and Validate a Screen

Review [screen files] for my confirmed WunderUI plan. Verify component signatures, tokens, motion, and every data region. Run checks, typecheck, and build.

Bewährte Praktiken

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.

Vermeiden

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.

Häufig gestellte Fragen

Which assistants can use this skill?

The skill supports Claude, Codex, and Claude Code in a React project that uses WunderUI.

What does the bundled helper do?

It searches component and block metadata, then checks specified source files for WunderUI conventions. The assistant performs screen implementation.

Can I use the Free plan?

Yes. Specify Free explicitly and use documented free alternatives. Verify entitlements manually because missing metadata can bypass the helper checks.

Does it need network access?

Block search retrieves a public registry index. Component metadata is read locally when available, otherwise it is fetched from the configured site.

Does it guarantee a working screen?

No. Its regex checks are limited. The workflow also calls for project typechecking, building, and manual review of responsive layouts and UI states.

Does it upload project source or credentials?

No evidence found of source or credential uploads in the bundled helper. Network requests retrieve metadata, and source checks read explicitly selected files.