eladser/wem icon
public
Published on 5/28/2025
WEM-TEST

wem

Rules
Models
Context
relace Relace Instant Apply model icon

Relace Instant Apply

relace

40kinput·32koutput
anthropic Claude 3.7 Sonnet model icon

Claude 3.7 Sonnet

anthropic

200kinput·8.192koutput
anthropic Claude 3.5 Sonnet model icon

Claude 3.5 Sonnet

anthropic

200kinput·8.192koutput
mistral Codestral model icon

Codestral

mistral

voyage voyage-code-3 model icon

voyage-code-3

voyage

voyage Voyage AI rerank-2 model icon

Voyage AI rerank-2

voyage

## 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

Prompts

Learn more

No Prompts configured

Context

Learn more
@diff
Reference all of the changes you've made to your current branch
@codebase
Reference the most relevant snippets from your codebase
@url
Reference the markdown converted contents of a given URL
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@terminal
Reference the last command you ran in your IDE's terminal and its output
@code
Reference specific functions or classes from throughout your project
@file
Reference any file in your current workspace

No Data configured

MCP Servers

Learn more

No MCP Servers configured