Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "building-ui-ux" 技能: 1. 下载 https://raw.githubusercontent.com/microsoft/FluidFramework/main/.agency/plugins/nori/skills/building-ui-ux/SKILL.md 2. 保存为 ~/.claude/skills/building-ui-ux/SKILL.md 3. 装好后重载技能,告诉我可以用了
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."
Ask the user:
"Would you like to:
If multiple variations:
For web projects:
Check if the dev server is running:
npm run dev, npm start)http://localhost:3000 or similar)For other UI types:
When implementing multiple variations:
Stack variations in a way that makes comparison easy. For web UIs, this typically means:
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:
Present to user:
Iterate based on feedback:
Ensure proper integration:
Common integration points to check:
Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
Generate the OCE shift status dashboard. Triggers on: 'generate shift dashboard', 'show dashboard', 'shift status', 'status dashboard', 'what's going on', or any request for a NON-SPECIFIC overview of current OCE status (incidents, pipelines, errors).