af-dev-ui

Convert GitHub issue descriptions into concrete Airflow UI development tasks.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/guan404ming/gmccc --skill af-dev-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-dev-ui
Source: https://github.com/guan404ming/gmccc/tree/main/skills/airflow/af-dev-ui
Command: npx skills add https://github.com/guan404ming/gmccc --skill af-dev-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating vague issue descriptions into actionable Airflow UI development tasks can be error-prone and slow down UI improvements.

Core Features & Use Cases

  • Issue-to-UI Translation: Convert a GitHub issue URL or plain text into concrete Airflow UI work items.
  • Reuse First: Leverage existing src/ components and layout conventions to minimize changes.
  • Validation & Collaboration: Document conventions and guide reviewers through the UI implementation process with clear examples.

Quick Start

Describe the desired Airflow UI feature by sharing a GitHub issue URL or a brief text description.

Frequently Asked Questions about af-dev-ui

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

FAQPage Schema
How do I convert GitHub issues into Airflow UI development tasks?

To convert GitHub issues into Airflow UI development tasks, provide the issue URL or text description. The Skill translates vague issue requirements into concrete UI work items while enforcing existing src component patterns.

How do I enforce existing component reuse when augmenting the Airflow UI?

Enforcing existing component reuse when augmenting the Airflow UI is handled by implementing workflow guidance in SKILL.md. It leverages existing layout conventions to minimize changes and document UI implementation patterns for reviewers.

Can I use plain text descriptions for Airflow UI ticket grooming?

Yes, you can use plain text descriptions for Airflow UI ticket grooming. The Skill accepts brief text descriptions alongside GitHub issue URLs to generate actionable UI development tasks for sprint work and project planning.

What is the best way to translate vague issue descriptions into actionable Airflow UI work items?

The best way to translate vague issue descriptions into actionable Airflow UI work items is using an issue-to-UI translation process. It converts raw issue inputs into structured development tasks that guide reviewers through the implementation process with clear examples.