minimaxir

Agent Guidelines for Python Code Quality

This document provides guidelines for maintaining high-quality Python code. These rules MUST be followed by all AI coding agents and contributors.

Your Core Principles

All code you write MUST be fully optimized.

"Fully optimized" includes:

cameroncooke

Agent instructions

Persona

• Address the user as Cam.
• Optimize for correctness and long-term leverage, not agreement.
• Be direct, critical, and constructive — say when an idea is suboptimal and propose better options.
• Assume staff-level technical context unless told otherwise.

Quality

• Inspect project config (package.json, etc.) for available scripts.

intellectronica

Source
../.config/ruler/instructions.md

Default Agent Instructions

• You have useful tools available as MCP or command-line. Use them.
• Unless you are absolutely sure that you have correct and, crucially, up-to-date information in your knowledge, always get information from the web. You can use Tavily for searching and getting information, and you can always use curl to fetch web pages.
• If you are working on something that presents web pages, you should use Playwright to open these pages, take snapshots, and inspect them.
• When working in a git repository, always switch to a new branch, unless explicitly insutrcted not to.
• If the git repo has a corresponding repo on GitHub, use the gh tool for things like looking at issues, opening pull requests, reading review comments, and looking at CI results.

veekaybee

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Foundational Concepts

Pre-Transformer Models

hybrist

JavaScript File Format Differences

There's the pervarsive notion that all JS is created equal and that there's only minor and easily detectable differences between the various file formats used to author JavaScript. This is correct, from a certain point of view.

For many people writing JavaScript that gets passed into build tools,

lehno

'use strict';


// Use this produce and consume jobs from AWS SQS as a normal queue list.
// Just add as a mixin and listen to your queues

const { Consumer } = require('sqs-consumer');
const Producer = require('sqs-producer');
const _ = require('lodash');
const AWS = require('aws-sdk');

byrro

CREDITS

This code snippet was extracted from an AWS Step Functions example.

It can ben found in the AWS Console for the Step Functions service.

Follow the instructions on this documentation page

Date: 2019-10-16

TrillCyborg

Mastodon Docker Setup

Setting up

Clone Mastodon's repository.

# Clone mastodon to ~/live directory
git clone https://github.com/tootsuite/mastodon.git live
# Change directory to ~/live

cd ~/live

snowkidind

Access to Ameritrade API

notes that may be helpful for node.js devs

What I've gathered is authorization tokens must be earned first. Authorization tokens are good for three months, once you are setup, you will get two tokens which come as long strings, An access_token and a refresh_token. Access tokens are only valid for 30 minutes so you will need to code to refresh the session using the refresh token frequently. When you refresh, you are given a new access token and that is what you use to "login" or pull from the api for the next period. But in order to get the tokens, you will be required to go through some processes to get a valid token that applies to your app. The following text kind of steers you in that direction...

Making an app

On the api site you will need to make an app, where you pick some random name by using some random numbers. It should be automatically generated but it isnt. For this field item, I simply went to https://www.uuidgenerator.net/ and just grabbed the firs

rauschma

Visual Studio Code shortcuts I use often

Navigation

Sidebar:

• Cmd-Shift-F: search
• Cmd-Shift-E: files

Navigating in current editor: