Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/copilot-instructions.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# This project is a Ruby on Rails application.

# Frontend requirements:
- Always use Stimulus for JavaScript behavior — do not write raw/inline JS or jQuery
- Always use Tailwind CSS utility classes for styling — do not write custom CSS unless absolutely necessary
- Prefer Turbo for navigation and form submissions before reaching for Stimulus
- ES6+ syntax, ESM imports/exports
- Stimulus controller naming: `[name]_controller.js`

# Code style requirements:
- Use modern Ruby syntax
- Prefer early returns and guard clauses
Expand Down Expand Up @@ -50,3 +57,9 @@ This project uses rubocop-rails-omakase. All code MUST follow these rules:
- Use `Foo.method` not `Foo::method` for method calls
- No parentheses around conditions: `if foo` not `if (foo)`
- No semicolons to separate statements

# PRs
- On every push, update the PR title and description to reflect the current diff

# Git
- When rebasing onto main, review incoming changes for their intent and flag any oversights — missing tests, incomplete migrations, broken assumptions, or conflicts between the two branches. Check both directions: schema/model changes on either branch that affect views, partials, or layouts on the other (e.g., main redesigned a table's CSS but your branch adds new columns to it, or vice versa)
14 changes: 14 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,6 +208,12 @@ end

## Frontend

### Preferences

- **Always use Stimulus** for JavaScript behavior — do not write raw/inline JS or jQuery
- **Always use Tailwind CSS** utility classes for styling — do not write custom CSS unless absolutely necessary
- Prefer Turbo for navigation and form submissions before reaching for Stimulus

### Stimulus Controllers (32)

Key controllers:
Expand Down Expand Up @@ -313,6 +319,14 @@ RuboCop linting on PRs and pushes to main.
| Positioning | Positioning gem for ordered records |
| API | JWT tokens, Apipie docs, Rack CORS |

## PRs

- On every push, update the PR title and description to reflect the current diff

## Git

- When rebasing onto main, review incoming changes for their intent and flag any oversights — missing tests, incomplete migrations, broken assumptions, or conflicts between the two branches. Check both directions: schema/model changes on either branch that affect views, partials, or layouts on the other (e.g., main redesigned a table's CSS but your branch adds new columns to it, or vice versa)

## Rake Tasks

Located in `lib/tasks/` (~17 files). Notable:
Expand Down
7 changes: 5 additions & 2 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,10 +149,11 @@ bundle exec bundle-audit check --update
## JavaScript

- ES6+ syntax, ESM imports/exports
- Prefer Stimulus + Turbo for new interactive features
- **Always use Stimulus** for JavaScript behavior — do not write raw/inline JS or jQuery
- **Always use Tailwind CSS** utility classes for styling — do not write custom CSS unless absolutely necessary
- Prefer Turbo for navigation and form submissions before reaching for Stimulus
- Controller naming: `[name]_controller.js`
- Keep controllers focused and small
- Use Tailwind CSS v4 utility classes

## Migrations

Expand All @@ -164,13 +165,15 @@ bundle exec bundle-audit check --update
- Default branch is `main`
- Commit messages should explain why, not what
- CI runs via GitHub Actions (`.github/workflows/`)
- **When rebasing onto main**, review incoming changes for their intent and flag any oversights — missing tests, incomplete migrations, broken assumptions, or conflicts between the two branches. Check both directions: schema/model changes on either branch that affect views, partials, or layouts on the other (e.g., main redesigned a table's CSS but your branch adds new columns to it, or vice versa)

## PRs

- Use `docs/pull_request_template.md` for PR description structure
- Use bullet points, not paragraphs, when filling out each section
- Description must explain why the change was made, not just what
- Include screenshots for UI changes
- **On every push**, update the PR title and description to reflect the current diff

## Quick Commands

Expand Down
Loading