agentleFS
jhy0285jhy0285/monofield/skills/swiss-user-research-video-template/SKILL.md

swiss-user-research-video-template

Skill6 starsChanged 6 months agoApache-2.0View on GitHub

Swiss-style user-research narrative template in warm-paper editorial aesthetics. Use when users ask for a premium research deck or story-first live artifact with minimalist typography, high-clarity layout, subtle motion, donut breakdowns, and keyboard/click navigation across slides in a single HTML file.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read DESIGN.md, then map tokens to the template CSS variables (--paper, --ink, --muted, rule colors, segment colors) without changing …

    line 58
  2. Very specific:

    Start from assets/template.html.

    line 59
  3. Distinctive:

    Keep all data realistic and internally consistent between copy, donut labels, and percentages.

    line 68
  4. Distinctive:

    Keep HTML self-contained (inline CSS/JS), with no external framework dependencies.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swiss User Research Video Template

A premium Swiss-editorial user research template for narrative-heavy live artifacts. The visual language is warm paper, strict spacing rhythm, thin rules, and restrained micro-interactions that keep attention on the story.

Resource map

swiss-user-research-video-template/
├── SKILL.md
├── assets/
│   └── template.html
├── references/
│   └── checklist.md
└── example.html

Workflow

  1. Read DESIGN.md, then map tokens to the template CSS variables (--paper, --ink, --muted, rule colors, segment colors) without changing layout semantics.
  2. Start from assets/template.html; keep the three-slide structure:
    • title / framing
    • participant breakdown donut
    • behavioral pattern + evidence panel
  3. Preserve interactions:
    • click/keyboard slide navigation (ArrowLeft/ArrowRight)
    • bottom pagination dots with active state
    • donut legend hover highlight
    • subtle line-draw and panel-lift transitions
  4. Keep all data realistic and internally consistent between copy, donut labels, and percentages.
  5. Keep HTML self-contained (inline CSS/JS), with no external framework dependencies.
  6. Validate using references/checklist.md before output.

Output contract

Emit one concise orientation sentence and then a single HTML artifact:

<artifact identifier="swiss-user-research-deck" type="text/html" title="Swiss User Research Synthesis">
<!doctype html>
<html>...</html>
</artifact>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.