Browse

CSS .cursorrules strategies

Filters

Tech

Clear

agency_swarm

openai

1. HTML

HTMX

AlpineJS

GitHub Pages

redis

morgan

winston

sequelize

prom-client

ExpressJs

Postgres

Prime React

Inertia.js

Pest

Jetstream

react-hook-form.

JsonKey

ChangeNotifierProvider

Flutter Hooks

cached_network_image

JsonValue

Riverpod Hooks

StateNotifierProvider

AssetImage

auto_route

StateProvider

Freezed

AsyncNotifierProvider

build_runner

GoRouter

ListView.builder

JsonSerializable

NotifierProvider

serverless environments

Nx

npm workspaces

API development

Lerna

swr

Postcss

Apollo Graphql

TypeORM

React.memo()

Lucide icons

RevenueCat

Shadcn UI components

Prisma ORM

Mux

RGAA

Jupyter Notebook

taskfile.dev

testify

loggo

TS

tailwind

shadcn

magicui

lucide

Supabase Client API

Supabase/Postgres

scikit-image

RPi.GPIO

SoundDevice

ORB

OpenCV

SIFT

YAML

cn utility

useCallback

useMemo

useImmerReducer

memo

temporal

frame motion

module css

Shopify Admin GraphQL API

Polaris

Genql

Vercel KV

NetCDF

nbdev

fastcore

Marisco

SASS

SCSS

Hugo

Go templating

Vinxi

React Query SSR

React Router

Tanstack Start

Obsidian Plugin Development

Google Chat

EditorConfig

nextjs app router

ShadCN-Graphs

ShadCN-UI

Google Calendar

Categories

Clear

Database Design

Deployment and Scaling

Personal Website

Minimalist Design

3D Graphics

Entrepreneurship

Design System

Laravel development

TALL stack

Alpine.js integration

Laravel 11 changes

Livewire components

Contract Development

Decentralized Applications (DApps)

Coding

Nuxt-specific Guidelines

Formatting

UI

Composition API

Key Conventions

ES6

Bun

GraphQL

Unix Philosophy

Behavior-Driven Development

Data Engineering

JavaScript Code Style

Static Generation

Async/Await

React Functional Components

JavaScript ES6

component libraries

frontend development

database integration

code maintainability

Async Ecosystem

Rust Best Practices

Concurrency

TypeScript coding standards

Web development

Error handling and validation

React best practices

Programming principles

AI Modeling

Village Simulation

Data Structures and Algorithms

Programming Paradigms

Prompting Guidance

AI Behavior Guidelines

Styling Guidelines

Web Scraping

Data Extraction

Software Best Practices

Mobile Development

Component Libraries

Software development

Code best practices

Debugging and Troubleshooting

Material UI Usage

iterative refinement

full-stack development

authentication

system thinking

clean code practices

data fetching

testing and documentation

User-Friendly Tools

README Generator

Software Projects

data science

software testing

command line applications

JavaScript naming conventions

Programming best practices

Code Improvement

Data Analysis

Medical Imaging

Code Reproducibility

document authoring

asynchronous operations

serverless architecture

Adobe Edge Delivery Services

accessibility

lazy loading

responsive design

GitHub integration

spreadsheet integration

semantic HTML

block-based development

metadata handling

content management

Cross-Platform Development

Scripting

Software Documentation

Programming Languages

Cross-platform applications

Schema validation

Monorepo management

Mobile development

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