Loading...
Generate pristine, structured .cursorrules files, file-scoped Cursor MDC rules (.cursor/rules/*.mdc), custom system prompts, and .cursor/mcp.json Model Context Protocol tool permission configs with 100% browser privacy.
100% Browser-Local Processing: All prompt parameters, rule sets, and file exports execute locally in client memory with zero server calls.
Place this file directly at the root of your repository (`/.cursorrules`).
# Cursor AI Agent Rules (.cursorrules) # Auto-generated by HiMat Technologies (https://himat.tech/free-tools/cursor-rules-prompt-generator) ## 1. Primary Role & Persona You are acting as a Senior Full-Stack Next.js & React Engineer. Follow high software engineering standards, write clean self-documenting code, and strictly adhere to project architecture. ## 2. Tech Stack & Framework Constraints - **Core Stack**: Next.js 16 (App Router), React 19, TypeScript (Strict), Tailwind CSS v4, Lucide React icons, Zod validation. ## 3. Code Style & Syntax Standards - Prefer Functional Components and React Hooks. Use Server Components by default; add 'use client' only when state or browser APIs are required. Follow strict TypeScript with zero 'any'. Wrap custom CSS variables in var(). ## 4. Architecture & Directory Structure - src/app (routes and layouts), src/components (reusable UI components), src/lib (utility functions & helpers), src/data (static datasets & catalogs), src/types (shared TypeScript definitions). ## 5. Error Handling & Quality Assurance - **Error Handling**: Use explicit error boundaries, typed try/catch blocks, and return structured error objects instead of throwing unhandled exceptions. - **Testing Standards**: Write unit tests with Vitest / React Testing Library. Ensure 100% type safety before building. ## 6. Security & Data Protection - **Security Guardrails**: Never expose secret API keys or credentials in client bundles or public repositories. Sanitize all user inputs. ## 7. Additional Project Rules 1. Always run lint checks or build validation before marking tasks complete. 2. Do not add third-party dependencies without explicit rationale.
Choose pre-configured best practices for Next.js 16, Python FastAPI, React 19, Node.js Express, or AI Agent MCP frameworks.
Tune role personas, folder structures, error handling guidelines, custom directives, and auto-approved MCP tools or terminal commands.
Copy formatted output to clipboard or download `.cursorrules`, `main.mdc`, `system_prompt.txt`, and `mcp.json` directly to your repository root.
Generate root .cursorrules Markdown files, file-scoped .cursor/rules/*.mdc files with glob patterns, custom AI system prompts, and .cursor/mcp.json permission configs.
Pre-configured best practices for Next.js 16 App Router, FastAPI & Pydantic v2, React + TypeScript, Node.js Express/Nest, AI Agents & MCP Servers, Go, and Rust.
Enforce code style, folder hierarchy, error handling, strict TypeScript settings, test suite conventions, and secret sanitization rules for Cursor AI agent.
Define auto-approved terminal commands and Model Context Protocol (MCP) tool server settings to streamline Cursor Composer agent workflows.
Instantly copy formatted configuration text to your clipboard or download `.cursorrules`, `main.mdc`, `system_prompt.txt`, and `mcp.json` directly to your local workspace.
All prompt compilation, rule formatting, and file exports run entirely inside your browser memory. Zero code, rules, or inputs are transmitted to remote servers.
HiMat's Cursor Rules & System Prompt Generator operates 100% locally inside your client web browser. Neither your project architecture, folder structures, system prompt settings, nor terminal commands leave your local machine.
`.cursorrules` is a legacy single root configuration file placed in your project root. Cursor now recommends `.cursor/rules/*.mdc` (Markdown Component) files, which allow you to set specific file glob patterns (e.g., `globs: ["**/*.tsx"]`), description metadata, and context-specific agent behaviors that only activate when matching files are edited.
For root rules, download or copy the output and create a `.cursorrules` file in your repository root directory. For modern MDC rules, create a `.cursor/rules/` directory in your project root and save the file as `.cursor/rules/main.mdc`. Cursor AI automatically reads these files upon startup.
Yes! Our tool includes a dedicated MCP Permission tab that generates `.cursor/mcp.json` configurations. You can specify auto-approved MCP servers and terminal commands so Cursor Composer can execute build, test, and lint commands without requiring manual confirmation dialogs every time.
No, absolutely not. The HiMat Cursor Rules & System Prompt Generator runs 100% client-side in your browser JavaScript memory. No project rules, tech stack choices, or system prompt settings leave your local machine.
Yes. In addition to `.cursorrules` and MDC files, our tool generates a raw System Prompt format that can be pasted into Cursor's System Prompt settings, Claude Desktop, ChatGPT, or custom LLM agent system messages.
HiMat Technologies builds production AI agent architectures, custom Model Context Protocol (MCP) integrations, automated refactoring pipelines, and fixed-scope AI pilots with complete source code ownership.
Continue with related utilities, services, and guides from HiMat.