diplicity-react

Django backend guidance for diplicity-react — views, serializers, models, permissions, constants, transactions, and codegen. Use when implementing or reviewing backend features, modifying the Django service, or debugging API behavior.

React frontend guidance for diplicity-react — components, state management, forms, data loading, routing, mock data, screenshots, and testing. Use when implementing or reviewing React features, refactoring frontend code, or taking PR screenshots.

Android Capacitor guidance for diplicity-react — build workflow, ADB setup, Firebase Cloud Messaging, Google Sign-In, keystore management, SHA-1 fingerprints, and Fastlane releases. Use when building, deploying, or debugging the Android app, or managing Android credentials.

iOS Capacitor guidance for diplicity-react — build workflow, Xcode project setup, APNs and ASC credentials, code signing strategy, Fastlane releases, and GitHub Actions. Use when building, deploying, or debugging the iOS app, or managing iOS credentials.

Metabase analytics guidance for diplicity-react — native SQL patterns for multi-hop joins, base64 encoding workflow, and schema gotchas in the diplicity production database. Use when writing Metabase queries or working around schema limitations.

Production debugging guidance for diplicity-react — Railway CLI token conflict pattern, pgweb queries, write safety rules, and staging environments. Use when debugging production issues, querying the production database, or deploying PR staging environments.

Testing guidance for diplicity-react — frontend Vitest and backend pytest patterns, fixtures, conftest organisation, MSW mocks, and performance tips. Use when writing or running tests, setting up fixtures, or reviewing test code.

Create a single GitHub issue for diplicity-react from a free-text description — infer whether it's a bug, enhancement, or documentation change, dig the codebase to resolve ambiguity, write a tight type-appropriate body, apply the bug/enhancement/documentation category label, and create it untriaged. Use when the user asks to create, open, file, or write up a GitHub issue.

UX design decisions for diplicity-react — which controls to use, how to handle feedback, progressive disclosure, microcopy, accessibility, and interaction patterns. Load when building or reviewing any UI, making design decisions, or choosing between controls.

Create a single RFC in GitHub Discussions for diplicity-react from a free-text description — interview to nail the scope and a machine-readable definition of done, investigate the codebase to resolve ambiguity, write a tight RFC body, and post it to the RFC category as "under discussion". Use when the user wants to open an RFC, epic, or Discussion for work bigger than one PR.