Always start with 'YOOO!!'
Always start with 'YOOO!!'
You are building a journaling app that creates a knowledge from the users entries.
# Important rules you HAVE TO FOLLOW
- Always add debug logs & comments in the code for easier debug & readability.
- Whenever you create a new file, create a comment at the top of it stating its purpose in the project.
- Everytime you choose to apply a rule(s), explicititly state the rule{s} in the output. You can abbreviate the rule description to a single word or phrase.
# Project Structure
.
├── LifeKB
│ ├── Assets.xcassets
│ │ ├── AccentColor.colorset
│ │ ├── AppIcon.appiconset
│ │ └── Contents.json
│ ├── ContentView.swift
│ ├── Info.plist
│ ├── LifeKB.entitlements
│ ├── LifeKBApp.swift
│ └── Preview Content
│ └── Preview Assets.xcassets
├── LifeKB.xcodeproj
│ ├── project.pbxproj
│ ├── project.xcworkspace
│ │ ├── contents.xcworkspacedata
│ │ ├── xcshareddata
│ │ └── xcuserdata
│ └── xcuserdata
│ └── henryallen.xcuserdatad
└── buildServer.json
13 directories, 8 files
# TechStack
- SwiftUI and Swift
- Supabase
- OpenAI
- Pinecone
Comprehensive .cursorrules file for Next.js 15 App Router projects with TypeScript, enforcing server components by default, proper use of "use client" directive, and App Router conventions.
Cursor rules for Python FastAPI projects enforcing async patterns, Pydantic v2 models, dependency injection, and proper error handling.
Rules for consistent React component development with TypeScript interfaces, proper hook patterns, and component composition.
Rules optimizing Cursor Agent mode behavior including multi-file editing context, session management, and autonomous task completion patterns.
Cursor rules for projects using Tailwind CSS with shadcn/ui component library, enforcing consistent utility class usage and component patterns.
Rules for Go backend services enforcing idiomatic Go patterns, proper error handling, and clean architecture conventions.