petrogurcak/ui
plugins/ux/skills/ui/SKILL.md
Use when designing or improving any UI — combines UX analysis with copywriting for interface text. Covers screens, components, pages, forms, modals, onboarding flows.
$ install --global
skillsauthnpx skillsauth add petrogurcak/skills uiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:50 AM4.3s1 file scanned
SKILL.md
- name:
- ui
- description:
- Use when designing or improving any UI — combines UX analysis with copywriting for interface text. Covers screens, components, pages, forms, modals, onboarding flows.
UI Skill
Combined UX + copywriting workflow for interface work. Runs both disciplines together instead of separately.
When to Use
- Designing new screens, pages, or components
- Improving existing UI (layout + copy together)
- Landing pages, forms, modals, onboarding flows
- Any "make this UI better" request
Workflow
Phase 1: Understand
Read the current UI (screenshot, code, or description). Identify:
- What it is: Page type, component, flow
- Who sees it: User segment, context, state
- What it should do: Primary action, success metric
Phase 2: UX Analysis
Invoke ux-orchestrator to determine the right UX approach:
- New design or redesign →
ux-expert-dialogue(section-by-section critique) - Has conversion data →
ux-optimization(data-driven) - Clarity problem →
uvp-optimization(positioning first)
Apply UX findings: layout, hierarchy, flow, interactions.
Phase 3: Copy
Invoke copywriting-orchestrator to handle all interface text:
- Web pages →
web-copy(headlines, CTAs, sections) - Product UI →
product-copy(descriptions, features) - Onboarding/emails →
newsletter(sequences)
Apply copy to the UX structure from Phase 2.
Phase 4: Integration Check
Verify UX and copy work together:
| Check | Question | |-------|----------| | Hierarchy | Does the most important copy sit in the most prominent UI position? | | Scannability | Can user get the point in 5 seconds without reading everything? | | CTA clarity | Is there one clear primary action? Does the button text say what happens? | | Consistency | Same tone, same terminology across all elements? | | Mobile | Does the copy still work when the layout stacks vertically? |
Quick Routing
| UI Type | UX Skill | Copy Skill |
|---------|----------|------------|
| Landing page | ux-expert-dialogue | web-copy |
| Product page | ux-optimization | product-copy |
| Form/checkout | ux-optimization | web-copy (microcopy) |
| Onboarding flow | ux-expert-dialogue | newsletter + web-copy |
| Dashboard/app screen | ux-expert-dialogue | product-copy |
| Modal/dialog | ux-optimization | web-copy (microcopy) |
Iron Laws
- UX before copy. Structure first, words second. Don't write headlines for a broken layout.
- Copy validates UX. If you can't write a clear CTA, the flow is wrong.
- One screen, one job. If the copy needs to explain too much, the UI is doing too much.
Related Skills
petrogurcak/testimonial-harvesting
development
VerifiedTrustedCommunity
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
2SKILL.mdUpdated May 14, 2026
petrogurcak/launch-orchestrator
development
VerifiedTrustedCommunity
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
2SKILL.mdUpdated May 14, 2026
petrogurcak/info-product-launch
testing
VerifiedTrustedCommunity
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
2SKILL.mdUpdated May 14, 2026
petrogurcak/mobile-store-release
development
VerifiedTrustedCommunity
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).
2SKILL.mdUpdated May 14, 2026