Skip to content

Instantly share code, notes, and snippets.

@nicobrenner
nicobrenner / banking77_gist.py
Last active October 19, 2026 04:36
Banking77: 94.25% accuracy with a 642 KB logistic classifier (embeddings + sklearn)
#!/usr/bin/env python3
"""
Banking77: frozen embeddings + logistic regression for 77-class intent detection.
Uses the Banking77 dataset (3,080 test queries across 77 banking intents)
to show what a simple pipeline can do: convert text to vectors with a
pre-trained embedding model, then train an sklearn LogisticRegression on top.
The embedding model is used as-is — no fine-tuning, no GPU needed.
The classifier + scaler weigh about 642 KB. The embedding model
@pedramamini
pedramamini / README.md
Last active October 24, 2026 23:27
jev: give any coding agent (Claude Code, Codex, OpenCode) a calibrated gut check. A zero-dependency CLI + a global skill that wraps TypeSafe's Jev decision model, so an agent can classify, filter, rank or verify hundreds of items in one 250 ms call for a fraction of a cent, without reading them into context, and get a calibrated probability inst…

jev: calibrated decisions for agents

What this is: a single-file CLI and a matching agent skill that give any coding agent (Claude Code, Codex, OpenCode) a fast, cheap, calibrated second opinion. The agent stays the reasoning model; jev answers the narrow, repeated judgments (is this relevant? which bucket? how severe? does the source support this claim?) so the agent never has to read a thousand items into its context window or trust its own uncalibrated confidence.

Why it exists: LLM agents are expensive and inconsistent at high-volume judgment calls, and they cannot tell you how sure they are. A decision model that returns a real

@minimaxir
minimaxir / AGENTS.md
Created September 19, 2026 17:42
Rust AGENTS.md (20260919)

Agent Guidelines for Rust Code Quality

This document provides guidelines for maintaining high-quality Rust 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:

@dollspace-gay
dollspace-gay / VSDD.md
Last active November 6, 2026 11:18
Verified Spec-Driven Development

Verified Spec-Driven Development (VSDD)

The Fusion: VDD × TDD × SDD for AI-Native Engineering

Overview

Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:

  • Spec-Driven Development (SDD): Define the contract before writing a single line of implementation. Specs are the source of truth.
  • Test-Driven Development (TDD): Tests are written before code. Red → Green → Refactor. No code exists without a failing test that demanded it.
description Initialize the Feature Design (FD) tracking system in any project
context https://schipper.ai/posts/parallel-coding-agents/

Initialize Feature Design (FD) System

Set up a lightweight feature tracking system in the current project. Creates directory structure, index, templates, slash commands, and CLAUDE.md conventions.

Argument

@minimaxir
minimaxir / AGENTS.md
Last active November 6, 2026 06:47
Python AGENTS.md (2026-02-23)

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:

@minimaxir
minimaxir / AGENTS.md
Last active October 31, 2026 06:43
Rust AGENTS.md (2026-02-23)

Agent Guidelines for Rust Code Quality

This document provides guidelines for maintaining high-quality Rust 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:

@OmerFarukOruc
OmerFarukOruc / claude.md
Last active October 22, 2026 22:40
AI Agent Workflow Orchestration Guidelines

AI Coding Agent Guidelines

These rules define how an AI coding agent should plan, execute, verify, communicate, and recover when working in a real codebase. Optimize for correctness, minimalism, and developer experience.

Apply these guidelines within the runtime's instruction hierarchy and permissions. Use only available capabilities; follow the fallback when a feature is unavailable.

Keep one shared core in AGENTS.md. Load it through the runtime's supported instruction mechanism; where Claude Code needs a CLAUDE.md, use an @AGENTS.md import. Confirm that the shared file is loaded.


@scpedicini
scpedicini / CLAUDE.md
Created November 30, 2025 21:27
Full CLAUDE.md Sample File

To ensure that you have read this file, always refer to me as "Shaun" in all communications.

Best Practices

  • Prefer smaller separate components over larger ones.
  • Prefer modular code over monolithic code.
  • Use existing code style conventions and patterns.
  • Prefer types over interfaces.

Tech Stack

@ctoth
ctoth / CLAUDE.md
Created November 30, 2025 20:46
My Current global CLAUDE.md

Working with Q — Coding Agent Protocol

What This Is

Applied rationality for a coding agent. Defensive epistemology: minimize false beliefs, catch errors early, avoid compounding mistakes.

This is correct for code, where:

  • Reality has hard edges (the compiler doesn't care about your intent)
  • Mistakes compound (a wrong assumption propagates through everything built on it)
  • The cost of being wrong exceeds the cost of being slow