viewcomponent-patterns
Creates ViewComponents for reusable UI elements with TDD. Use when building reusable UI components, extracting complex partials, creating cards/tables/badges/modals, or when user mentions ViewComponent, components, or reusable UI.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill viewcomponent-patterns90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 a well-crafted skill description that excels across all dimensions. It clearly specifies the capability (ViewComponents with TDD), provides concrete examples of use cases (cards, tables, badges, modals), and includes explicit trigger guidance with natural keywords developers would use. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates ViewComponents', 'reusable UI elements', 'TDD', 'extracting complex partials', 'creating cards/tables/badges/modals'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Creates ViewComponents for reusable UI elements with TDD') and when ('Use when building reusable UI components, extracting complex partials, creating cards/tables/badges/modals, or when user mentions ViewComponent, components, or reusable UI'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ViewComponent', 'components', 'reusable UI', 'partials', 'cards', 'tables', 'badges', 'modals'. These are terms developers naturally use when discussing UI components. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Rails ViewComponent specifically with distinct triggers like 'ViewComponent', 'partials', and specific UI element types. Unlikely to conflict with general UI or frontend skills due to the Rails/ViewComponent specificity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent executable code examples covering multiple ViewComponent patterns. The TDD workflow is clear and the testing examples are comprehensive. Main weaknesses are the slightly verbose overview section and the monolithic structure that could benefit from splitting into separate pattern files.
Suggestions
Remove or significantly trim the Overview section - Claude already knows what ViewComponents are and their benefits
Consider splitting the 5 patterns into separate files (e.g., patterns/badge.md, patterns/modal.md) with SKILL.md as an index pointing to them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary content like the Overview section explaining what ViewComponents are (Claude knows this) and could be tightened in places like the verbose project structure section. | 2 / 3 |
Actionability | Excellent executable code throughout - complete Ruby classes, ERB templates, RSpec tests, and bash commands that are copy-paste ready. Every pattern includes working implementation code. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit steps (RED -> GREEN), numbered progression, and a checklist at the end. The workflow is well-sequenced with validation through running specs. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting patterns into separate files. No external references are provided for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.