dollspace-gay

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.

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:

minimaxir

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

AI Coding Agent Guidelines (claude.md)

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.

---

Operating Principles (Non-Negotiable)

• Correctness over cleverness: Prefer boring, readable solutions that are easy to maintain.
• Smallest change that works: Minimize blast radius; don't refactor adjacent code unless it meaningfully reduces risk or complexity.

scpedicini

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

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

fungiboletus

- name: Overprovision like the pros'
  hosts: all
  tasks:
    - name: Install early OOM killer and zram
      ansible.builtin.apt:
        pkg:
          - earlyoom
          - zram-tools
    - name: Configure early OOM killer
      ansible.builtin.lineinfile:

alexedwards

func TestChain(t *testing.T) {
	used := ""

	mw1 := func(next http.Handler) http.Handler {
		return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
			used += "1"
			next.ServeHTTP(w, r)
		})
	}

tarruda

"""
A micro event loop library implementation from scratch.

This library provides a minimal but feature-complete asynchronous event loop
implementation for educational purposes. It demonstrates the core concepts of
asynchronous programming including:

- Task scheduling and management
- I/O multiplexing with non-blocking sockets
- Timeouts and sleep functionality

pirate

#!/usr/bin/env python3

# A single-file pure-python implementation of UUIDv7:  (e.g. 01941230-851a-77fd-9b0b-8c8eac3b2d23)
# - makes sure UUIDv7s are always generated in alphabetic order (using system time + nanoseconds + extra monotonic random bits)
# - store millisecond, microsecond, nanosecond / variable precision timestamps all using same format
# - graceful degradation in precision, falls back to monotonic urandom bytes depending on user-provided timestamp precision
# - fully compatible with standard UUIDv7 spec (48 bit millisecond unix epoch time with rand_a & rand_b monotonic randomness)
# - allows you to generate a UUIDv7 with a given timestamp (of any precision), and parse the timestamp back out from any UUIDv7
# - helps guarantee that UUIDv7s generated back-to-back in the same thread are always monotonically sortable
# - helps lower the risk of UUIDv7s colliding with other UUIDv7s generated in other threads / on other machines