agentleFS
Sign inStart free
cpiprintcpiprint/skills/new-rails-project/SKILL.md

new-rails-project

Skill1 starsChanged 10 months agoMITView on GitHub

Create a new Rails project

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. VALL-dikss/skills★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use Kamal or Docker

    line 23
  2. Distinctive:

    Do not use Rails "solid_*" components/systems

    line 24
  3. Distinctive:

    Use Redis for caching

    line 26
  4. Distinctive:

    All tables use UUID primary keys (pgcrypto extension)

    line 29
  5. Distinctive:

    Use Sidekiq 8 with Redis

    line 36
  6. Very specific:

    Use mocha gem and VCR for external services (only in the providers layer)

    line 40
  7. Very specific:

    Prefer OpenStruct for mock instances

    line 41
  8. Distinctive:

    Only mock what's necessary

    line 42
  9. Very specific:

    Run bundle exec rubocop -a after significant code changes

    line 45
  10. Very specific:

    Use .rubocop.yml for style configuration

    line 46
  11. Distinctive:

    All React components and views should be TSX

    line 50
  12. Distinctive:

    Ask lots of clarifying questions when planning.

    line 53
  13. Very specific:

    Verify the boilerplate is working by running bin/rails server and accessing the application at http://localhost:3000 via playwright MCP.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generate a new Rails project named $1 in the current directory. You may reference @CLAUDE.md for general guidance, though the guidance here takes precedence.

Tech Stack

Set up the following tech stack:

  • Rails ~8 with PostgreSQL - Server-side framework and database
  • Inertia.js ~2.3 - Bridges Rails and React for SPA-like experience without API
  • React ~19.2 - Frontend UI framework
  • Vite ~5 - JavaScript bundler with HMR
  • Tailwind CSS ~4 - Utility-first CSS framework
  • Sidekiq 8 - Background job processing with scheduled jobs via sidekiq-scheduler
  • Redis - Sessions, caching, and job queue

Rails guidance

  • Do not use Kamal or Docker
  • Do not use Rails "solid_*" components/systems
  • Development should generally match production settings where possible
  • Use Redis for caching

Database

  • All tables use UUID primary keys (pgcrypto extension)
  • Timestamps use timestamptz for timezone awareness
  • JSONB columns for flexible metadata storage
  • Comprehensive indexing strategy for performance
  • Encrypted fields for sensitive data (OAuth tokens, API keys)

Background jobs

  • Use Sidekiq 8 with Redis

Testing

  • Always use minitest
  • Use mocha gem and VCR for external services (only in the providers layer)
  • Prefer OpenStruct for mock instances
  • Only mock what's necessary

Code maintenace

  • Run bundle exec rubocop -a after significant code changes
  • Use .rubocop.yml for style configuration
  • Security scanning with bundle exec brakeman

Frontend

  • All React components and views should be TSX

General guidance

  • Ask lots of clarifying questions when planning. The more the better. Make extensive use of AskUserQuestionTool to gather requirements and specifications. You can't ask too many questions.

Verify

Verify the boilerplate is working by running bin/rails server and accessing the application at http://localhost:3000 via playwright MCP.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free