frontend-patterns

Frontend patterns for Rails applications using Slim templates, Stimulus JavaScript framework, CSS with Optics utilities. Use when building views, adding interactivity, styling components, or when the user mentions Slim, Stimulus, JavaScript, CSS, or frontend development.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/frontend-patterns/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable frontend patterns reference with verified external examples and clean sectioning. Its main gaps are the absence of explicit validation checkpoints for destructive/batch patterns and a body that is somewhat long for an overview.

Suggestions

Add a brief validation/verification note to the bulk-action and delete patterns (e.g., confirm selection count and re-render the list after the batch request succeeds) to raise workflow clarity above 3.

Trim inline code blocks that duplicate what references/EXAMPLES.md already covers, keeping the SKILL.md body as a lean overview with signaled pointers.

Remove redundant intro sentences like 'JavaScript interactions using Stimulus framework.' that restate the section heading.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable patterns and tables that assume Rails/Slim competence, with only minor redundant intros like 'JavaScript interactions using Stimulus framework.' that could be trimmed. Not a 5 because a few explanatory lines restate what the code already shows.	4 / 5
Actionability	It provides fully executable, copy-paste-ready Slim and Stimulus code plus concrete input-type and option tables covering the common frontend cases. The examples are complete rather than pseudocode.	5 / 5
Workflow Clarity	This is a patterns catalog rather than a sequenced workflow, and it presents batch/destructive patterns (bulk action form, delete buttons) without explicit validation or verification checkpoints. Not a 4 because no clear sequence with checkpoints is present, and not a 2 because structure and the turbo_confirm pattern show some awareness of safety.	3 / 5
Progressive Disclosure	Clear section structure with one-level-deep references to the real references/EXAMPLES.md signaled three times, and detailed examples correctly live in that file. Not a 5 because the ~245-line body still inlines substantial code that could be pushed to the reference for a leaner overview.	4 / 5
	Total	16 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly covers both capability and trigger conditions in third person, with a clear Rails-frontend niche. Its only weakness is that the stated actions are somewhat generic rather than concretely enumerated.

Dimension	Reasoning	Score
Specificity	Names the domain and tech stack ('Frontend patterns for Rails applications using Slim templates, Stimulus JavaScript framework, CSS with Optics utilities') and a couple of actions ('building views, adding interactivity, styling components'), but the actions remain generic rather than comprehensive. It does not reach 4 because no multiple specific concrete actions are enumerated.	3 / 5
Completeness	It clearly states what it does (frontend patterns for Rails with Slim, Stimulus, Optics) and explicitly gives a 'Use when' clause with concrete trigger phrases. This matches the anchor that answers both what and when with concrete triggers.	5 / 5
Trigger Term Quality	The 'Use when ... the user mentions Slim, Stimulus, JavaScript, CSS, or frontend development' clause gives good natural keyword coverage users would actually say. Not a 5 because common synonyms and file extensions (e.g. .slim, .css files) are absent.	4 / 5
Distinctiveness Conflict Risk	The Slim + Stimulus + Optics on Rails niche is specific with distinct triggers, minimizing overlap with other skills. Conflict risk is minimal.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: RoleModel/rolemodel-skills
Path: skills/frontend-patterns/SKILL.md
Commit: 6d600e9

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.