tjboudreaux/eng-user-impact
skills/eng-user-impact/SKILL.md
Anchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.
$ install --global
skillsauthnpx skillsauth add tjboudreaux/cc-plugin-engineering-excellence eng-user-impactInstall 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 25, 2026, 9:35 PM1.8s1 file scanned
SKILL.md
- name:
- eng-user-impact
- description:
- Anchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.
User Impact and Product Sense
Intent
- Translate technical work into clear user outcomes (fun, trust, productivity, revenue).
- Ensure flows are accessible, consistent, and measurable across mobile, web, and decentralized surfaces.
Workflow
- Clarify the user story
- Write the scenario in plain language (persona, goal, success metric).
- Note must-haves vs delights; align with PM/design if ambiguous.
- Define acceptance signals
- Specify behavioral analytics, A/B guardrails, or smart-contract events to prove impact.
- Include accessibility requirements (screen readers, haptics, color contrast, controller support).
- Prototype + validate early
- Use lightweight demos, storybooks, simulators, or testnets to gather feedback quickly.
- Instrument thoughtfully
- Add analytics hooks or telemetry to measure adoption without leaking sensitive data.
- Close the loop
- Plan post-launch follow-up: metrics to review, user feedback channels, rollback criteria.
Verification
- Acceptance criteria mapped to concrete tests or demo steps.
- Accessibility checks (linting, WCAG tools, platform inspectors) run for affected surfaces.
- Analytics/telemetry schemas reviewed with stakeholders; events verified in staging/testnet before release.
Related Skills
tjboudreaux/tools-debugging-root-cause
tools
VerifiedTrustedCommunity
Systematic debugging playbook for tracing failures backward through the call chain, adding instrumentation, and fixing bugs at their origin.
1SKILL.mdUpdated Apr 17, 2026
tjboudreaux/meta-superpowers
testing
VerifiedTrustedCommunity
Startup protocol for every task—discover applicable skills, run them, announce usage, and follow required workflows (brainstorming, TodoWrite checklists, etc.).
1SKILL.mdUpdated Apr 17, 2026
tjboudreaux/eng-verification
testing
VerifiedTrustedCommunity
Mandatory checklist before claiming work is complete—run the evidence-producing command, inspect output, and only then state a result.
1SKILL.mdUpdated Apr 17, 2026
tjboudreaux/eng-testing-anti-patterns
tools
VerifiedTrustedCommunity
Use when writing or modifying tests, adding mocks, or considering test-only hooks—prevents common mistakes like testing mocks, polluting production with test helpers, and mocking without understanding dependencies.
1SKILL.mdUpdated Apr 17, 2026