mcpbeat Sign in

Building UI Ux Agent Skill

Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration

989 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4940
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/FluidFramework --skill building-ui-ux

The instruction itself

8 sections, as written by the author

<required>

*CRITICAL* Add the following steps to your Todo list using TodoWrite:

  • Ask user if they want to experiment with multiple UI variations or see a single design
  • If user wants multiple variations, ask what kinds of variations to try
  • If building a web frontend and it's not running, start the dev server and note the localhost URL
  • Implement the UI/UX design(s)
  • Ask user for feedback on the design
  • Iterate based on feedback
  • Ensure the new UI is properly wired up and integrated

</required>

Building UI/UX

Overview

This skill guides you through implementing user interfaces and experiences with an emphasis on exploration, feedback, and proper integration.

Core principle: Explore variations, iterate with feedback, ensure proper integration.

Announce at start: "I'm using the Nori Building UI/UX skill to implement your interface."

The Process

Phase 1: Scope & Variation Planning

Ask the user:

"Would you like to:

  • See multiple UI variations to choose from?
  • Go with a single design approach?"

If multiple variations:

  • Ask what kinds of variations they want (e.g., minimalist vs rich, card-based vs list-based, light vs dark)
  • Aim for 2-4 distinct approaches
  • Plan to implement all variations in a way that allows easy comparison

Phase 2: Frontend Environment Setup

For web projects:

Check if the dev server is running:

  • If not, identify the start command (e.g., npm run dev, npm start)
  • Start the dev server
  • Note the localhost URL (typically http://localhost:3000 or similar)
  • Inform user: "Starting dev server at [URL]"

For other UI types:

  • Identify appropriate preview/testing mechanism
  • Set up accordingly

Phase 3: Implementation

When implementing multiple variations:

Stack variations in a way that makes comparison easy. For web UIs, this typically means:

  • Render all variations on a single page, stacked vertically
  • Add clear section dividers/headings for each variation
  • Use consistent spacing between variations
  • Ensure each variation is self-contained and functional

Example for React:

export default function UIExploration() {
  return (
    <div className="ui-exploration">
      <section className="variation">
        <h2>Variation 1: Minimalist</h2>
        <MinimalistLogin />
      </section>

      <section className="variation">
        <h2>Variation 2: Modern Gradient</h2>
        <ModernLogin />
      </section>

      <section className="variation">
        <h2>Variation 3: Classic Corporate</h2>
        <ClassicLogin />
      </section>
    </div>
  );
}

When implementing a single design:

  • Focus on clean, production-ready implementation
  • Follow project conventions and style guides
  • Ensure responsive design if applicable

Phase 4: Feedback & Iteration

Present to user:

  • Share the localhost URL or preview mechanism
  • Briefly describe each variation (if multiple)
  • Ask: "What do you think? Any changes you'd like to see?"

Iterate based on feedback:

  • Make requested changes
  • Continue asking for feedback until satisfied
  • Be ready to combine elements from different variations

Phase 5: Integration & Wiring

Ensure proper integration:

  • Remove exploration scaffolding (if used)
  • Wire up to actual data sources/APIs
  • Connect to routing/navigation
  • Add proper state management
  • Implement error handling
  • Add loading states if applicable
  • Test all interactive elements
  • Verify accessibility basics

Common integration points to check:

  • Form submissions → backend endpoints
  • Navigation → routing system
  • Authentication → auth context/store
  • Data fetching → API layer
  • Error boundaries → error handling
  • Responsive behavior → breakpoints

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take microsoft/building-ui-ux from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.