Browse

Obsidian Plugin Development .cursorrules strategies

Filters

Tech

Clear

MacOS

Vuejs

shadcn/u

ESModule

Anthropic APIs

NodeJS

Plain JS

Remix

Yoga

Pulumi

PandaCSS

VueMacroes

@testing-library/vue

Tiptap

@faker-js/faker

@tool-belt/type-predicates

Reactivity transform

vitest

llama-index

langchain

WebPageTest

11ty

eleventy

Tremor

LangChain

Local Storage

React Context API

Mockito

Java Platform Module System (JPMS)

DeepLearning4J

Terraform

Spring Framework

Java Cryptography Architecture (JCA)

Eureka Server

Hibernate

Ansible

Hadoop

Spring MVC

Spark

JBehave

Cucumber

Spring Cloud Gateway

JUnit 5

Logback

Spring Boot Actuator

Java Persistence API (JPA)

Franklin

Airbnb’s JavaScript Style Guide.

Helix

Adobe Edge Delivery Services

uvicorn

SqlAlchemy 2.0

arq

Alembic

Postgres v3.12

LINQ

Moq

MSTest

ASP.NET Core

AutoMapper

Entity Framework Core

IMemoryCache

Fluent Validation

NUnit

NSubstitute

Dependency Injection

Swashbuckle.AspNetCore

xUnit

RESTful

Poetry

with statements

bcrypt

ReDoc

Python's logging module

async support

dependency injection

Factory Boy

list comprehensions

Swagger UI

requirements.txt

FastAPI's TestClient

Dockerfiles

docstrings

parse_obj_as

type hints

Bootstrap

decorators

Jinja2

generator expressions

BaseSettings

context managers

Sveltekit 2

CDN

Firebase CLI

Firebase Crashlytics

Firebase Firestore

Xcode

Google Analytics

Firebase Authentication

Firebase Cloud Messaging

Categories

Clear

Security Considerations

Software Design Patterns

Data Validation

Tailwind CSS

Component Modularity

Mobile App Development

Data Storage

Git Workflow

System Design

Styling and Design

Data Transformation

animations

Simulations

Multi-Agent Systems

middleware

response schemas

scalable API development

caching strategies

input validation

AI-friendly coding practices

configuration management

project structure

type hints

debugging

code style consistency

logging

modular design

code snippets.

API-based applications

software components

graphical applications

software development

LLM applications

Programming Assistance

Scalable API Development

Project Conventions

Model Evaluation

Chemistry

Reproducibility

Data Augmentation

Data Preprocessing

Deep Learning

Experiment Tracking

Project Structure

Neural Networks

Graph Neural Networks.

Hyperparameter Tuning

Architecture

Behavior

Configuration Management

Monitoring

Logging

Libraries

Dependency Management

Project Specific

code best practices

data validation

data analysis

data visualization

PEP 8 guidelines

EEG application development

Software development best practices.

User interface design

Signal processing

LLM Integration

Security Practices.

Project Structuring.

Open Source Tools

Coding Principles

Caching

CI/CD Pipelines

Data Infrastructure

Server-Side Programming

Cloud Platforms

Microservices Architecture

Containerization and Orchestration

Data Modeling

Desktop Application Development

Programming Best Practices.

API Communication

File Structure.

Web Development.

Blockchain Technology

User Interface Development

Software Development Best Practices

Code Performance

Software Refactoring

Debugging

Problem Solving.

Technology Integration

Dynamic Loading.

URL State Management

Code Examples

Commit Guidelines

Reusable Code

Frontend Development.

Modular Design

Gas Efficiency

Commit Messaging

Automated Testing

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