arndvs/ux-inform-engage-invite
skills/ux-inform-engage-invite/SKILL.md
Step 5.2 of Sketch the Solution. Apply the Inform → Engage → Invite framework to each screen. Use when asked to 'inform engage invite', 'screen intent', 'screen structure framework', or 'IEI framework'.
development
Updated Apr 30, 2026
$ install --global
skillsauthnpx skillsauth add arndvs/ctrlshft ux-inform-engage-inviteInstall 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 30, 2026, 2:37 AM16.4s1 file scanned
SKILL.md
- name:
- ux-inform-engage-invite
- description:
- Step 5.2 of Sketch the Solution. Apply the Inform → Engage → Invite framework to each screen. Use when asked to 'inform engage invite', 'screen intent', 'screen structure framework', or 'IEI framework'.
UX Step 5.2 — Inform → Engage → Invite
Output "Read UX Inform Engage Invite skill." to chat to acknowledge you read this file.
Phase: /ux-screen-requirements → Step 2 of 3
Structure each screen's intent using the three-part framework. Every screen should Inform the user (build trust/context), Engage them (show value), and Invite them forward (call to action).
Process
- For each screen, define three layers:
### [Screen Name]
**Inform** — What context/trust does the user need?
- [e.g., "Benefits per user type", "Testimonials", "Press mentions"]
- [e.g., "Breadcrumb showing location in the app"]
**Engage** — What value does the user get here?
- [e.g., "Preview of member profiles with relevant skills"]
- [e.g., "Content excerpts with author and date"]
**Invite** — What action should the user take next?
- [e.g., "View Full Profile button", "Post Content CTA"]
- [e.g., "Search/filter controls to refine results"]
-
Landing pages get extra attention:
- Inform: headline, sub-copy, how-it-works steps, trust elements (featured companies, testimonials, press)
- Engage: show value before asking for anything — previews, demos, examples
- Invite: primary CTA per user type, secondary CTA (learn more)
-
Internal screens are simpler:
- Inform: breadcrumb, page title, current state
- Engage: the content/data/functionality
- Invite: primary action button, navigation to related screens
Rules
- Engage before asking for anything — show value first, then request credentials
- Trust elements are critical on entry/landing screens
- Every screen must have at least one clear Invite (CTA)
- The Inform layer prevents users from feeling lost
- Apply the Instant Gratification principle from Phase 3
Output
Append to screen-requirements.md: Per-screen Inform/Engage/Invite breakdown.
Related Skills
arndvs/visual-feedback
development
VerifiedTrustedCommunity
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
SKILL.mdUpdated May 21, 2026
arndvs/press1-check
development
VerifiedTrustedCommunity
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
SKILL.mdUpdated May 21, 2026
arndvs/plan-archive
tools
VerifiedTrustedCommunity
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
SKILL.mdUpdated May 21, 2026
arndvs/grill-with-docs
testing
VerifiedTrustedCommunity
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
SKILL.mdUpdated May 21, 2026