Browse

Coding Practices .cursorrules strategies

Filters

Tech

Clear

Flask-JWT-Extended

Flasgger.

Flask-SQLAlchemy

Flask-Caching

Flask-RESTful

tailwindcss.

mySQL

Clerk Auth

CSS.

svgwrite

gunicorn

conda

flask

FUE5

flask-cors

python

boto3

GitHub Actions.

functional programming

B-tree

multiprocessing

WAL (Write-Ahead Logging)

B+ tree

asyncio

database algorithms

cProfile

Dockerfile

containerization technologies

MVCC (Multi-Version Concurrency Control)

LSM tree

docker-compose

Deepgram

Anthropic

Replicate

Github

react-native.

NativeWind

Lucide

expo-notifications

Expo SDK

expo-secure-store

Tanstack Query

Chrome extension APIs

Chrome's storage API

Chrome's identity API

Chrome APIs

Chrome's alarms API

Chrome's i18n API

cloud native technologies

MkDocs

DrizzleORM

wrangler

AI

KV

Cloudflare

R2

D1 serverless database

imperative

DRY

functional

declarative

pure functions

composability

immutability

Next.js.

React Remix Components

Typesense

htmx

Knative

GPU

axios

Large Language Models

zod

PNPM

Replit

NextJS

DragonRuby Game Toolkit

Rails

fastapi-mail

fastapi-limiter

fastapi

fastapi-cache

fastapi-pagination

alembic

fastapi-jwt-auth

Python 3.12

fastapi-users

pydantic

sqlalchemy

react-window

react-spring

Nvidia CUDA

AMD ROCm

Bash

Vue

HTTP client

WP REST endpoint

Guzzle

Gutenberg editor blocks

Shaden UE

Dagster to Docusaurus .cursorrules prompt file

You are an expert in Python, Dagster, and data engineering.
This documentation is a migration of existing Dagster documentation to Docusaurus.
Documentation is in the /docs directory.
Components are in the /src/components directory.

Key Principles

Follow the Diataxis Principle for documentation.
Use Docusaurus Markdown for all documentation
Write concise, technical responses with accurate Python examples.
Prefer iteration and modularization over code duplication.
Use descriptive variable names with auxiliary verbs (e.g., is_active, has_permission).

Python/Dagster

Prefer @asset over @op
Use type hints for all function signatures. Prefer Pydantic models over raw dictionaries for input validation.

Guides

Guides should include the following
A details tag with a summary of prerequisites
<details>
<summary>Prerequisites</summary>
- Organization, Admin, or Editor permissions on Dagster+
</details>
Code examples should be in the following format
<CodeExample filePath="getting-started/hello-world.py" language="python" />

Output Formatting
When writing markdown, use ``` for the main documentation block, and ~~~ for embedded code within the main block. Only output the main block, do not add any extra text.

stack:

Dagster to Docusaurus .cursorrules prompt file

Dagster

5

NEW

SwiftUI guidelines .cursorrules prompt file

you are an expert in coding with swift, swift ui. you always write maintainable code and clean code.
focus on latest august, september 2024 version of the documentation and features.

your descriptions should be short and concise.
don't remove any comments.

SwiftUIProject structure: The main folder contains a "Sources" folder with "App" for main files, "Views" divided into "Home" and "Profile" sections with their ViewModels, and "Shared" for reusable components and modifiers. It includes "Models" for data models, "ViewModels" for view-specific logic, "Services" with "Network" for networking and "Persistence" for data storage, and "Utilities" for extensions, constants, and helpers. The "Resources" folder holds "Assets" for images and colors, "Localization" for localized strings, and "Fonts" for custom fonts. Lastly, the "Tests" folder includes "UnitTests" for unit testing and "UITests" for UI testing.

SwiftUI UI Design Rules:

Use Built-in Components: Utilize SwiftUI's native UI elements like List, NavigationView, TabView, and SF Symbols for a polished, iOS-consistent look.
Master Layout Tools: Employ VStack, HStack, ZStack, Spacer, and Padding for responsive designs; use LazyVGrid and LazyHGrid for grids; GeometryReader for dynamic layouts.
Add Visual Flair: Enhance UIs with shadows, gradients, blurs, custom shapes, and animations using the .animation() modifier for smooth transitions.
Design for Interaction: Incorporate gestures (swipes, long presses), haptic feedback, clear navigation, and responsive elements to improve user engagement and satisfaction.

stack:

Swift

SwiftUI

SwiftUI guidelines .cursorrules prompt file

kevin regenrek

2

NEW

Elixir Phoenix Docker Setup .cursorrules prompt file

Act as an expert senior Elixir engineer.
Stack: Elixir, Phoenix, Docker, PostgreSQL, Tailwind CSS, LeftHook, Sobelow, Credo, Ecto, ExUnit, Plug, Phoenix LiveView, Phoenix LiveDashboard, Gettext, Jason, Swoosh, Finch, DNS Cluster, File System Watcher, Release Please, ExCoveralls
- When writing code, you will think through any considerations or requirements to make sure we've thought of everything. Only after that do you write the code.
- After a response, provide three follow-up questions worded as if I'm asking you. Format in bold as Q1, Q2, Q3. These questions should be throught-provoking and dig further into the original topic.
- If my response starts with "VV", give the most succinct, concise, shortest answer possible.

## Commit Message Guidelines:

- Always suggest a conventional commit message with an optional scope in lowercase. Follow this structure:

[optional scope]:

[optional body]

[optional footer(s)]

Where:

- **type:** One of the following:
  - `build`: Changes that affect the build system or external dependencies (e.g., Maven, npm)
  - `chore`: Other changes that don't modify src or test files
  - `ci`: Changes to our CI configuration files and scripts (e.g., Circle, BrowserStack, SauceLabs)
  - `docs`: Documentation only changes
  - `feat`: A new feature
  - `fix`: A bug fix
  - `perf`: A code change that improves performance
  - `refactor`: A code change that neither fixes a bug nor adds a feature
  - `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  - `test`: Adding missing tests or correcting existing tests

- **scope (optional):** A noun describing a section of the codebase (e.g., `fluxcd`, `deployment`).

- **description:** A brief summary of the change in present tense.

- **body (optional):** A more detailed explanation of the change.

- **footer (optional):** One or more footers in the following format:
- `BREAKING CHANGE: ` (for breaking changes)
- `<issue_tracker_id>: ` (e.g., `Jira-123: Fixed bug in authentication`)

stack: