cau1k

import { WarpGrepClient } from "@morphllm/morphsdk";
import { tool } from "@opencode-ai/plugin/tool";
import { promises as fs } from "fs";
import { resolve } from "path";

const z = tool.schema;

const MAX_RETRIES = 3;
const BASE_DELAY_MS = 250;
const MAX_CONTEXTS = 20;

cau1k

• No breadcrumbs. If you delete or move code, do not leave a comment in the old place. No "// moved to X", no "relocated". Just remove it.
• Minimize comments unless you are adding a // TODO: or otherwise necessary context for a senior developers who might not understand why you chose a certain paradigm. Line by line comments are completely unnecessary and you should opt for function/block scoped comments like JSDoc/TSDoc (/** ... */), python docstrings/pydoc (""" ... """), rustdoc (//{! |* | |}..., Go Doc (/* ... */`), etc.
• Think hard, do not lose the plot.
• When referencing files in the chat area, please ensure you use either the full path (i.e., ~/projects/... if it is not project specific. If it is indeed project specific, reference the relative path from the project, i.e. ./apps/server/...
• Search before pivoting. If you are stuck or uncertain, do a quick Nia MCP web search for official docs or specs, then continue with the current approach. Do not change direction unless asked.
• Whe

cau1k

tailwind based

• https://ui.shadcn.com
• https://www.diceui.com - really well designed components
• https://magicui.design - mostly overused but some components are great. PLEASE DON'T USE THE GLOBE COMPONENT!!!
• https://www.cult-ui.com - good if you like animations
• https://ui-layouts.com - a lot of gems but some of the components follow bad design patterns
• https://craft.mxkaske.dev - amazing
• https://originui.com/ - lot of variants for core shadcn components
• https://github.com/ekmas/neobrutalism-components

cau1k

***LSP MCP USAGE***
Whenever inspecting, debugging, or prior to writing code, you should ***always*** familiarize yourself with the definitions of the symbols, definitions, and references you are working with. The LSP mcp server provides an incredibly efficient way to do this. Here's an example:

<lsp_mcp_usage>
<example>
<context>
The user is debugging an error related to a function call in their code and needs to understand its definition and usages.
</context>

user: "I'm getting a TypeError when calling 'processData' in my main script. Can you help figure out why? @path/to/src/main.ts lines 9-11"

cau1k

services:
  cursor_qdrant:
    image: qdrant/qdrant:latest
    container_name: cursor-qdrant-db
    restart: unless-stopped
    ports:
      - "6333:6333"
    volumes:
      - ./cursor_qdrant_data:/qdrant/storage