railway-ui-skills
Railway's UI design system. Use when building interfaces inspired by Railway's aesthetic - dark mode, Inter font, 4px grid.
75
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/railway/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is concise and clearly scoped to Railway's specific design system, with an explicit 'Use when' clause that aids skill selection. Its main weakness is the lack of concrete actions—it describes the aesthetic but not what the skill actually does (e.g., generate components, apply styles, create layouts). Adding specific capabilities would strengthen it significantly.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates UI components, applies theme styles, and creates layouts following Railway's design system.'
Include additional natural trigger terms users might say, such as 'UI components', 'theme', 'design tokens', 'styling', or 'Railway-style interface'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific elements (dark mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'style layouts', or 'generate theme tokens'. | 2 / 3 |
Completeness | Answers both 'what' (Railway's UI design system) and 'when' explicitly ('Use when building interfaces inspired by Railway's aesthetic - dark mode, Inter font, 4px grid'), with clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Railway', 'dark mode', 'Inter font', and '4px grid' which are somewhat relevant, but misses common user terms like 'UI components', 'design tokens', 'theme', 'styling', or 'Railway-style'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Railway' as a brand, combined with concrete design details (Inter font, 4px grid, dark mode), creates a clear niche that is unlikely to conflict with generic UI or other design system skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%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 design system reference with clear constraint language (MUST/SHOULD/NEVER) and useful token tables. Its main weaknesses are the lack of executable code examples showing how to apply these design tokens in practice, and some verbose reference data that could be moved to supplementary files. The content would benefit from at least one concrete implementation example (e.g., a Tailwind config or CSS custom properties block).
Suggestions
Add at least one executable code example, such as a Tailwind CSS config or CSS custom properties block that implements the design tokens, making the skill copy-paste actionable.
Move the detailed text styles table (10+ rows) and detected layout patterns into a separate REFERENCE.md file, keeping only the 2-3 most important styles inline.
Remove low-value data like the 'Count' column in text styles and the redundant 'Typography Reference' section that repeats information already conveyed in the table above it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundant data (e.g., listing 10+ text styles with individual counts of '1', detected layout patterns with raw pixel dimensions, and the 'Typography Reference' section repeating what's already in the table). The 'Count' column in text styles adds no value. | 2 / 3 |
Actionability | Provides concrete design tokens, specific hex values, and clear constraints (MUST/SHOULD/NEVER), which is good. However, it lacks executable code examples - no CSS/Tailwind snippets, no component code, no copy-paste-ready implementations. For a UI design system skill, at least one concrete code example showing how to apply these tokens would significantly improve actionability. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow skill. The single-purpose nature (apply these design constraints when building Railway-style UIs) is unambiguous. The MUST/SHOULD/NEVER hierarchy provides clear priority ordering, and the 'When to Apply' section clearly scopes usage. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and tables, but it's a fairly long monolithic document. Some sections like the full text styles table (10 rows) and detected layout patterns could be split into a reference file, with the SKILL.md retaining only the most critical tokens and constraints. | 2 / 3 |
Total | 9 / 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
- ihlamury/design-skills
- Commit
126714e
- 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.