- Skills
- 14
- 仓库
- 1
- 职业覆盖
- 1
- 场景覆盖
- 2
- Stars
- ★ 1
Ben Kanagroo 的 Skills 14
ux-principles
ScribeFloat UX principles and design intent. Use when designing or reviewing any new screen, component, interaction pattern, or user flow — or when you need to understand WHY a design rule exists, not just what it is. Complements ui-enforcement (which governs tokens and class names).
ui-taxonomy
Classify UI work into the correct taxonomy level before building. Use when creating a new UI element, naming a component, deciding where something belongs in the system, or when another skill needs a shared vocabulary for UI structure.
ui-enforcement
Enforces ScribeFloat UI consistency — typography role classes, design tokens, and component primitives. Use when writing or editing Svelte/CSS frontend code, Tailwind classes, forms, labels, screens, onboarding, or when the user mentions design system, typography pass, sf-* classes, scroll layout, chrome/body panes, or UI consistency.
design-skill
暂无简介
ux-principles
ScribeFloat UX principles and design intent. Use when designing or reviewing any new screen, component, interaction pattern, or user flow — or when you need to understand WHY a design rule exists, not just what it is. Complements ui-enforcement (which governs tokens and class names).
ui-taxonomy
Classify UI work into the correct taxonomy level before building. Use when creating a new UI element, naming a component, deciding where something belongs in the system, or when another skill needs a shared vocabulary for UI structure.
ui-enforcement
Enforces ScribeFloat UI consistency — typography role classes, design tokens, and component primitives. Use when writing or editing Svelte/CSS frontend code, Tailwind classes, forms, labels, screens, onboarding, or when the user mentions design system, typography pass, sf-* classes, scroll layout, chrome/body panes, or UI consistency.
design-skill
Understand how to design consistent user interfaces in scribefloat. Use when asked to work on the frontend or any code that might affect how users interact with the system.
commit-curator
Safely split, rewrite, explain, or review git commits. Use when asked to commit uncommitted work, split changes, propose commit messages, clean up messy local commits, or curate a branch. ALWAYS present a commit plan and wait for user approval before running git add/commit — even when the user says "commit".
ux-principles
ScribeFloat UX principles and design intent. Use when designing or reviewing any new screen, component, interaction pattern, or user flow — or when you need to understand WHY a design rule exists, not just what it is. Complements ui-enforcement (which governs tokens and class names).
ui-taxonomy
Classify UI work into the correct taxonomy level before building. Use when creating a new UI element, naming a component, deciding where something belongs in the system, or when another skill needs a shared vocabulary for UI structure.
ui-enforcement
Enforces ScribeFloat UI consistency — typography role classes, design tokens, and component primitives. Use when writing or editing Svelte/CSS frontend code, Tailwind classes, forms, labels, screens, onboarding, or when the user mentions design system, typography pass, sf-* classes, scroll layout, chrome/body panes, or UI consistency.
design-skill
Understand how to design consistent user interfaces in scribefloat. Use when asked to work on the frontend or any code that might affect how users interact with the system.
commit-curator
Safely split, rewrite, explain, or review git commits. Use when asked to commit uncommitted work, split changes, propose commit messages, clean up messy local commits, or curate a branch. ALWAYS present a commit plan and wait for user approval before running git add/commit — even when the user says "commit".