Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
Terminals should generate the 256-color palette from the user's base16 theme.
If you've spent much time in the terminal, you've probably set a custom base16 theme. They work well. You define a handful of colors in one place and all your programs use them.
The drawback is that 16 colors is limiting. Complex and color-heavy programs struggle with such a small palette.
| #!/usr/bin/env bun | |
| /** | |
| * ============================================================ | |
| * PROOF: Anthropic is specifically blocking "OpenCode" | |
| * in Claude Code OAuth system prompts | |
| * ============================================================ | |
| * | |
| * Video covering this script here: https://www.youtube.com/watch?v=G9YX6StP2-M | |
| * | |
| * This script demonstrates that Anthropic has specifically blocked |
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
The name of this project is "Yeetsheet". Yeetsheet is a spreadsheet automation tool. It connects to Google Sheets, Excel, and Airtable. Core functionality: watch spreadsheets for changes, run transformations on cell data, sync data between multiple spreadsheet sources, and send notifications based on conditions. Users create automations through a visual node-based editor rather than code. Common use cases include consolidating data from multiple sheets into one, auto-populating templates when source data changes, and validating data against rules. Has a REST API for programmatic access. Data transformations support filtering, mapping, lookups, and basic aggregations.
hi, i'm daniel. i'm a 16-year-old high school senior. in my free time, i hack billion dollar companies and build cool stuff.
about a month ago, a couple of friends and I found serious critical vulnerabilities on Mintlify, an AI documentation platform used by some of the top companies in the world.
i found a critical cross-site scripting vulnerability that, if abused, would let an attacker to inject malicious scripts into the documentation of numerous companies and steal credentials from users with a single link open.
(go read my friends' writeups (after this one))
how to hack discord, vercel, and more with one easy trick (eva)
Redacted by Counsel: A supply chain postmortem (MDL)
🆕 Update: See more extensive repo here: https://github.com/marckohlbrugge/unofficial-37signals-coding-style-guide
This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.
Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.
| print "\e[?25l" | |
| rows, cols = `stty size`.split.map(&:to_i) | |
| drops = Array.new(cols) { rand(rows) } | |
| chars = ("0".."9").to_a + ("A".."Z").to_a + ("a".."z").to_a | |
| loop do |
name: tester description: Use this agent when you need to write RSpec tests for new functionality, including feature specs for user workflows and unit tests for models, services, or other classes. Examples: Context: User has just implemented a new authentication feature and needs comprehensive test coverage. user: 'I just added magic link authentication to the User model. Can you write tests for this?' assistant: 'I'll use the rspec-test-writer agent to create comprehensive tests for your magic link authentication feature.' Since the user needs RSpec tests written for new functionality, use the rspec-test-writer agent to create appropriate test coverage. Context: User has created a new controller action and wants to ensure it's properly tested. user: 'I added a new endpoint for project time tracking. Here's the controller code...' assistant: 'Let me use the rspec-test-writer agent to write feature specs and controller tests for your new time tracking en
| def fix_encoding(str) | |
| # The "b" method returns a copied string with encoding ASCII-8BIT | |
| str = str.b | |
| # Strip UTF-8 BOM if it's at start of file | |
| if str.byteslice(0..2) == "\xEF\xBB\xBF".b | |
| str = str.byteslice(3..-1) | |
| end | |
| if str.ascii_only? |
