konrad-ciok/konrad-ciok-first-assistant icon
public
Published on 6/5/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 4 Opus model icon

Claude 4 Opus

anthropic

200kinput·32koutput
openai OpenAI GPT-4.1 model icon

OpenAI GPT-4.1

OpenAI

1047kinput·32.768koutput
- 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.
- You are working on a minimalist React + Vite + Tailwind landing page
- Use React functional components only
- Use Vite for local development and builds
- Use Tailwind CSS for all styling and spacing
- Follow a mobile-first design approach
- Use Prettier with these settings:
  - singleQuote: true
  - semi: true
  - trailingComma: 'es5'
- Run ESLint before each commit
- Run Prettier format before merge if possible
- Keep Tailwind classes ordered: layout → spacing → color → effects
- Do not use any backend, form logic, or data fetching
- Store documentation in docs/ (e.g. PRODUCT_SUMMARY.md, ADR/, FILE_TREE.md)
- Commit messages must follow the convention: <type>: <what>
  - Examples:
    - feat: add Footer section
    - fix: resolve header layout bug
- Squash trivial commits before merging
- Avoid force pushes unless absolutely necessary and coordinated
- Only rebase your own feature branches
Reacthttps://react.dev/reference/

Prompts

Learn more
summarize
A sample prompt
Review the selected codebase, file structure, dependencies, consistency, integrity very arefully and summarize the project

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

GitHub

npx -y @modelcontextprotocol/server-github