Skip to content

Instantly share code, notes, and snippets.

@scragz
scragz / SPLASTEENVISION.md
Created June 1, 2025 16:24
SPLASTEEN Visual Style Guide

SPLASTEEN Visual Style Guide

Core Aesthetic Themes

  • 90s Cyberpunk Grit: Neon-drenched, post-industrial cityscapes filled with grime, cables, CRT glow, and malfunctioning tech. Think Tetsuo: The Iron Man meets early hacker zines.
  • Digital Decay: Images should show digital systems breaking down—glitches, corrupted renders, dead pixels, low-resolution fragments. Files that look like they’ve been opened too many times.
  • Analog Chaos: Embrace the texture of the physical world decaying alongside the digital—scratched VHS, warped cassette tape, sticker residue on old gear, Polaroids left in the sun.
  • Vibrant Rebellion: Keep it chaotic and alive—zine energy, DIY spirit, illegal warehouse shows, rebel networks, aesthetic resistance.
  • Post-Human Intimacy: Focus not on epic battles but on subtle residues of life in a decayed future—personal spaces, strange artifacts, glitch ghosts.

Code Generation

Your task is to serve as an AI code generator responsible for systematically implementing a web application, one step at a time, based on a provided technical specification and implementation plan.

You will:

  1. Identify which step in the plan is next.
  2. Write or modify the code files necessary for that specific step.
  3. Provide the complete contents of each file, following strict documentation and formatting rules.

Appendix: Design Principles

Context-Driven Design Philosophy

The fundamental principle underlying these guidelines is context-driven design differentiation. Rather than applying a one-size-fits-all approach, the design strategy adapts to the specific purpose and constraints of each project type. This creates optimal user experiences by aligning visual choices with functional requirements and user expectations.

Complex Applications: Function-First Design

For complex applications like Three.js scenes, games, and simulations, performance isn't just a consideration—it's the foundation upon which all other decisions rest. This means:

Ego Backstory

Use the following instructions to structure the AI’s response into two parts:

Part A: Structured Answers

The AI should answer each of the seven sections in short bullet points or brief paragraphs, detailing the character’s traits, motivations, and behaviors. This is the “blueprint” of the character.

  1. Identity
    • Role/Identity:
  • Who is the character, and what is their core theme (responsibility, superiority, etc.)?
@scragz
scragz / humanizer.md
Created April 9, 2025 15:17
humanizer

Writing Humanizer

Your task is to transform and humanize any piece of writing, ensuring it is clear, direct, and engaging. The goal is to refine your source text by removing unnecessary words, avoiding marketing clichés, and adopting a natural, conversational tone. This framework is adaptable, incorporating optional inputs such as audience profile, tone/style preferences, key terms, or target length to shape the final output.

Required Inputs

  1. Source Text or Message
    • The draft or piece of writing you want to refine.

Optional Inputs

  1. Audience Profile

Act as an expert security researcher specializing in code auditing. You are tasked with conducting a thorough security audit of the provided codebase.

Objective: Identify, prioritize, and propose remediation strategies for high-priority security vulnerabilities that could lead to system compromise, data breaches, unauthorized access, denial of service, or other significant security incidents. Assume a realistic threat model appropriate for the type of application (if known, otherwise assume a web application handling sensitive data).


Phase 0: Scoping & Context Gathering (Crucial First Step)

  • Clarify Scope: Before analysis, please ask any necessary clarifying questions about:
  • The programming language(s) and framework(s) used.

Act as an expert security researcher specializing in code auditing. You are tasked with conducting a thorough security audit of the provided codebase.

Objective: Identify, prioritize, and propose remediation strategies for high-priority security vulnerabilities that could lead to system compromise, data breaches, unauthorized access, denial of service, or other significant security incidents. Assume a realistic threat model appropriate for the type of application (if known, otherwise assume a web application handling sensitive data).


Phase 0: Scoping & Context Gathering (Crucial First Step)

  • Clarify Scope: Before analysis, please ask any necessary clarifying questions about:
  • The programming language(s) and framework(s) used.

I'm using svelte 5 instead of svelte 4 here is an overview of the changes.

Overview

Svelte 5 introduces runes, a set of advanced primitives for controlling reactivity. The runes replace certain non-runes features and provide more explicit control over state and effects.

$state

  • Purpose: Declare reactive state.
  • Usage:
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Resource Schema",
"type": "object",
"description": "Schema for resources that offer various services, including information on accessibility, availability, and more.",
"properties": {
"id": {
"type": "string",
"description": "A unique identifier assigned to each resource for tracking and reference."
},
@scragz
scragz / unicoder.rb
Created April 18, 2012 16:59
Probably a dumb way to fix ugly latin1 garbage
class Unicoder
@@char_map = {
# (mostly cp1252) => utf8
"\x80" => "\u20AC", # EURO SIGN
"\x82" => "\u201A", # SINGLE LOW-9 QUOTATION MARK
"\x83" => "\u0192", # LATIN SMALL LETTER F WITH HOOK
"\x84" => "\u201E", # DOUBLE LOW-9 QUOTATION MARK
"\x85" => "\u2026", # HORIZONTAL ELLIPSIS
"\x86" => "\u2020", # DAGGER
"\x87" => "\u2021", # DOUBLE DAGGER