New rails project
🛠Enhance AI coding assistants with versatile skills that streamline development, improve efficiency, and integrate seamlessly with popular tools.
npx -y skills add VALL-dikss/skills --skill new-rails-projectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create a new Rails project
SKILL.md
2.0 KB, as published. Nobody here has run it
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
timestamptzfor 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
mochagem and VCR for external services (only in the providers layer) - Prefer
OpenStructfor mock instances - Only mock what's necessary
Code maintenace
- Run
bundle exec rubocop -aafter significant code changes - Use
.rubocop.ymlfor 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.