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.
When to Use
- You need to bootstrap a new Rails project with the opinionated stack defined in this skill.
- The project should start with Rails, PostgreSQL, Inertia.js, React, Vite, Tailwind, Sidekiq, and Redis already planned together.
- You want setup guidance that covers project creation, conventions, testing, and verification for a fresh Rails app.
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
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.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: new-rails-project3description: Create a new Rails project4license: MIT5---6
7Generate a new Rails project named $1 in the current directory. You may reference @CLAUDE.md for general guidance, though the guidance here takes precedence.
8
9## When to Use
10- You need to bootstrap a new Rails project with the opinionated stack defined in this skill.
11- The project should start with Rails, PostgreSQL, Inertia.js, React, Vite, Tailwind, Sidekiq, and Redis already planned together.
12- You want setup guidance that covers project creation, conventions, testing, and verification for a fresh Rails app.
13
14# Tech Stack
15Set up the following tech stack:
16- **Rails ~8** with PostgreSQL - Server-side framework and database
17- **Inertia.js ~2.3** - Bridges Rails and React for SPA-like experience without API
18- **React ~19.2** - Frontend UI framework
19- **Vite ~5** - JavaScript bundler with HMR
20- **Tailwind CSS ~4** - Utility-first CSS framework
21- **Sidekiq 8** - Background job processing with scheduled jobs via sidekiq-scheduler
22- **Redis** - Sessions, caching, and job queue
23
24# Rails guidance
25- Do not use Kamal or Docker
26- Do not use Rails "solid_*" components/systems
27- Development should generally match production settings where possible
28- Use Redis for caching
29
30# Database
31- All tables use UUID primary keys (pgcrypto extension)
32- Timestamps use `timestamptz` for timezone awareness
33- JSONB columns for flexible metadata storage
34- Comprehensive indexing strategy for performance
35- Encrypted fields for sensitive data (OAuth tokens, API keys)
36
37# Background jobs
38- Use Sidekiq 8 with Redis
39
40# Testing
41- Always use minitest
42- Use `mocha` gem and VCR for external services (only in the providers layer)
43- Prefer `OpenStruct` for mock instances
44- Only mock what's necessary
45
46# Code maintenace
47- Run `bundle exec rubocop -a` after significant code changes
48- Use `.rubocop.yml` for style configuration
49- Security scanning with `bundle exec brakeman`
50
51# Frontend
52- All React components and views should be TSX
53
54# General guidance
55- 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.
56
57# Verify
58Verify the boilerplate is working by running `bin/rails server` and accessing the application at `http://localhost:3000` via playwright MCP.
59
60## Limitations
61- Use this skill only when the task clearly matches the scope described above.
62- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
63- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
nous-hermeshub