pluggedin-app: Cursor rule for Cursor

Plugged.in Project Intelligence Rules

Project Structure Patterns

1. The app uses a Next.js App Router structure:

   • app/ - Main application folder
   • app/(sidebar-layout)/ - Routes with the sidebar layout
   • app/actions/ - Server actions for backend operations
   • app/api/ - API routes for external access
   • db/ - Database schema and utilities
   • types/ - TypeScript type definitions
   • components/ - Reusable UI components
   • hooks/ - Custom React hooks

2. MCP server logic is organized as:

   • db/schema.ts - Database schema definitions
   • app/actions/mcp-servers.ts - Server actions for MCP servers
   • app/actions/custom-mcp-servers.ts - Server actions for custom MCP servers
   • types/mcp-server.ts - Type definitions for MCP servers
   • app/(sidebar-layout)/(container)/mcp-servers/ - UI for MCP server management

3. MCP playground components:

   • app/actions/mcp-playground.ts - Server actions for MCP playground
   • app/actions/playground-settings.ts - Server actions for playground settings
   • app/(sidebar-layout)/(container)/mcp-playground/page.tsx - UI implementation
   • app/(sidebar-layout)/(container)/mcp-playground/README.md - Documentation

Code Patterns

1. Server-side operations use Next.js server actions:

   'use server';
   
   export async function serverAction(arg1, arg2) {
     // Database operations or other server-side logic
   }
   

2. Database operations use Drizzle ORM with PostgreSQL:

   import { db } from '@/db';
   import { someTable } from '@/db/schema';
   
   // Query example
   const result = await db.query.someTable.findFirst({
     where: eq(someTable.id, someId)
   });
   
   // Insert example
   await db.insert(someTable).values({
     field1: value1,
     field2: value2
   });
   

3. Frontend data fetching uses SWR:

   const { data, error, mutate } = useSWR(
     key,
     () => fetchFunction(args)
   );