frontend-classification

Classify software development tickets as frontend or UI work.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/matteobortolazzo/cenci --skill frontend-classification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-classification
Source: https://github.com/matteobortolazzo/cenci/tree/main/flow/skills/frontend-classification
Command: npx skills add https://github.com/matteobortolazzo/cenci --skill frontend-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in project management by providing a standardized, automated way to determine if a task involves frontend or UI work, ensuring the correct design-aware workflows are applied.

Core Features & Use Cases

  • Automated Classification: Scans ticket titles, descriptions, and acceptance criteria for UI-related keywords.
  • Visual Verification Logic: Identifies tasks that require interactive browser testing or visual checks.
  • Use Case: When an agent is planning a new ticket, it uses this skill to decide whether to trigger design-aware refinement or UI-specific testing protocols.

Quick Start

Ask the system to classify the current ticket to determine if it requires frontend-specific design and testing workflows.

Frequently Asked Questions about frontend-classification

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

FAQPage Schema
How do I automatically classify frontend tasks in software development workflows?

Automated frontend task classification scans ticket titles, descriptions, and acceptance criteria for UI-related keywords to determine if a task requires frontend design and testing workflows. This standardizes project management by eliminating ambiguity in distinguishing frontend work from backend or infrastructure tasks.

What is the best way to identify UI work from ticket metadata for automated routing?

Identifying UI work from ticket metadata involves semantic analysis of ticket content to apply a centralized rule-set. This ensures consistent workflow routing for design-aware planning, visual verification, and UI testing based on the presence of specific frontend-related indicators.

Does automated workflow routing support visual verification logic for UI testing?

Automated workflow routing supports visual verification logic by identifying tasks that require interactive browser testing or visual checks. When an agent classifies a ticket, it decides whether to trigger UI-specific testing protocols for design-aware refinement.

Can I use semantic analysis to separate frontend tickets from backend development work?

Semantic analysis separates frontend tickets from backend development work by applying a consistent rule-set to ticket metadata. This standardized approach ensures correct design-aware workflows are triggered exclusively for tasks involving UI work.

When do I need a centralized rule-set for distinguishing frontend tasks?

A centralized rule-set for distinguishing frontend tasks is needed when automating project management workflows to ensure consistent routing. It provides a standardized method to determine if a task involves UI work, triggering appropriate design-aware refinement and visual verification protocols.