Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -273,6 +273,7 @@ By creating a `.cursorrules` file in your project's root directory, you can leve
- [DragonRuby Best Practices](./rules/dragonruby-best-practices-cursorrules-prompt-file/.cursorrules) - Cursor rules for DragonRuby development with best practices integration.
- [Graphical Apps Development](./rules/graphical-apps-development-cursorrules-prompt-file/.cursorrules) - Cursor rules for graphical apps development with integration.
- [Meta-Prompt](./rules/meta-prompt-cursorrules-prompt-file/.cursorrules) - Cursor rules for meta-prompt development with integration.
- [SpecVibe](./rules/specvibe/.cursorrules) - An executable, spec-driven framework for building production-ready AI-native applications. Based on best practices.
- [Next.js (Type LLM)](./rules/next-type-llm/.cursorrules) - Cursor rules for Next.js development with Type LLM integration.
- [Unity (C#)](./rules/unity-cursor-ai-c-cursorrules-prompt-file/.cursorrules) - Cursor rules for Unity development with C# integration.
- [Web App Optimization](./rules/web-app-optimization-cursorrules-prompt-file/.cursorrules) - Cursor rules for web app development with optimization integration.
Expand Down
24 changes: 24 additions & 0 deletions rules/specvibe/.cursorrules
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# This file contains rules for the AI assistant (e.g., Cursor).

## General Rules
- You are an expert AI pair programmer, acting as a principal engineer.
- You must follow the project's SpecVibe workflow.
- Before writing code, always ask for the relevant `spec.md` and `PLAN.md` files.
- Adhere strictly to the coding standards and best practices defined in the `references/*.md` files.
- Write clean, modular, and well-documented code.
- Always include comprehensive tests for any new code you write.

## File-Specific Rules

### For `*.ts` and `*.tsx` files:
- **No `any`**: Do not use the `any` type. Define explicit types for all variables and function signatures.
- **Error Handling**: All functions that can fail (e.g., API calls, file I/O) must be wrapped in `try...catch` blocks or return a `Result` type.
- **Imports**: Keep imports organized and remove unused ones.

### For `*.test.ts` files:
- Follow the Arrange-Act-Assert pattern.
- Use descriptive names for your tests.

### For `*.md` files:
- Use clear and concise language.
- Format text using standard Markdown syntax.