agentleFS
Sign inStart free
hidenobunagaihidenobunagai/astack/skills/principle-experience-first/SKILL.md

principle-experience-first

Skill1 starsChanged 11 days agoMITView on GitHub

Apply when deliverable shape comes up: which charts to include, what a dashboard shows first, how a report is organized, or how much detail a notebook shows. Choose what the reader of the chart, report, or dashboard can act on over implementation convenience, and ship fewer, clearer views.

45 other projects use a version of this, 43 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, poteto-help and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 19 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 11 projects that use this

  • JoshueOsunaSkill

    Poteto Mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

    Also in 3 projects that use this

  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 18 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When implementation convenience conflicts with the reader's understanding, choose the reader.

    line 8
  2. Distinctive:

    Every chart, table, KPI tile, and filter must justify itself by the decision it supports.

    line 10
  3. Distinctive:

    Check accessibility. Contrast must meet 4.5:1 for text, and color must never be the only carrier of meaning.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 34 edited versions of this file we could read. “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

Experience First

When implementation convenience conflicts with the reader's understanding, choose the reader.

  • Every chart, table, KPI tile, and filter must justify itself by the decision it supports.
  • Ship less, ship better. Three views that answer the question beat ten that do not.
  • Prototype before committing. A rough plot or a throwaway notebook cell is cheaper to change than a scheduled dashboard.
  • Get the details right: axis labels with units, a sort order that matches the message, the time window in the title, a visible note on missing data, and a clear empty state. Use the dataviz skill for chart design.
  • Check accessibility. Contrast must meet 4.5:1 for text, and color must never be the only carrier of meaning. The visualization playbook in the analyst-mode skill has the full checklist.
  • Tighten the core loop. Every view should serve the question the analysis set out to answer (see principle-define-the-question) or get out of the way.

The user is whoever consumes the work. For a dashboard that is the stakeholder who reads it. For a notebook it is the colleague who reruns it, and the engineer who maintains the pipeline next. Weigh their experience the same way, and explain impact from their perspective.

Foundations should serve the experience. Foundational thinking governs the sequence of work. This principle governs the target.

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.

Check your setup, free