- Home
- Skills
- Steveclarke
- Dotfiles
- Real World Rails
real-world-rails_skill
- Shell
31
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
1 month ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill steveclarke/dotfiles --skill real-world-rails- SKILL.md1.5 KB
Overview
This skill researches how production Ruby on Rails applications solve architectural problems by inspecting a large collection of real app source code. It helps you find patterns, compare approaches, and synthesize concrete examples from real projects so you can make informed design choices for your own app. Use it when you want practical, code-level evidence of how teams implement features and structure Rails apps.
How this skill works
Given a topic you provide, the skill searches the available apps directory for relevant code: models, migrations, controllers, concerns, and config. It reads actual implementations and extracts common approaches, trade-offs, and representative snippets. When asked to choose among patterns for your project, it can spawn adversarial analyses that argue for competing options in your specific context.
When to use it
- You want concrete examples of how mature apps implement a Rails pattern (e.g., authorization, background jobs, tenancy).
- You need to compare multiple real-world approaches before deciding on a design.
- You’re troubleshooting how to scale or refactor a Rails feature and want proven patterns.
- You want code-level evidence (migrations, associations, queries) rather than high-level descriptions.
- You need an adversarial comparison of competing patterns tailored to your project.
Best practices
- Provide a clear, focused topic (feature, pattern, or component) to get targeted results.
- Indicate relevant constraints for your project (DB, scale, multi-tenant needs, team size).
- Request examples from specific high-profile apps if you want inspiration from certain domains.
- Ask for both synthesis and concrete file references so you can inspect the original code.
- Use adversarial analyses only when you want a direct, comparative recommendation for your project.
Example use cases
- Compare approaches to multi-tenancy (schema vs. row-level vs. separate DB) used by real apps.
- Find how production apps structure background job flows and error handling for retries.
- Discover common database indexing and migration strategies for large Rails schemas.
- See how apps implement authorization patterns (Pundit, CanCanCan, custom policies) in practice.
- Evaluate strategies for file uploads, CDN integration, and background processing from real projects.
FAQ
It inspects a local collection of production Rails app source trees (models, controllers, migrations, etc.). If the collection isn’t found locally, it will ask where the files live.
Can it recommend a single best pattern for my app?
Yes—when you provide project constraints the skill synthesizes trade-offs and can recommend the best fit. For contentious choices it can produce adversarial arguments for multiple options.