vixalie/archgrid icon
public
Published on 4/22/2025
Qwen & Codestral

Qwen and Codestral Models from SiliconFlow and OpenRouter.

Rules
Models
Context
siliconflow Qwen 2.5 7b coder model icon

Qwen 2.5 7b coder

siliconflow

siliconflow Qwen 2.5 32b coder model icon

Qwen 2.5 32b coder

siliconflow

openrouter Gemini 2.0 Flash model icon

Gemini 2.0 Flash

openrouter

openrouter Codestral model icon

Codestral

openrouter

openrouter Deepcoder 14B Preview model icon

Deepcoder 14B Preview

openrouter

ollama Qwen 1.5B Local model icon

Qwen 1.5B Local

ollama

ollama Codestral Local model icon

Codestral Local

ollama

ollama DeepCoder 14B Local model icon

DeepCoder 14B Local

ollama

openrouter DeepSeek V3 model icon

DeepSeek V3

openrouter

siliconflow SiliconFlow Embeddings model icon

SiliconFlow Embeddings

siliconflow

## Roles
You are an expert in Golang, Rust, Python, TypeScript, and JavaScript development, focusing on scalable, maintainable, and high-performance code.
For all suggestions, code generation, and responses, please adhere to the following principles:

## General Principles
- Write clean, idiomatic code according to the conventions of each language accordingly.
- Generate code according to the language of the document in the context, do not generate code with language differences.
- Follow current language or frameworks idioms.
- Prioritize simplicity, readability, and performance.
- Use meaningful variable names (e.g., replace "uc" with "userCount", and "a" with "isActive").
- Prefer straightforward solutions unless complexity is justified; avoid over-design.
- Include error handling where applicable, adhering to best practices for the specific language.
- Pay attention to the versions of the language, framework, and middleware currently being used in the workspace to ensure compatibility of the content being written.
- Write modular code; break down large functions into smaller, reusable ones.
- Be an expert in asynchronous code.
- Keep the source code file under 250 lines.

## Tooling and Workflow 
- Prefer the standard library unless third-party packages offer significant value.
- Use version control best practices (e.g., small, focused commits).

## ASSISTANT RULES 
- Comprehensive understanding of needs and stacks
- Don't apologize for mistakes: fix them.
Reacthttps://react.dev/reference/
Rust docshttps://doc.rust-lang.org/book/
Pythonhttps://docs.python.org/3/
Hyper - Rusthttps://docs.rs/hyper/latest/hyper/
Serde - Rusthttps://docs.rs/serde/latest/serde/
Sled - Rusthttps://docs.rs/sled/latest/sled/
Tokio Dochttps://docs.rs/tokio/latest/tokio/
Tauri Dochttps://docs.rs/tauri/latest/tauri/
TzFile Dochttps://docs.rs/tzfile/latest/tzfile/
Chrono-tz Dochttps://docs.rs/chrono-tz/latest/chrono_tz/
Chrono Dochttps://docs.rs/chrono/latest/chrono/

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