Nexus iux neuro
Applies neuro-UX and behavioral science principles to reduce cognitive load, eliminate friction patterns, and design adaptive interfaces. Use when optimizing user flows for cognitive efficiency, analyzing behavioral patterns, or designing interfaces that adapt to user mental models.From its SKILL.md
npx -y skills add Shuwanito/SkillsMP --skill nexus-iux-neuroAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as proprietary. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, 191 tokens by cl100k_base, as published. Nobody here has run it
NeuroSense
Capabilities
- Neuro-UX analysis and cognitive load assessment
- Behavioral pattern detection and friction identification
- Cognitive load reduction strategies
- Adaptive interface design recommendations
- Frontend UX evaluation grounded in behavioral science
Workflow
- Analyze target application interfaces for cognitive load issues
- Map user behavioral patterns and identify friction points
- Apply neuro-UX principles to assess information architecture
- Design adaptive interface proposals that reduce cognitive overhead
- Validate recommendations against behavioral science research
- Produce UX improvement reports with cognitive load metrics
- Submit proposals for peer review
Guidelines
- Never modify target application code directly
- All proposals require peer review
- Ground all recommendations in behavioral science evidence
- Prioritize high-friction patterns that most impact user task completion
- Consider diverse user cognitive profiles and experience levels
- Avoid dark patterns -- optimize for user benefit, not engagement manipulation
What ships with it: 1 file
5.4 KB alongside SKILL.md
- evals.json5.4 KB
Gives 0 of the 12 instructions most design frontend skills give in 191 tokens
Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07
- Use CSS variables for color consistencyin 72 of 1169, across 23 files
- Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
- Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
- Add atmospheric background effects and texturesin 57 of 1169, across 9 files
- Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
- Implement real working codein 55 of 1169, across 7 files
- Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
- Launch chromium in headless modein 47 of 1169, across 4 files
- Close the browser when donein 47 of 1169, across 4 files
- Run provided scripts with help flag firstin 47 of 1169, across 4 files
- Wait for network idle statein 47 of 1169, across 4 files
- Use descriptive selectors for elementsin 47 of 1169, across 4 files
Said here and by no other author read
- Analyze interfaces for cognitive load issues
- Map user behavioral patterns and friction points
- Assess information architecture using neuro-UX principles
- Design adaptive interfaces reducing cognitive overhead
- Validate recommendations against behavioral science
- Produce reports including cognitive load metrics
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.