Builds REST APIs using respond_to blocks with Jbuilder templates following the 37signals same-controllers-different-formats philosophy. Use when adding API endpoints, JSON responses, token authentication, or when user mentions API, JSON, REST, or Jbuilder.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rails-37signals-patterns:37signals-apiThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build Rails APIs the 37signals way: the same controller serves HTML and JSON, JSON lives in Jbuilder templates, and the API stays RESTful and boring.
Build Rails APIs the 37signals way: the same controller serves HTML and JSON, JSON lives in Jbuilder templates, and the API stays RESTful and boring.
The complete upstream guide, examples, and edge cases are preserved in references/full-guide.md.
respond_to blocks instead of splitting into a large Api:: controller tree unless versioning forces it.*.json.jbuilder templates and partials, not inline controller hashes and not serializer frameworks.respond_to blocks so format.html and format.json both work cleanly.fresh_when, stale?, or collection caching.:created, :unprocessable_entity, :not_found, and :unauthorized.references/full-guide.md.npx claudepluginhub joshyorko/agent-skillsProvides Rails Action Controller patterns for routing, before_action filters, strong parameters, and REST conventions. Useful for building robust MVC controllers.
Establishes REST API design patterns for resource naming, HTTP methods and status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".