olivier-contant/frontend-assistant

Problem solving approach with tools (ignore if tools are not available):
1. Understand the user's request. Clarify ambiguous parts through conversation. Identify core problems to be solved, and determine which information and files you'll need to access
2. Explore the repository to find relevant code, using the ls, glob, and grep tools
3. Use the read tool to hone in on relevant files. Check the currently open file if the user's request doesn't point anywhere clear.
4. Generate a plan, identifying files which need to be updated, and considering the potential side effects
5. Implement the solution using the create new file and/or edit existing file tools.
6. Review and test changes using the run command and diff tools. If absolutely necessary, you can use the web search tool to find additional relevant context.

Remember to take an iterative approach - explore, understand, plan, implement, and test in smaller steps when dealing with complex problems.

Docs

Learn more

Turborepohttps://turbo.build/repo/docs

Vitehttps://vite.dev/guide/

Vitesthttps://vitest.dev/guide/

Tailwindcsshttps://tailwindcss.com/docs

Shadcn UIhttps://ui.shadcn.com/docs/installation

React hook formhttps://react-hook-form.com/docs

Zodhttps://zod.dev/

Zustandhttps://zustand.docs.pmnd.rs/getting-started/introduction

Ag-Gridhttps://www.ag-grid.com/react-data-grid/getting-started/

Module federationhttps://module-federation.io/guide/start/index.html

Vue docshttps://vuejs.org/v2/guide/

Prompts

Learn more

No Prompts configured

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

@file

Reference any file in your current workspace

@url

Reference the markdown converted contents of a given URL

@currentFile

Reference the currently open file

@repo-map

Reference the outline of your codebase

@open

Reference the contents of all of your open files

@commit

@os

Reference the architecture and platform of your current operating system

Data

Learn more

No Data configured

MCP Servers

Learn more

Playwright

npx -y @executeautomation/playwright-mcp-server

Memory

npx -y @modelcontextprotocol/server-memory

Browser MCP

npx -y @browsermcp/mcp@latest

Repomix

npx -y repomix --mcp

context7

npx -y '@upstash/context7-mcp@latest'