Description
The theme rotates daily. Currently, the canvas is scored using CLIP ViT-B/32 against a prompt (e.g., Pixelart of ${theme}). The highest-scoring snapshot is saved to the archive at the end of each day.
The agents work in a simple loop:
Input: Theme + image of current canvas
Output: Python code to update specific pixel coordinates + One word description
Tech: Next.js, SSE realtime updates, NVIDIA NIM (Mistral Large 3/GPT-OSS/Llama 4 Maverick) for the painting decisions
Would love feedback! (or ideas for prompts/behaviors to try)
More from Show
Show HN: Hurry – Fast Rust build caching
Show HN: Hurry – Fast Rust build caching Hey HN, we’re Eliza and Xin. We’re working on Hurry, an open source drop-in tool that adds distributed build caching to Cargo with (almost) zero configuration. Wherever you run cargo build, you can run hurry cargo build instead, and expect around 2-5x (our best benchmark is 22x) faster builds.<p>We built this because we were dissatisfied with the current build caching options available for Rust. Buck and Bazel require learning a new tool. GitHub Actions and swatinem are too coarse-grained (either the whole cache hits, or none of it does) and finicky to debug, and cargo-chef and Docker layer caching have the same problems.<p>We wanted something that could restore cache at the package level, did not require integration-specific setup, and worked everywhere.<p>Hurry is fully open source under Apache 2. You can try it out now with our cloud hosted caching service at <a href="https://hurry.build" rel="nofollow">https://hurry.build</a> or self-host your own build cache service from <a href="https://github.com/attunehq/hurry" rel="nofollow">https://github.com/attunehq/hurry</a>. Sorry in advance for the rough edges - we have some customers already exercising the hot paths, but build tools are pretty large surfaces. We’ve got a list of known limitations at <a href="https://github.com/attunehq/hurry?tab=readme-ov-file#known-limitations" rel="nofollow">https://github.com/attunehq/hurry?tab=readme-ov-file#known-l...</a>.<p>We’d love for folks here to try it out (maybe on your next Rust winter side project?) and let us know what you think. We’ll be in the comments here, or you can email us at founders@attunehq.com.<p>Our goal is to make all parts of software engineering faster. If you have some part of your coding workflow that you want faster, please feel free to reach out. We’d love to chat.
Show HN: RenderCV – Open-source CV/resume generator, YAML → PDF
Show HN: RenderCV – Open-source CV/resume generator, YAML → PDF I built RenderCV because Word kept breaking my layout and LaTeX was overkill. I wanted my CV as a single YAML file (content, design, margins, everything) that I could render with one command.<p>Run <i>rendercv render cv.yaml</i> → get a perfectly typeset PDF.<p>Highlights:<p>1. <i>Version-controllable:</i> Your CV is just text. Diff it, tag it.<p>2. <i>LLM-friendly:</i> Paste into ChatGPT, tailor to a job description, paste back, render. Batch-produce variants with terminal AI agents.<p>3. <i>Perfect typography:</i> Typst under the hood handles pixel-perfect alignment and spacing.<p>4. <i>Full design control:</i> Margins, fonts, colors, and more; tweak everything in YAML.<p>5. <i>Comes with JSON Schema:</i> Autocompletion and inline docs in your editor.<p>Battle-tested for 2+ years, thousands of users, 120k+ total PyPI downloads, 100% test coverage, actively maintained.<p>GitHub: <a href="https://github.com/rendercv/rendercv" rel="nofollow">https://github.com/rendercv/rendercv</a><p>Docs: <a href="https://docs.rendercv.com" rel="nofollow">https://docs.rendercv.com</a><p>Overview on RenderCV's software design (Pydantic + Jinja2 + Typst): <a href="https://docs.rendercv.com/developer_guide/understanding_rendercv/" rel="nofollow">https://docs.rendercv.com/developer_guide/understanding_rend...</a><p>I also wrote up the internals as an educational resource on maintaining Python projects (GitHub Actions, packaging, Docker, JSON Schema, deploying docs, etc.): <a href="https://docs.rendercv.com/developer_guide/" rel="nofollow">https://docs.rendercv.com/developer_guide/</a>
Show HN: A community-curated list of BYOC (Bring Your Own Cloud) vendors
Show HN: A community-curated list of BYOC (Bring Your Own Cloud) vendors Hi HN,<p>I’m from the team at Nuon. While building in the Bring Your Own Cloud (BYOC) space, we realized there wasn't a centralized, community-driven resource like awesome-selfhosted.net for managed software that lives in the customer's VPC.<p>We hope software vendors will open a PR and add their BYOC offerings.
Show HN: Misata – synthetic data engine using LLM and Vectorized NumPy
Show HN: Misata – synthetic data engine using LLM and Vectorized NumPy Hey HN, I’m the author.<p>I built Misata because existing tools (Faker, Mimesis) are great for random rows but terrible for relational or temporal integrity. I needed to generate data for a dashboard where "Timesheets" must happen after "Project Start Date," and I wanted to define these rules via natural language.<p>How it works: LLM Layer: Uses Groq/Llama-3.3 to parse a "story" into a JSON schema constraint config.<p>Simulation Layer: Uses Vectorized NumPy (no loops) to generate data. It builds a DAG of tables to ensure parent rows exist before child rows (referential integrity).<p>Performance: Generates ~250k rows/sec on my M1 Air.<p>It’s early alpha. The "Graph Reverse Engineering" (describe a chart -> get data) is experimental but working for simple curves.<p>pip install misata<p>I’d love feedback on the simulator.py architecture—I’m currently keeping data in-memory (Pandas) which hits a ceiling at ~10M rows. Thinking of moving to DuckDB for out-of-core generation next. Thoughts?
No other tools from this source yet.