angular-with-rails

What problem does it solve?

AI coding agents often generate incorrect Angular and Ruby on Rails integration setups, such as forcing Inertia (which is poorly suited for Angular's full SPA model), using insecure JWT storage, misconfiguring CORS, or ignoring Angular 17+ standalone component conventions. This Skill teaches agents the senior Rails-approved patterns for Angular integration to avoid these costly rework cycles.

Core Features & Use Cases

• Classical API+SPA Architecture: Enforces the correct Rails-API backend + standalone Angular SPA setup, avoiding misaligned Inertia adapters with thin ecosystem support.
• Production-Ready Patterns: Provides ready-to-use guidance for JWT authentication flows, standalone component setup, signals vs NgRx state management, and CORS configuration.
• Deployment Guidance: Covers separate deployment of Angular (via CDN or static host) and Rails (via Kamal) with proper domain and routing setup.
• Use Case: When you ask your AI to add an Angular frontend to your Rails 8 API, it will generate a secure, conventional setup instead of a broken Inertia-based monolith.

Quick Start

Ask your AI coding agent to set up a new Angular 17+ standalone SPA that connects to your existing Rails API with JWT authentication and proper CORS for separate deployment.