Browse

Deno .cursorrules prompt files

Deno is a secure, modern runtime for JavaScript and TypeScript that simplifies code execution by providing a built-in package manager and TypeScript support without external configuration.

Filters

All

React

Tailwind CSS

Filters

Tech

Clear

TimelockController

Ruby on Rails

Inertia.JS

Supabase real time client

Nextjs

Supabase PostgresSQL

Plaid

Supabase auth

Plaid API

tabulate

rich

colorama

pyperclip

prompt-toolkit

jinja2

tiktoken

click

singleton

AppLocalizations

const constructors

underscores_case

reduce

factory

arrow functions

URL

lazy singleton

English

map

freezed

ThemeData

UPPERCASE

AutoRoute

Web3Modal

@tableland/sdk

@ethsign/sp-sdk

PostCSS

ethers.js

CSS modules

C

Javascript

Torii

Sozo

Katana

blockchain technology

Starknet

ECS

Dojo Framework

AllowedMethodsEnforcer

TimestampEnforcer

delegator-core-viem

@codefi/delegator-core-viem

IdEnforcer

ValueLteEnforcer

AllowedTargetsEnforcer

BlockNumberEnforcer

NonceEnforcer

LimitedCallsEnforcer

ICaveatEnforcer

NativePaidEnforcer

Ethereum Virtual Machine

IERC721

solidity contracts

SomeContract

DeployedEnforcer

ERC20BalanceGteEnforcer

AllowedCalldataEnforcer

ERC20TransferAmountEnforcer

solidity

MetaMask Delegation Toolkit

ERC-4337

Supabase SDK

SwiftUI

Swift

$bindable

$effect

$derived

$host

Snippets

$props

$state

$inspect

`createRawSnippet`

Nuxt UI Pro

Nuxt UI

Zunder UI

Unity 2021.3.18f1

C#

lambda expressions

SQL injection

Java reflection

Java collections

streams

@FunctionalInterface

Javadoc

diamond operator (<>)

cross-site scripting

Log4j

CountDownLatch

Java concurrency utilities

Windows

Rust Tauri Screenpipe Development .cursorrules prompt file

Rules:

Coding: louis is working on screenpipe most of the time, it's an open source app, lib, and CLI, that record screens & mics 24/7, extract OCR & STT, save to local db, connect to AI, do magic, it's written in Rust + Tauri and we write plugins (pipes) in TS + Deno. the Rust CLI is embedded as a sidecar in Tauri. it works on macos, windows, linux
Coding: always keep my style black and white, with some nerdy style and fonts pixelated / scientific style
Coding: do not remove @ts-ignore except if i explicitly ask you
Coding: always use lower case for logging stuff or UI
Coding: Rust: always use anyhow error, tokio instead of std stuff, avoid mutex if you can, prefer channels, write code easy to read for humans, fast for machines
Coding: when i ask to give me the full code it means FULL, no fucking // rest of the code comments GIVE ME THE FULL CODE
Coding: if it seems like you lack some context about a niche lib just ask me to provide the source code and i will (instead of providing a bad answer)
Coding: NextJS: make sure to use tailwind, typescript, shadcn, lucide, magicui, and framer-motion to make UIs amazing
Coding: Make sure to escape html thing like quotes etc properly. Only when necessary
Coding: When writing react or html code make sure to use thing like ' instead of ". Only when necessary (e.g inside quote themselves)

stack:

Rust Tauri Screenpipe Development .cursorrules prompt file

mediar

0

NEW

Deno Integration Techniques .cursorrules prompt file

@findhow Automation

This project contains automation scripts and workflows for the @findhow packages, based on the original Deno automation repository. The goal is to provide consistent and efficient automation for the @findhow ecosystem.

Purpose

The purpose of this project is to refactor and adapt the automation scripts from @https://github.com/denoland/automation for use with the @findhow packages found at @https://github.com/zhorton34/findhow.

Project Guidelines

Update all references from denoland/automation to zhorton34/automation.
Modify scripts to work with @findhow packages instead of @std packages.
Maintain the same structure and naming conventions as the original automation repository where possible.
Update configuration files to reflect the new @findhow ecosystem.
Adapt existing documentation to reflect the @findhow context.
Ensure all scripts and workflows are compatible with the @findhow package structure.
Update any hardcoded paths or references to point to the correct @findhow repositories.

Cursor AI Assistance

When working on this project, Cursor AI should:

Suggest replacements for denoland/automation references with zhorton34/automation.
Help identify and update package references from @std to @findhow.
Assist in updating configuration files and build scripts for the @findhow ecosystem.
Provide suggestions for adapting automation scripts to work with @findhow packages.
Offer insights on best practices for Deno package automation.
Help in identifying and resolving any compatibility issues that may arise from the transition.
Assist in updating examples and usage instructions in README files.

Version Control

When making changes:

Use descriptive commit messages that clearly indicate the purpose of the automation script updates.
Create separate branches for each major automation script or workflow update.
Regularly sync with the upstream zhorton34/automation repository to incorporate any updates or fixes.
Assist in creating pull request templates for automation updates.

Testing and Quality Assurance

Ensure all automation scripts are tested with @findhow packages.
Update test files to use the new @findhow namespace where applicable.
Maintain or improve the existing code coverage for automation scripts.
Ensure all CI/CD pipelines are updated to work with the @findhow ecosystem.
Suggest additional test cases for new or modified automation functionality.

Documentation

When updating documentation:

Update all references from denoland/automation to zhorton34/automation.
Update examples to use @findhow packages instead of @std packages.
Assist in generating documentation for new or modified automation scripts.
Help maintain consistent documentation style across all automation scripts.

Script Structure

When creating or modifying automation scripts:

Maintain consistent directory structures across all automation scripts.
Suggest appropriate file naming conventions for new scripts.
Assist in creating and updating main entry points for automation scripts.
Help organize and structure test files for automation scripts consistently.

Integration with @findhow

Ensure all automation scripts are compatible with the @findhow package structure.
Update any necessary import maps or configuration files to work with @findhow packages.
Modify CI/CD workflows to properly build, test, and publish @findhow packages.
Adapt release automation to work with the @findhow versioning and publishing process.

Remember to thoroughly test all modifications to ensure they work correctly with the @findhow ecosystem before merging changes into the main branch.

stack:

Deno