wem
## Build & Development Commands
- Frontend: Use `npm run dev` for React development. Use Vite or Next.js for modern setups. - Backend: Use `dotnet watch run` for C# backend development. Use ASP.NET Core. - Database: PostgreSQL should be run via Docker Compose or local install. Include a `.env` for connection strings. - Use Docker Compose for orchestration (React, C#, PostgreSQL, Redis, Kafka).
## Testing Guidelines
- Frontend: Use Jest and React Testing Library. Tests must cover edge cases and user flows. - Backend: Use xUnit or NUnit with Moq for C#. Follow Arrange-Act-Assert pattern. - Write integration tests for APIs and Kafka consumers/producers. - CI pipeline must run all tests on every push and pull request.
## Code Style & Guidelines
- React: Use functional components with hooks. Use Tailwind CSS for styling. Prefer `clsx` for conditional classes. - C#: Follow SOLID principles. Use dependency injection. Use async/await properly. Organize into Controllers, Services, Repositories. - Ensure both frontend and backend are modular, with reusable components or services. - Enforce Prettier and ESLint for frontend; use `dotnet format` or StyleCop for backend.
## Documentation Guidelines
- Use JSDoc or TypeScript types for component props and utility functions in React. - Use XML comments or Swagger annotations in C# for public APIs. - Each public endpoint should be documented with method, URL, expected inputs/outputs. - Maintain a `README.md` with how to run, build, test, and deploy both frontend and backend.
No Docs configured
No Prompts configured
No Data configured
No MCP Servers configured