rails-guides
Rails Guides
Official Rails documentation for reference during development.
Topic Map
Getting Started
references/getting_started.md— Rails basics, MVC overview, first app walkthroughreferences/command_line.md—railscommand, generators, rake tasksreferences/configuring.md— Environments, initializers, credentials, database.ymlreferences/autoloading_and_reloading_constants.md— Zeitwerk, module naming, reload behaviorreferences/initialization.md— Rails boot sequence, railties, engines
Active Record
references/active_record_basics.md— Models, CRUD, conventions, migrationsreferences/active_record_querying.md— Finders, scopes, joins, includes, explainreferences/active_record_validations.md— Built-in validators, custom validators, errorsreferences/active_record_callbacks.md— Lifecycle hooks, after_commit, skip_callbackreferences/association_basics.md— belongs_to, has_many, has_one, HABTM, polymorphic
More from lucianghinda/superpowers-ruby
ruby
Use when writing, reviewing, or debugging pure Ruby code — idiomatic patterns, modern 3.x+ features (pattern matching, Data.define, endless methods), error handling conventions (raise vs fail, result objects), memoization, and performance idioms. For Rails use rails-guides. For testing use minitest. For code style use sandi-metz-rules.
80test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
29sandi-metz-rules
This skill should be used when users request code review, refactoring, or code quality improvements for Ruby codebases. Apply Sandi Metz's four rules for writing maintainable object-oriented code - classes under 100 lines, methods under 5 lines, no more than 4 parameters, and controllers instantiate only one object. Use when users mention "Sandi Metz", "code quality", "refactoring", or when reviewing Ruby code for maintainability.
12writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
1237signals-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.
12brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
12