fe

Plan frontend implementation for VegaExchange trading UI issues.

1|Updated Mar 28, 2025
One-click install
npx skills add https://github.com/davidting0918/VegaExchange --skill fe-davidting0918
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fe
Source: https://github.com/davidting0918/VegaExchange/tree/main/.claude/skills/fe
Command: npx skills add https://github.com/davidting0918/VegaExchange --skill fe-davidting0918

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VegaExchange frontend project planning often involves misalignment between business goals and UI implementation. This Skill provides a structured approach to defining roles, tasks, and workflows for frontend features, ensuring clear expectations and repeatable processes.

Core Features & Use Cases

  • Facilitates issue-driven frontend implementation planning, including design plans, component breakdowns, state management, routes, and UI patterns.
  • Guides Technical Discussion with structured analysis templates, alternative approaches, and decision records.
  • Provides a repeatable Quick Start workflow to kick off frontend tasks quickly and consistently.

Quick Start

Invoke /fe with issue numbers or discuss topic to begin the implementation guidance flow.

Frequently Asked Questions about fe

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

FAQPage Schema
How do I plan frontend implementation for trading UI features?

Structure technical discussions for React UI components using analysis templates, alternative approaches, and decision records. This framework provides concrete implementation plans and copy-ready documentation to support reliable handoffs.

How do I structure technical discussions for React UI components?

Structure technical discussions for React UI components using analysis templates, alternative approaches, and decision records. This framework provides concrete implementation plans and copy-ready documentation to support reliable handoffs.

What's the best way to break down state management and routing for trading platform UI?

Yes, you can use TypeScript planning workflows for issue-driven frontend development by invoking the skill with issue numbers or discussion topics. It generates structured implementation guidance and repeatable quick start workflows.

Can I use TypeScript planning workflows for issue-driven frontend development?

Yes, you can use TypeScript planning workflows for issue-driven frontend development by invoking the skill with issue numbers or discussion topics. It generates structured implementation guidance and repeatable quick start workflows.

Why does frontend project planning misalign with business goals in trading UI development?

Frontend project planning misaligns with business goals in trading UI development due to unstructured workflows. Applying a structured approach to defining roles, tasks, and UI patterns ensures clear expectations and repeatable processes.

Do I need specific issue numbers to start frontend workflow planning?

No, you do not need specific issue numbers to start frontend workflow planning. You can invoke the skill with a discussion topic to begin the implementation guidance flow and generate structured technical analysis.