jenkins-ui

Create Jenkins configuration pages using Jelly templates and Design Library components.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/aneveux/claude-garden --skill jenkins-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jenkins-ui
Source: https://github.com/aneveux/claude-garden/tree/main/plugins/graft/skills/jenkins-ui
Command: npx skills add https://github.com/aneveux/claude-garden --skill jenkins-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jenkins UI development can be error-prone and inconsistent across projects; this skill provides a structured approach to building Jenkins frontend components using Jelly templates and the Design Library, ensuring consistent UI patterns and reliable form behavior.

Core Features & Use Cases

  • Jelly-based UI: Create Jenkins configuration pages and UI views using Jelly templating with proper security (XSS protection) and Staples form controls.
  • Design Library integration: Apply Design Library components and CSS conventions to ensure consistent styling and behavior across Jenkins pages.
  • Reference patterns: Follow documented patterns for Jelly files, form bindings, and dialog interactions, including config.jelly and help files.

Quick Start

Create a Jenkins config page by implementing a Jelly config.jelly that leverages the Design Library components.

Frequently Asked Questions about jenkins-ui

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

FAQPage Schema
How do I create a Jenkins configuration page using Jelly templates?

To create a Jenkins configuration page with Jelly templates, you implement a config.jelly file that leverages Jenkins Design Library components and Staples form controls for consistent UI and reliable form behavior.

How does Jenkins Design Library integration work with Jelly views?

Jenkins Design Library integration works by applying its CSS conventions and UI components directly within Jelly templates, ensuring consistent styling and reliable form behavior across all Jenkins configuration pages and views.

How do I ensure XSS protection in Jenkins UI components?

To ensure XSS protection in Jenkins UI components, you follow structured Jelly template patterns and utilize Staples form controls, which enforce proper security boundaries within your Jenkins configuration pages.

What is the best way to build Jenkins frontend dialogs and help files?

The best way to build Jenkins frontend dialogs and help files is by following documented Jelly patterns and Dialog APIs, integrating Design Library components to maintain consistent styling and behavior across views.

Can I use standard CSS patterns with Jenkins Jelly templates?

Yes, you can use standard CSS patterns with Jenkins Jelly templates by applying the Jenkins Design Library conventions, ensuring that your UI components remain consistently styled and reliably bound to Staples form controls.

Why are my Jenkins form controls behaving inconsistently across views?

Jenkins form controls behave inconsistently across views when developers bypass the Design Library CSS conventions and documented Jelly patterns, which provide the structured approach needed for reliable form binding.