pajamas
GitLab Pajamas Design System expert for building UIs with Pajamas components and patterns. Use when: (1) implementing UI that should follow GitLab's Pajamas design system, (2) selecting or configuring Pajamas/GlComponent components (GlButton, GlAlert, GlModal, etc.), (3) translating Figma designs into Pajamas-compliant code, (4) questions about Pajamas component usage, variants, categories, or accessibility, (5) building GitLab-style interfaces, or (6) the user mentions "Pajamas", "GitLab UI", "Gl components", or "design system" in a GitLab context. Works hand-in-hand with the implement-design skill and Figma MCP tools.
75
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its domain (GitLab Pajamas Design System), lists specific concrete capabilities, and provides comprehensive trigger guidance through a well-structured numbered 'Use when' clause. The inclusion of specific component names, file format references (Figma), and explicit mention of related skills makes it both highly discoverable and clearly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implementing UI with Pajamas components, selecting/configuring GlComponent components (with named examples like GlButton, GlAlert, GlModal), translating Figma designs into Pajamas-compliant code, and answering questions about component usage, variants, categories, and accessibility. | 3 / 3 |
Completeness | Clearly answers both 'what' (building UIs with Pajamas components, selecting/configuring components, translating Figma designs, answering component questions) and 'when' with an explicit numbered 'Use when' clause covering six distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'Pajamas', 'GitLab UI', 'Gl components', 'design system', specific component names (GlButton, GlAlert, GlModal), 'Figma designs', 'Pajamas-compliant', and 'GitLab-style interfaces'. These are terms a developer working in the GitLab ecosystem would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: GitLab's Pajamas design system. The specific component naming convention (Gl-prefixed components), the Pajamas brand name, and the GitLab context make it very unlikely to conflict with generic UI or design system skills. It also explicitly notes its relationship with the implement-design skill, reducing ambiguity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill that serves as an effective hub for Pajamas Design System implementation. Its greatest strengths are the clear multi-step workflows with validation, comprehensive component/pattern lookup tables with exact file references, and strong progressive disclosure to bundled reference files. The main weakness is moderate verbosity — the design token rules are emphasized repeatedly with many NEVER statements, and some sections could be more concise without losing clarity.
Suggestions
Consolidate the design token rules into a single concise section rather than repeating the 'NEVER use absolute values' message multiple times with extensive examples — the point is made effectively once.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~250 lines) with some redundancy — the design token rules are repeated/emphasized multiple times, and the component selection guide table is extensive. However, most content is reference material (tables, file paths) that earns its place. Some sections like 'Integration with Figma and implement-design' could be tighter, and the repeated 'NEVER' emphasis is verbose. | 2 / 3 |
Actionability | The skill provides concrete, executable commands (bash scripts, npm commands), specific import statements, exact CSS variable names, clear file paths to reference, and detailed lookup workflows. The component tables with exact import names and SSoT file paths are highly actionable and copy-paste ready. | 3 / 3 |
Workflow Clarity | Multiple workflows are clearly sequenced: initialization (3 ordered commands), component lookup (5-step prioritized chain with fallback), token resolution (4-step process with priority order), project scaffolding (3 steps with verification), and Figma integration (clear step references). Validation checkpoints are present — 'Do not skip this step', 'Only after exhausting all five steps', 'Verify after install'. | 3 / 3 |
Progressive Disclosure | The skill is structured as an overview that consistently points to one-level-deep reference files (component-index.md, token-map.md, tokens.css, various SSoT docs). Tables map needs to specific reference file paths. The reference architecture (references/pajamas-docs/, references/design-tokens/) is well-organized with clear navigation signals throughout. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- gitlabhq/orbit-knowledge-graph
- Commit
f5efc36
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.