37signals-style
Rails coding patterns derived from analysis of 37signals' Fizzy codebase. Use when writing Rails code in 37signals/Basecamp style or when asked to follow 37signals patterns. Covers controllers, models, views, Hotwire, testing, database, security, and team philosophy.
71
63%
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/37signals-style/SKILL.mdQuality
Discovery
89%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 solid skill description with excellent trigger terms and completeness. The 'Use when' clause is explicit and the 37signals/Basecamp/Fizzy niche makes it highly distinctive. The main weakness is that the capabilities are listed as topic categories rather than specific concrete actions the skill enables.
Suggestions
Replace the category list ('Covers controllers, models, views...') with specific concrete actions like 'Generates controllers following 37signals' thin-controller patterns, applies Hotwire Turbo Frame conventions, structures models with concerns and callbacks per Fizzy conventions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Rails coding patterns) and lists topic areas (controllers, models, views, Hotwire, testing, database, security, team philosophy), but these are categories rather than concrete actions. It doesn't describe specific actions like 'generates controller code' or 'applies Hotwire Turbo patterns'. | 2 / 3 |
Completeness | Clearly answers both what ('Rails coding patterns derived from analysis of 37signals' Fizzy codebase') and when ('Use when writing Rails code in 37signals/Basecamp style or when asked to follow 37signals patterns'). The 'Use when...' clause is explicit and well-defined. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Rails', '37signals', 'Basecamp', 'Hotwire', 'controllers', 'models', 'views', 'testing', 'Fizzy'. A user asking about 37signals patterns, Basecamp-style Rails, or Hotwire would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific niche of 37signals/Basecamp/Fizzy Rails patterns. This is unlikely to conflict with generic Rails skills or other coding skills because of the very specific organizational and codebase context. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill body is essentially a pure table of contents with no substantive content of its own. While it's admirably concise and well-organized, it provides zero actionable guidance — no key patterns, no code examples, no decision-making heuristics, and no workflow for applying 37signals conventions. A developer or Claude reading only this file would learn nothing about 37signals style beyond the existence of reference documents.
Suggestions
Add a 'Quick Reference' or 'Key Principles' section with 5-10 of the most important 37signals patterns inline (e.g., 'Thin controllers, fat models', 'Prefer Turbo Frames over custom JS', 'Use concerns for shared behavior') so the skill provides immediate value without requiring reference file lookups.
Add a brief workflow or decision guide, e.g., 'When writing a new feature: 1. Start with the model (see models.md), 2. Add a RESTful controller (see controllers.md), 3. Use Hotwire for interactivity (see hotwire.md)' to give Claude a clear sequence for applying these patterns.
Include at least one concrete code example showing the canonical 37signals style (e.g., a thin controller action with a concern) so Claude has an immediate, executable reference point.
Add brief annotations to each reference link describing when to consult it (e.g., 'references/hotwire.md — Consult when adding interactivity without full-page reloads') to help with navigation and decision-making.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — just a brief context-setting sentence and a well-organized topic map. No unnecessary explanations of what Rails is, what 37signals is, or how to use the references. Every token earns its place. | 3 / 3 |
Actionability | The skill body contains zero concrete guidance, code examples, commands, or actionable instructions. It is purely a table of contents pointing to reference files, with no inline patterns, rules, or executable content whatsoever. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. No guidance on when to consult which reference, no decision tree for choosing patterns, and no validation steps. It's purely a flat index. | 1 / 3 |
Progressive Disclosure | The topic map is well-organized into logical categories with one-level-deep references, which is good. However, there is no quick-start content, no inline summary of key patterns, and no guidance on which references are most important — it's essentially all disclosure with no primary content to progressively disclose from. | 2 / 3 |
Total | 7 / 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
- lucianghinda/superpowers-ruby
- Commit
cb03f92
- 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.