dzamataev/dzamataev-first-assistant icon
public
Published on 6/6/2025
Semilocal React Native Assistant 3301

This is an example custom assistant that will help you complete the Python onboarding in VS Code. After trying it out, feel free to experiment with other blocks or create your own custom assistant.

Rules
Prompts
Models
Context
anthropic Claude 3.7 Sonnet model icon

Claude 3.7 Sonnet

anthropic

200kinput·8.192koutput
anthropic Claude 3.5 Haiku model icon

Claude 3.5 Haiku

anthropic

200kinput·8.192koutput
openai OpenAI GPT-4o Mini model icon

OpenAI GPT-4o Mini

OpenAI

128kinput·16.384koutput
ollama nomic-embed-text latest model icon

nomic-embed-text latest

ollama

openai OpenAI GPT-4o model icon

OpenAI GPT-4o

OpenAI

128kinput·16.384koutput
openai OpenAI GPT-4.1 model icon

OpenAI GPT-4.1

OpenAI

1047kinput·32.768koutput
openai OpenAI GPT-4.1 mini model icon

OpenAI GPT-4.1 mini

OpenAI

1047kinput·32.768koutput
ollama qwen2.5-coder 1.5b model icon

qwen2.5-coder 1.5b

ollama

32kinput·8.192koutput
You are a React Native coding assistant. You should always try to
    - Use Typescript types consistently
    - Write concise comments with annotations on functions and classes
    - Follow the following codestyle rules:
      - no end line semicolon
      - whitespace after brackets
    - Check your edits with typescript compiler and fix errors as necessary
    - In assistant mode read files you want to edit before editing them
    - Do not teach me how to setup project, go straight to writing code necessary to solve the task
React Native docshttps://reactnative.dev/docs/

Prompts

Learn more
Jest Test
Write comprehensive Jest tests for the provided code file.
Write comprehensive Jest tests for the provided code file. Follow this iterative process:
Process:

Scan `__tests__` directory - find all existing test files and identify which source files need tests
Analyze the code - understand functions, methods, dependencies, and expected behaviors
Create/update tests - write new Jest test files or update existing ones in `__tests__` directory
Run yarn test - execute tests and check output
Iterate - if tests fail, modify the test code (NOT source code) until all pass
Repeat steps 4-5 until all tests pass

Test Requirements:

Use describe blocks for grouping
Test happy paths, edge cases, and error handling
Mock external dependencies appropriately
Use clear, descriptive test names
Follow Arrange-Act-Assert pattern

Key Rules:

Never modify the source code - only create/update test files in `__tests__` directory
Create new test files following naming convention (e.g., filename.test.js)
Run yarn test after each change
Keep iterating until all tests pass
Ensure good coverage of all source files

First, scan the `__tests__` directory and source files to determine what tests need to be created or updated.

Context

Learn more
@code
Reference specific functions or classes from throughout your project
@docs
Reference the contents from any documentation site
@diff
Reference all of the changes you've made to your current branch
@terminal
Reference the last command you ran in your IDE's terminal and its output
@problems
Get Problems from the current file
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@codebase
Reference the most relevant snippets from your codebase
@currentFile
Reference the currently open file
@open
Reference the contents of all of your open files
@file
Reference any file in your current workspace
@repo-map
Reference the outline of your codebase
@commit

No Data configured

MCP Servers

Learn more

No MCP Servers configured