Rails Context

Always-on framing for outlaw-skills workflow skills (work, plan, and future brainstorm/ideate). Loaded near session start by those skills. Reusable verbatim across all of them.

This file is not a Rails tutorial. It is a posture document: how to think about a Rails task before reaching for code. The substantive Rails knowledge lives in the dispatch targets (layered-rails, ce-dhh-rails-style, controller-patterns, routing-patterns, frontend-patterns). This file tells you when and why to reach for them.

1. Operating Assumptions

• The codebase is Ruby on Rails. Default to Rails conventions before reaching for anything custom.
• The user has installed layered-rails, ce-dhh-rails-style, controller-patterns, routing-patterns, frontend-patterns. These are available as Skill-tool invocations.
• The user values clarity over cleverness, REST over RPC, fat models over service-object-everywhere, Hotwire over SPAs, and convention over configuration. When in doubt, choose the more conventional path.
• The user works exclusively in Rails. Do not propose stack changes, alternative frameworks, or non-Rails patterns unless explicitly invited.

2. Repo-Shape Probe