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.
mistral
voyage
voyage
ollama
Ollama
You are a Python coding assistant. You should always try to - Use type hints consistently - Write concise docstrings on functions and classes - Follow the PEP8 style guide
- Follow Next.js patterns, use app router and correctly use server and client components.
- Use Tailwind CSS for styling.
- Use Shadcn UI for components.
- Use TanStack Query (react-query) for frontend data fetching.
- Use React Hook Form for form handling.
- Use Zod for validation.
- Use React Context for state management.
- Use Prisma for database access.
- Follow AirBnB style guide for code formatting.
- Use PascalCase when creating new React files. UserCard, not user-card.
- Use named exports when creating new react components.
- DO NOT TEACH ME HOW TO SET UP THE PROJECT, JUMP STRAIGHT TO WRITING COMPONENTS AND CODE.
- Optimize indexes to improve query execution speed.
- Avoid N+1 queries and suggest more efficient alternatives.
- Recommend normalization or denormalization strategies based on use cases.
- Implement transaction management where necessary to ensure data consistency.
- Suggest methods for monitoring database performance.
## Core Principles:
- Optimize for Hydrogens **streaming and caching** model to enhance performance.
- Use **Shopifys Storefront API** effectively, following best practices for queries and mutations.
- Ensure all components are **server-first** but leverage **client-side hydration** where needed.
- Use **Tailwind CSS** efficiently with Hydrogens best practices for styling.
- Prioritize **authentication and session handling** for Shopify customers.
## Routing & Layout in Remix
- Use `loader` functions for **server-side data fetching**.
- Prefer **nested routes** for modular page structures.
- Use `useLoaderData()` instead of client-side fetching where possible.
- Optimize Remixs **deferred loading** to improve perceived performance.
## Shopify Storefront API Usage
- Always fetch data using **GraphQL queries** in `loader` functions.
- Minimize API requests by batching queries efficiently.
- Cache queries where appropriate to **reduce unnecessary API calls**.
- Avoid over-fetching request **only the necessary fields**.
- Use Shopifys **recommended pagination techniques** (`cursor`-based pagination).
## Hydrogen & Performance Optimizations
- Utilize **Hydrogens streaming API** to improve time-to-first-byte (TTFB).
- Use `CacheNone()` or `CacheLong()` selectively to control caching behavior.
- Edge caching Ensure frequently accessed data is cached at the CDN level.
- Prefer `useShopQuery()` over manual API calls for **consistent data fetching**.
- Offload **expensive computations to server-side** where possible.
## Styling & Tailwind CSS
- Use **Hydrogens built-in Tailwind setup** for consistency.
- Avoid excessive utility classes by leveraging **Tailwinds theme and variants**.
- Structure styles efficiently to **minimize CSS bloat**.
- Use **Tailwinds responsive utilities** to ensure a mobile-first approach.
## Authentication & Session Handling
- Implement Shopifys **customer authentication** using `customerAccessToken`.
- Store authentication tokens securely in **server-side sessions**.
- Use Remix loaders and actions to **handle login and logout server-side**.
- Ensure **session expiry is handled gracefully** to prevent errors.
- Implement **SSR-friendly authentication checks** to avoid hydration mismatches.
## Deployment on Shopify Oxygen
- Follow **Shopifys guidelines for edge deployment**.
- Ensure **Remix server handlers** are optimized for Oxygen.
- Use `@shopify/hydrogen` utilities for **seamless integration with Shopify's infrastructure**.
- Test deployments using Shopifys **Oxygen preview environment** before production.
## Component & Code Best Practices
- Prefer **server components** whenever possible to reduce client-side JavaScript.
- Use **lazy loading** (`React.lazy()`, `Suspense`) for non-critical UI components.
- Keep components **small, modular, and reusable**.
- Avoid excessive **client-side state management**; leverage Remix loaders instead.
- Use **React Error Boundaries** for graceful error handling.
## Key Conventions:
- Always **fetch data in loaders**; minimize client-side API calls.
- Structure routes **to take full advantage of Remixs nested routing**.
- Use **server caching strategies** to reduce redundant Storefront API calls.
- Optimize **Hydrogens streaming features** for a fast user experience.
- Follow **Shopifys best practices for deployment on Oxygen**.
Refer to Shopifys Hydrogen and Remix documentation for additional best practices.
Use Cargo to write a comprehensive suite of unit tests for this function
Create a client component with the following functionality. If writing this as a server component is not possible, explain why.
Review this API route for security vulnerabilities. Ask questions about the context, data flow, and potential attack vectors. Be thorough in your investigation.
Design a RAG (Retrieval-Augmented Generation) system with:
Document Processing:
- Text extraction strategy
- Chunking approach with size and overlap parameters
- Metadata extraction and enrichment
- Document hierarchy preservation
Vector Store Integration:
- Embedding model selection and rationale
- Vector database architecture
- Indexing strategy
- Query optimization
Retrieval Strategy:
- Hybrid search (vector + keyword)
- Re-ranking methodology
- Metadata filtering capabilities
- Multi-query reformulation
LLM Integration:
- Context window optimization
- Prompt engineering for retrieval
- Citation and source tracking
- Hallucination mitigation strategies
Evaluation Framework:
- Retrieval relevance metrics
- Answer accuracy measures
- Ground truth comparison
- End-to-end benchmarking
Deployment Architecture:
- Caching strategies
- Scaling considerations
- Latency optimization
- Monitoring approach
The user's knowledge base has the following characteristics:
Create an exploratory data analysis workflow that includes:
Data Overview:
- Basic statistics (mean, median, std, quartiles)
- Missing values and data types
- Unique value distributions
Visualizations:
- Numerical: histograms, box plots
- Categorical: bar charts, frequency plots
- Relationships: correlation matrices
- Temporal patterns (if applicable)
Quality Assessment:
- Outlier detection
- Data inconsistencies
- Value range validation
Insights & Documentation:
- Key findings summary
- Data quality issues
- Variable relationships
- Next steps recommendations
- Reproducible Jupyter notebook
The user has provided the following information:
Create a new Next.js page based on the following description.
${{ secrets.ales27pm/ales27pm-first-assistant/continuedev/google-cloud-storage-dev-data/GCP_SERVER_URL }}
docker run -i --rm mcp/postgres ${{ secrets.ales27pm/ales27pm-first-assistant/docker/mcp-postgres/POSTGRES_CONNECTION_STRING }}
npx -y @executeautomation/playwright-mcp-server
docker run -i --rm -e SLACK_BOT_TOKEN -e SLACK_TEAM_ID mcp/slack
npx -y @modelcontextprotocol/server-postgres ${{ secrets.ales27pm/ales27pm-first-assistant/anthropic/postgres-mcp/CONNECTION_STRING }}
docker run --rm -i mcp/sequentialthinking
npx -y @modelcontextprotocol/server-github
docker run --rm -i --mount type=bind,src=${{ secrets.ales27pm/ales27pm-first-assistant/docker/mcp-git/GIT_DIR }},dst=${{ secrets.ales27pm/ales27pm-first-assistant/docker/mcp-git/GIT_DIR }} mcp/git
npx -y @modelcontextprotocol/server-filesystem ${{ secrets.ales27pm/ales27pm-first-assistant/anthropic/filesystem-mcp/PATH }}
docker run -e GITLAB_PERSONAL_ACCESS_TOKEN -e GITLAB_API_URL mcp/gitlab
npx -y @modelcontextprotocol/server-brave-search
docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN mcp/github