prism

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

PRISM — People Research & Insight System for Makers. Two modules in one skill: (1) UX Research — generates professional personas, journey maps, interview synthesis reports, and usability test plans grounded in industry-standard research methodology. (2) UI Design — generates design philosophies, component specifications, design token systems, layout systems, interaction specs, and visual canvas artifacts. Accepts raw interview notes, survey data, analytics, product briefs, brand guidelines, or competitor screenshots as input. Includes an optional financial services layer for trust, compliance, and regulatory UX considerations across both modules. MANDATORY TRIGGERS: persona, user persona, journey map, customer journey, interview synthesis, usability test plan, UX research, user research, research plan, empathy map, user interview, affinity mapping, research findings, user insights, pain points analysis, research report, UI design, design system, component library, style guide, design tokens, color palette, typography system, layout grid, visual design, interface design, design spec, design philosophy, wireframe, visual hierarchy, design language, UI kit, brand identity, canvas design, design artifact, visual specification, component spec, interaction design, PRISM. Also trigger when someone describes a product and asks for research artifacts, design direction, component specs, or design system foundations, or when they paste raw interview notes.

26installs

Sourceravipalwe/prism

Added on2026-09-04

NPX Install

npx skill4agent add ravipalwe/prism prism

SKILL.md Content

View Translation Comparison →

PRISM — People Research & Insight System for Makers

Two modules. One skill. From research insight to design specification.

Module 1: UX Research

Generate research-grade deliverables — personas, journey maps, interview synthesis, and usability test plans. Every output should be something a senior UX researcher would be comfortable presenting to stakeholders.

Module 2: UI Design

Generate professional design deliverables — design philosophies, component specs, design tokens, layout systems, interaction specs, and visual canvas artifacts. Every output should look like it came from a senior product designer who obsesses over craft.

Pipeline Overview

User Input → Identify Module → Identify Deliverable → Classify Input → Generate → Quality Check → Output

Step 1: Identify the Module & Deliverable

UX Research Deliverables

If the user wants to understand...	Generate
Who their users are	Personas — see `references/PERSONA-GUIDE.md`
What users experience across touchpoints	Journey Map — see `references/JOURNEY-MAP-GUIDE.md`
Patterns in raw research data	Interview Synthesis — see `references/SYNTHESIS-GUIDE.md`
How to test an experience	Usability Test Plan — see `references/TEST-PLAN-GUIDE.md`

UI Design Deliverables

If the user wants to define...	Generate
Visual direction for a product	Design Philosophy — see `references/PHILOSOPHY-GUIDE.md`
Component patterns for an interface	Component Spec — see `references/COMPONENT-GUIDE.md`
Color, type, spacing foundations	Design Tokens — see `references/TOKEN-GUIDE.md`
Page structure & layout logic	Layout System — see `references/LAYOUT-GUIDE.md`
Interaction & motion behavior	Interaction Spec — see `references/INTERACTION-GUIDE.md`
Visual artifact (poster, infographic, PDF)	Canvas Artifact — see `references/CANVAS-GUIDE.md`

If the request is ambiguous, ask the user.

Research order (each builds on the previous): Interview Synthesis → Personas → Journey Maps → Usability Test Plans.

Design order (each builds on the previous): Design Philosophy → Design Tokens → Layout System → Component Spec → Interaction Spec.

Cross-module flow: Research deliverables feed design deliverables. Personas → emotional targets. Journey maps → key moments for state design. Synthesis → pain point to design solution mapping.

Step 2: Classify Input Fidelity

Input type	Approach
Raw interview notes / transcripts	Synthesize — find patterns, surface insights, use direct quotes. Never invent data.
Survey data	Identify quantitative trends, pull qualitative verbatims, note sample sizes.
Analytics / metrics	Ground personas and journeys in real usage patterns.
Existing brand guidelines / style guide	Extend — build on what exists, don't contradict it.
Product screenshots / competitor references	Analyze — extract patterns, identify gaps, propose improvements.
PRISM research artifacts	Ground — connect every design choice to a user need.
Brief / description only	Generate a well-reasoned draft, but label every assumption: "Assumption — validate with research."

Step 3: Generate the Deliverable

Read the relevant reference guide and follow its template exactly. Each guide contains the methodology, the output template, guidelines, and examples.

For UI Design deliverables: Always establish a design philosophy first (see

references/PHILOSOPHY-GUIDE.md

). Every design system needs a soul before it has rules.

Step 4: Financial Services Layer (Optional)

Activate when the user mentions financial products, banking, payments, insurance, wealth management, lending, or regulatory compliance — or when they explicitly ask for it.

For Research deliverables: Read
```
references/FINSERV-LAYER.md
```
For Design deliverables: Read
```
references/FINSERV-UI-LAYER.md
```

Step 5: Quality Check

Before delivering, verify against

references/QUALITY-CHECKLIST.md

. Every deliverable must pass all checks.

Step 6: Output

Save all deliverables as Markdown (.md) files:

Research outputs:

```
personas.md
```
```
journey-map-[persona-name].md
```
```
interview-synthesis.md
```
```
usability-test-plan.md
```

Design outputs:

```
design-philosophy.md
```
```
design-tokens.md
```
```
component-spec-[name].md
```
```
layout-system.md
```
```
interaction-spec.md
```

When visual canvas artifacts are requested, also output as

.pdf

or

.png

.

Key Principles

These apply to every deliverable this skill generates:

Research over opinion. When real data exists, use it. When it doesn't, say so clearly.
Synthesis over summary. Find patterns across data points — don't recap individual interviews.
Actionable over descriptive. Every section should connect to a design decision or recommendation.
Specific over generic. If a persona, journey, finding, or component could apply to any product, it's too vague.
Transparent over polished. Label assumptions, flag gaps, rate evidence strength. Stakeholders need to know what's proven and what's hypothesized.
Philosophy before pixels. Every design system needs a reason to exist. Establish the "why" before the "what."
Craft over templates. Design output must look meticulously crafted — painstaking attention, master-level execution.
Accessible by default. WCAG 2.2 AA minimum. Built into every spec, not bolted on after.
Buildable. Design specs must be precise enough that a developer can implement without guessing.