wunderui-setup
Set Up WunderUI in Your React Project
WunderUI components can appear unstyled when package installation, Tailwind scanning, or token precedence is incomplete. This skill coordinates setup, creates a verification component, and documents remaining checks.
설치 전에 중지하고 확인을 요청하세요.
계획을 검토하고 파일을 변경하기 전에 사용자의 명시적 동의를 받으세요.
내 에이전트로 설치
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
Review the Skillstore skill "wunderui-setup" from https://skillstore.io/skills/wunder-ui-wunderui-setup.md and its manifest at https://skillstore.io/api/skills/wunder-ui-wunderui-setup/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
테스트해 보기
"wunderui-setup" 사용 중입니다. Check whether my Tailwind v3 project is ready for WunderUI.
예상 결과:
- Readiness: Tailwind v3 does not meet the supported styling requirement.
- Next action: approve a Tailwind v4 upgrade before continuing setup.
- Verification: a styled WunderUI probe remains pending.
"wunderui-setup" 사용 중입니다. Summarize setup after creating the probe and registering MCP.
예상 결과:
- Setup report: lists the detected framework, CSS entry, package information, and recorded changes.
- Browser check: confirm the probe button background is not transparent.
- MCP check: restart the editor and call get_library_info.
- Remaining work: confirm token precedence before building the first screen.
보안 감사
높은 위험Most static alerts are formatting, regular expression matching, or expected project file access. Confirmed command execution risks include shell interpolation of checkout paths and npm output. Additional risks include unverified persistent agent rules, an unpinned MCP launcher, and package execution during checkout dry runs; no malicious payload was found.
확인된 보안 우려 사항 (3)
기능 검토 항목 (4)
이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.
위험 요인
🌐 네트워크 접근 (5)
⚡ 스크립트 포함 (1)
⚙️ 외부 명령어 (47)
📁 파일 시스템 접근 (17)
이 보고서 공유 및 인용
버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.
보고서 링크 복사
https://skillstore.io/skills/wunder-ui-wunderui-setup/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 배지
[](https://skillstore.io/skills/wunder-ui-wunderui-setup?utm_source=security_passport_badge)HTML 배지
<a href="https://skillstore.io/skills/wunder-ui-wunderui-setup?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wunder-ui-wunderui-setup/security.svg" alt="Skillstore security assessment" loading="lazy"></a>임베드 카드
<iframe src="https://skillstore.io/embed/skills/wunder-ui-wunderui-setup.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-setup security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wunder-ui-wunderui-setup/audits/1BibTeX 인용
@techreport{wunder-ui-wunder-ui-wunderui-setup-2026,
author = {wunder-ui},
title = {wunderui-setup security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/wunder-ui-wunderui-setup/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-setup 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-setup/audits/1"
identifiers:
- type: other
value: "skillstore:wunder-ui-wunderui-setup:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 점수
이 점수의 이유 증거 신뢰도: 중간만들 수 있는 것
Configure a New React Interface
Add WunderUI to an existing React project and inspect a small component probe before building application screens.
Resolve Unstyled Components
Check Tailwind source scanning, stylesheet imports, and token precedence when existing WunderUI components render without expected styles.
Standardize Team Setup
Review design references and MCP configuration, then document project prerequisites and pending verification for a team handoff.
이 프롬프트를 사용해 보세요
Inspect my React project with WunderUI detection in dry mode. Identify the framework, Tailwind version, and CSS entry without installing packages.
Set up WunderUI for my Free plan. Ask before installation or edits, and show downloaded agent instructions for review before inserting them.
Diagnose why my WunderUI buttons are unstyled. Check the Tailwind source path and stylesheet order, preserve my tokens, and verify the probe.
Review my built WunderUI checkout before setup. Check shell arguments, lifecycle scripts, and MCP version trust; require approval before execution and report remaining checks.
모범 사례
- Review dependency sources, lifecycle scripts, downloaded rules, and the MCP launcher before approving execution.
- Run detection first, confirm Tailwind v4, and agree on token precedence before editing the CSS entry.
- Keep a recoverable project snapshot, inspect changes, and verify both the probe rendering and MCP availability.
피하기
- Treating --dry checkout installation as a guarantee that no subprocesses run or files change.
- Automatically trusting downloaded instruction files or an unpinned MCP package.
- Removing project token overrides or declaring setup complete without consent and browser verification.
자주 묻는 질문
Does this create a React project from nothing?
Can I use Tailwind v3?
Can I use a local Core or Pro checkout?
Will setup preserve my existing design tokens?
Why are MCP tools unavailable after registration?
Is dry mode guaranteed to avoid changes?
개발자 세부 정보
작성자
wunder-ui라이선스
MIT
Skillstore 리비전
r1
버전 안내
작성자가 버전을 선언하지 않았습니다.
참조
e406bf64b5db6e514879399e87b346fa7ff7c2fb
유지보수 최신성
2026. 10. 11.
사용량
0 다운로드 · 0 조회
파일 구조