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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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

The body is a lean, highly actionable patterns catalog with executable code and a well-signaled single reference file. Its only gap is workflow clarity: batch and destructive patterns (bulk actions, deletes) appear without validation or feedback-loop guidance.

Suggestions

Add a brief validation/feedback note to the bulk-action and delete patterns (e.g., confirm selection count, re-render or surface errors after submission) so batch/destructive operations include an explicit checkpoint.

Consider a short 'Build a feature' workflow sequence (form -> controller hook -> partial -> Stimulus) to give multi-step work a clear ordered path with verification, raising workflow clarity above the batch-op cap.

Dimension	Reasoning	Score
Conciseness	The body is code-first with brief rules and no padding about what Rails/Slim/Stimulus are ('Always use Simple Form. Never use form_with', 'Single element = helper. Structure/layout = partial'), assuming Claude's competence; only minor inline comments approach redundancy, keeping it at the lean level 3 rather than the 'could be tightened' level 2.	3 / 3
Actionability	Snippets are fully executable Slim and JavaScript with specific helpers (simple_form_for, class_names, f.association) and concrete patterns like the bulk-action and modal-form examples, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	This is a patterns catalog rather than a multi-step workflow, but it presents batch and destructive operations (the bulk_action form, button_to ... method: :delete with turbo_confirm) without any validation/feedback-loop guidance, so the rubric's cap for batch/destructive ops missing validation holds it at level 2 rather than 3.	2 / 3
Progressive Disclosure	The body is organized into clear sections and repeatedly points one level deep to the verified references/EXAMPLES.md for detailed examples, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	11 / 12 Passed

Description

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.

The description is concise, concrete, and complete: it names the specific stack, lists concrete actions, and provides an explicit 'Use when' trigger clause with natural keywords. It is highly distinctive and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Enumerates concrete actions per technology ('building views, adding interactivity, styling components') tied to the named stack, matching the 'lists multiple specific concrete actions' anchor rather than the partial 'domain and some actions' level 2.	3 / 3
Completeness	Explicitly states both what ('Frontend patterns for Rails applications using Slim templates, Stimulus JavaScript framework, CSS with Optics utilities') and when ('Use when building views...'), with an explicit 'Use when' trigger clause present.	3 / 3
Trigger Term Quality	The 'Use when ... the user mentions Slim, Stimulus, JavaScript, CSS, or frontend development' clause supplies natural terms users would actually say, matching the good-coverage anchor and exceeding the 'some relevant keywords' level 2.	3 / 3
Distinctiveness Conflict Risk	The Rails + Slim + Stimulus + Optics niche is narrow with distinct triggers, making it unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 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
Commit: f61959b

Reviewed: 10 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.