common-components-skill

Provides reusable UI components and token-based CSS themes for FileTerm Electron frontend development.

234|36|Updated May 15, 2026
One-click install
npx skills add https://github.com/St0ff3l/fileterm --skill common-components-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: common-components-skill
Source: https://github.com/St0ff3l/fileterm/tree/main/.agents/skills/common-components-skill
Command: npx skills add https://github.com/St0ff3l/fileterm --skill common-components-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent UI implementation, theme mismatch bugs, and duplicated component code in the FileTerm desktop remote workspace client, reducing maintenance overhead and ensuring a seamless user experience across light and dark modes and standalone windows.

Core Features & Use Cases

  • Standardized Common Components: Pre-built TerminalView, AppIcon, ContextMenu, and horizontal scroll utilities that enforce consistent interaction patterns across all FileTerm panels.
  • Unified CSS Theme System: Token-based design system with strict separation of structural and theme styles, light/dark theme support, and anti-flash mechanisms for standalone windows.
  • Use Case: When building a new SFTP file manager panel, use this Skill to implement consistent icons, right-click context menus, and automatic theme adaptation without rewriting core theme logic.

Quick Start

Use the common-components-skill to add a themed, right-click enabled file list with horizontal scroll support to the new SFTP transfer panel.

Frequently Asked Questions about common-components-skill

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

FAQPage Schema
How do I build consistent UI components for an Electron desktop client?

You can build consistent Electron desktop UI components by using a token-based CSS theme system with pre-built elements like TerminalView and ContextMenu. This enforces consistent interaction patterns and reduces duplicated code.

What is the best way to prevent theme flashing in standalone Electron windows?

The best way to prevent theme flashing in standalone Electron windows is to implement an anti-flash initialization mechanism using a token-based CSS theme system. This ensures the correct theme renders immediately on window load.

How do I separate structural CSS from theme styles in a frontend application?

You separate structural CSS from theme styles by adopting a token-based design system. This architecture strictly divides layout rules from visual properties, enabling automatic light and dark mode adaptation without code duplication.

How do I add a right-click context menu to a file list in an Electron app?

You add a right-click context menu to a file list by utilizing standardized pre-built ContextMenu components. This enforces consistent interaction patterns across all panels without rewriting core event logic.

Can I use a token-based theme system for both light and dark modes in a remote workspace client?

Yes, you can use a token-based theme system for both light and dark modes in a remote workspace client. The system automatically adapts visual properties across all panels while maintaining visual consistency.