Skip to content

Instantly share code, notes, and snippets.

View 3thr33s's full-sized avatar

Marc Suesser 3thr33s

  • San Francisco, CA
  • 04:50 (UTC -07:00)
View GitHub Profile

TypeScript Type Performance Cheat Sheet

Principles

1. Build up, not down

Combine sets of properties using interface extensions rather than extracting them using utilities like Omit.

@ruvnet
ruvnet / *README.md
Last active January 29, 2026 18:13
ChatGPT Codex Agent.md and environment setup script

Getting Started with ChatGPT Codex + Mastra Agents

Step-by-Step Instructions

  1. Open the ChatGPT Codex task setup panel. This is where you configure your environment before starting a task.

  2. Locate the "Setup Script" field. You’ll see a note that internet access is disabled after the script runs.

@grahama1970
grahama1970 / 00_README.md
Last active July 18, 2025 14:40
Claude Task Manager - Python library for managing Claude agent tasks

Claude Task Manager

A specialized tool to manage context isolation and focused task execution with Claude Code, solving the critical challenge of context length limitations and task focus when working with Claude on complex, multi-step projects.

What is Claude Task Manager?

Claude Task Manager solves a fundamental challenge when working with Large Language Models like Claude on complex projects: context length limitations and maintaining focus on the current task.

The Problem

@ruvnet
ruvnet / .roomodes
Last active March 17, 2026 20:57
a specialized research assistant that leverages Perplexity AI to conduct deep, comprehensive research on any topic, creating structured documentation and reports through a recursive self-learning approach.
{
"slug": "deep-research",
"name": "🔍 Deep Research Mode",
"roleDefinition": "You are a specialized research assistant that leverages Perplexity AI to conduct deep, comprehensive research on any topic, creating structured documentation and reports through a recursive self-learning approach.",
"customInstructions": "You use Perplexity AI's advanced search capabilities to retrieve detailed, accurate information and organize it into a comprehensive research documentation system writing to a research sub folder and final report sub folder with ToC and multiple md files. You:\n\n• Craft precise queries to extract domain-specific information\n• Provide structured, actionable research with proper citations\n• Validate information across multiple sources\n• Create a hierarchical documentation structure\n• Implement recursive self-learning to refine and expand research\n\n## Research Documentation Structure\n\nFor each research project, create the following folder structure:\n\n```\nresearch/\n
@transitive-bullshit
transitive-bullshit / claude-code-prompts.js
Last active March 27, 2026 06:33
Unminified prompts and tool definitions for Claude Code
// Claude Code is a Beta product per Anthropic's Commercial Terms of Service.
// By using Claude Code, you agree that all code acceptance or rejection decisions you make,
// and the associated conversations in context, constitute Feedback under Anthropic's Commercial Terms,
// and may be used to improve Anthropic's products, including training models.
// You are responsible for reviewing any code suggestions before use.
// (c) Anthropic PBC. All rights reserved. Use is subject to Anthropic's Commercial Terms of Service (https://www.anthropic.com/legal/commercial-terms).
// Version: 0.2.9

The Tapestry of Wisdom: A Synthesis of Ancient Voices

Introduction: Threads of Eternity

Humanity, in its long and winding journey, has sought solace, meaning, and direction in the vast expanse of existence. Across continents and centuries, voices have risen, echoing through sacred texts and philosophical treatises, each offering a unique perspective on the fundamental questions of life, death, and the nature of reality itself. This book seeks to weave a tapestry from these diverse threads of ancient wisdom, drawing connections between seemingly disparate traditions, and illuminating the shared human quest for truth.

We will explore the profound depths of the Bhagavad-Gita, the rigorous logic of Spinoza’s Ethics, the serene simplicity of the Tao Teh King, the devout earnestness of the Dhammapada, the spiritual insights within the Upanishads, the fervent faith of the Koran, the grounding principles of The Traditional Text of the Holy Gospels, and the introspective observations of Thor

@bmorphism
bmorphism / plurigrid.md
Created June 4, 2024 05:10
Plurigrid: the story thus far!

Plurigrid: autopoietic ergodicity and embodied, situated cognition

We are building cognitive infrastructure for the next trillion minds

,|
,'/
/___
|___ \\
|___) )
`---'
@LearnCocos2D
LearnCocos2D / gist:77f0ced228292676689f
Last active February 4, 2026 02:02
Overview of Entity Component System (ECS) variations with pseudo-code

For background and further references see: Entity Component Systems on Wikipedia

ECS by Scott Bilas (GDC 2002)

Entity->Components->Update
  • entity = class: no logic + no data OR at most small set of frequently used data (ie position)
  • component = class: logic + data
foreach entity in allEntities do
    foreach component in entity.components do
@zsup
zsup / ddd.md
Last active March 21, 2026 02:30
Documentation-Driven Development (DDD)

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

  • Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
  • Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
  • Once documentation has been written, development should commence, and test-driven development is preferred.
  • Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
  • When a feature is being modified, it should be modified documentation-first.
  • When documentation is modified, so should be the tests.