fab-actions

Provides a fixed, expandable Save/Cancel action group for long forms.

1|Updated Mar 19, 2024
One-click install
npx skills add https://github.com/doitsu2014/my-cms --skill fab-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fab-actions
Source: https://github.com/doitsu2014/my-cms/tree/main/frontend/.claude/skills/fab-actions
Command: npx skills add https://github.com/doitsu2014/my-cms --skill fab-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a fixed, accessible set of form actions (Save/Cancel) that remain visible as users scroll long forms.

Core Features & Use Cases

  • Fixed bottom-right position for constant visibility
  • Expandable action group with smooth transitions
  • Plus icon rotates to indicate open state
  • Keyboard accessible buttons with proper semantics

Quick Start

Install and place the FAB component at the end of your form. Import the required icons and toggle state to open/close. Bind the Save action to the form submission and the Cancel action to navigation.

Frequently Asked Questions about fab-actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep form actions accessible when scrolling long forms?

To keep form actions accessible during scroll, use a fixed position floating action button (FAB) that stays visible. An expandable FAB provides Save and Cancel buttons that remain constantly accessible without intruding on the form content.

What is the best UI pattern for fixed Save and Cancel buttons on data-entry screens?

The best UI pattern for fixed Save and Cancel buttons is an expandable floating action button. It anchors to the bottom-right for constant visibility, uses a rotating plus icon to indicate state, and expands to reveal semantic action buttons.

Can I build a keyboard accessible floating action button in React without dependencies?

Yes, you can build a keyboard accessible floating action button in React with zero dependencies. The pattern relies on semantic button elements and proper toggle state management to ensure keyboard users can open and trigger actions.

How do I implement an expandable FAB with smooth transitions for content-management interfaces?

To implement an expandable FAB for content-management interfaces, place the component at the end of your form, import the required icons, and manage the toggle state to open and close the action group with smooth transitions.

Why does my fixed form action button obscure inputs on administrative UIs?

A fixed form action button obscures inputs when it lacks an expandable design that minimizes its footprint. Using a collapsed FAB that only expands upon user interaction prevents it from permanently covering form fields.