zerchaboi1152003/my-first-assistant-13047 icon
public
Published on 3/25/2025
My First Assistant

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
## Build & Development Commands
- Project Overview: Clearly explain the purpose of the portfolio site.

Technology Stack: Mention Next.js, Tailwind CSS, Appwrite (database), Firebase (authentication).

Component Documentation:

Navbar: Sticky, minimal design.

Hero Section: Full-screen introduction.

Portfolio Showcase: Grid layout with hover effects.

Testimonials: Carousel or grid format.

Contact Form: Integrated with Firebase authentication, storing inquiries in Appwrite.

Code Examples: Provide snippets for key functionalities.

SEO & Performance:

Use next/image for optimized images.

Implement lazy loading for non-critical components.

Add structured data for better SEO ranking.

## Testing Guidelines
- 

## Code Style & Guidelines 
Use JSX instead of TYPESCRIPT.

Follow ESLint and Prettier for code formatting.

Maintain a modular folder structure:

components/ → Reusable UI components

layouts/ → Page layouts

pages/ → Next.js pages

lib/ → Utility functions, API calls

Use Next.js Server Components where applicable.

Ensure accessibility:

Proper alt attributes for images.

Good color contrast for readability.
- 

## Documentation Guidelines 
- Project Overview: Provide a brief description of the architecture portfolio website, its purpose, and key features.

Technology Stack: Mention and link to the official documentation of the technologies used:

Next.js (Frontend Framework) → https://nextjs.org/docs

Tailwind CSS (Styling) → https://tailwindcss.com/docs

Appwrite (Database & Backend) → https://appwrite.io/docs

Firebase (Authentication) → https://firebase.google.com/docs

Folder Structure: Document the project's folder organization:

components/ → UI components (Navbar, Hero, Portfolio, etc.).

layouts/ → Page layouts.

pages/ → Next.js route pages.

lib/ → Utility functions and API handlers.

Component Documentation: Explain the purpose and props of each key component.

Example:

Navbar: Sticky, minimal design with navigation links.

Hero Section: Full-screen introduction with CTA.

Portfolio Showcase: Grid layout with hover effects.

Contact Form: Integrated with Firebase authentication.

API & Database Documentation:

Authentication: Email/password and Google OAuth using Firebase.

Database Structure: Appwrite collections for storing portfolio projects and user inquiries.

API Routes: Explain Next.js API routes for handling database interactions.

Code Examples: Provide essential snippets, such as setting up authentication, fetching data, and UI components.

SEO & Performance Optimization:

Use next/image for optimized images.

Implement lazy loading for non-critical components.

Add structured metadata for SEO improvements.

Deployment & Hosting: Document the deployment process with relevant links:

Netlify (Next.js Hosting) → https://netlify.com/docs

Firebase Hosting (Alternative) → https://firebase.google.com/docs/hosting


torch.nn Docshttps://nextjs.org/docs
torch.nn Docshttps://appwrite.io/docs

Prompts

Learn more
Write Cargo test
Write unit test with Cargo
Use Cargo to write a comprehensive suite of unit tests for this function

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

No Data configured

MCP Servers

Learn more

No MCP Servers configured