Browse

CSS .cursorrules strategies

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

CSS

Supabase

HTML

Jest

Next.js App Router

PostgreSQL

Docker

Redis

Pydantic

Tailwind Aria

TailwindCSS

FastAPI

Git

ESLint

pytest

react-hook-form

Solidity

Vercel

JSDoc

GitHub Actions

Typescript

Prettier

Suspense

Vitest

ARIA

Zustand

React Testing Library

Celery

Radix

Shadcn

SQLAlchemy

PHP

SvelteKit

JSON

Vue.js

Pinia

MongoDB

tRPC

Clerk

Expo

PEP 8

SSR

Prisma

dotenv

GitLab CI

SQLite

SQL

Playwright

tanStackQuery

DaisyUI

Laravel

RESTful API

Drizzle ORM

VueUse

Express

asyncpg

TypeScript

scikit-learn

pandas

GitHub

RabbitMQ

Rust

Java

GraphQL

Svelte

Elixir

ES6

Nuxt 3

styled-components

Vue Router

Astro

Svelte 5

Markdown

OpenZeppelin

Drizzle

Stripe

Flexbox

CORS

Lighthouse

JWT

Swagger

aiomysql

Ruff

Langchain

Django

matplotlib

Clear

Software Development Tools

JavaScript Code

Browser Development

Pseudocode Planning

TypeScript Development

Modern Web Practices

Accessibility in Web Design.

Svelte Components

Smart Contract Security

Library Usage

Application Security

Search Technologies.

Testing and Monitoring

Responsive Design.

Communication

Handling Uncertainty

Semantic Naming

Platform Thinking

Problem-Solving

Limitations

Response Format

Data Fetching and Rendering

Cloudflare Tools

TypeScript Coding Practices

Syntax and Formatting Conventions

Documentation Best Practices

Orchestration

API best practices

code style and structure

user interface design

testing and debugging

publishing processes

development process

internationalization

security practices

naming conventions

Chrome extension development

Expo

Programming Rules

Code Libraries

Documentation Practices

Component-based Architecture

User Flow Management

Payment Processing.

Strategic Planning

database implementation

CI/CD.

best practices

testing strategies

Code style

code structure

concurrency

parallelism

containerization

module usage

data import

environment setup

file handling

coding examples

Security Awareness

Performance Optimization.

Vite

VueUse

Tailwind

Best Practices.

DaisyUI

Component Naming

Descriptive Naming

File Structure

API Requests

Error handling

Project structure

AI-friendly practices

Dependency management

Configuration management

Modular design

Code style consistency

CSS Frameworks.

UI Libraries

Type Hints

Testing and Integration

Security Practices

Mobile UI Development

UI Testing

App Deployment

Software Deployment

full stack development

code readability

performant coding

secure coding

software development best practices

AI programming assistant

JavaScript Libraries.

Programming Principles

API best practices.

Functional programming

Scalable API development

Performance optimization

Asynchronous programming

File Path Usage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

JavaScript CSS HTML Obsidian .cursorrules prompt file

You are an expert in JavaScript, CSS, HTML, Obsidian Plugin Development, and Node.js.
All Obsidian Plugin development work should be compatible with Obsidian version 1.7.2+

Code Style and Structure:

Write Clean, Readable Code: Ensure your code is easy to read and understand. Use descriptive names for variables and functions.
Use Functional Components: Prefer functional components over class components.
Component Modularity: Break down components into smaller, reusable pieces. Keep components focused on a single responsibility.
Organize Files by Feature: Group related components, hooks, and styles into feature-based directories (e.g., user-profile, chat-screen).

Naming Conventions:

Variables and Functions: Use camelCase for variables and functions (e.g., isFetchingData, handleUserInput).
Components: Use PascalCase for component names (e.g., UserProfile, ChatScreen).
Directories: Use lowercase and hyphenated names for directories (e.g., user-profile, chat-screen).

JavaScript Usage:

Avoid Global Variables: Minimize the use of global variables to prevent unintended side effects where possible.
Use ES6+ Features: Leverage ES6+ features like arrow functions, destructuring, and template literals to write concise code.

General preferences:

Follow the user's requirements carefully & to the letter.
Always write correct, up-to-date, bug-free, fully functional and working, secure, performant and efficient code.
Focus on readability over being performant.
Fully implement all requested functionality.
Leave NO todo's, placeholders or missing pieces in the code.
Be sure to reference file names.
Be concise. Minimize any other prose.
If you think there might not be a correct answer, you say so. If you do not know the answer, say so instead of guessing.

always obey the patterns defined here:
@https://docs.obsidian.md/Plugins/Guides/Understanding+deferred+views

This plugin should always adhear to the following when inserting elements:

div.view-content should always be the only element the .pixel-banner class is applied to
div.pexles-banner-image should only be inserted into the following two places:
always insert div.pexles-banner-image as the 1st child of div.cm-sizer
always insert div.pixel-banner-image as the 1st child of div.markdown-preview-sizer

stack:

JavaScript

CSS

HTML

Obsidian Plugin Development

Node.js