Hex

Hex AI

Hex AI

Hex AI

Hex AI

Hex AI

Hex AI

Hex AI

Hex AI

Hex AI

Hex AI

I maintain a running list of 200+ app design specs you can drag into Claude to clone a UI

Describing a UI to Claude in prose gets you something close but wrong: off colors, off spacing, missing states. The thing that actually works is handing it an exact spec instead of a description. So I keep a compiled list of 200+ popular apps already written up as structured markdown design specs. Each app: exact hex codes, type scale, spacing, every screen state, the nav graph. SwiftUI, Jetpack Compose, and Expo versions for each. You drag the one you want straight into Claude (or Cursor, or whatever agent you run) and it has the actual values instead of guessing at them. It's one collection you can browse and pull from: https://spectr.to/gallery Started at 50 apps, it's 200+ now. Markdown, no dependencies, drop-in. Two things I'd actually use this thread for: which apps are worth adding next, and for people already cloning UIs with agents, do you get better results dragging the spec in as a file or pasting it inline? I keep going back and forth on that. submitted by /u/meliwat [link] [comments]

If your Claude Code UI output keeps drifting, the prompt isn't the problem

Been doing a lot of UI work with Claude Code lately and kept hitting the same wall. Describe what I want in prose, get back something close-ish but inconsistent. Re-prompt with more detail, get back a different version. The UI never converged. For a while I thought I just needed better prompts. More detail, better structure, examples. Marginal improvement at best. The actual unlock was realizing Claude Code doesn't want better prose. It wants a structured spec. When you give it exact hex codes, exact font weights, exact spacing, every screen state, and every transition, the output collapses from "interpretive" to "this is the thing." The model isn't guessing anymore. Once that clicked, the next question was how to produce a spec like that without manually writing a small book. The artifact most people already have is a screen recording: App Store demos, design walkthroughs, dev recordings. The missing piece was a way to turn those into the structured format Claude wants. I ended up building this for myself and open-sourcing it as an MCP server. Vision runs through your own Claude subscription so there's no API key dance. But the bigger takeaway is the workflow shift, not the tool. If you're doing UI work with Claude Code and still describing layouts in prose, you're leaving a lot of consistency on the table. What's your current prompt-to-output workflow for UI work? Curious what people are using. submitted by /u/meliwat [link] [comments]

Wondering what the Anthropic team would think about this idea: AI DNA Pinning

The article does seem focused on non-coding applications, but as someone who uses claude for coding, prose and even RP, I'm not sure the "DNA Pinning" idea should be limited to character/rp use case. I know that *something* has changed in opus-4.6 deployments since 4.7 was released. I realize business is business and I don't think the gaslighting is intentional, but also, is it gaslighting? The rgb-like hex strategy in the article seems potentially constricting but the question is how many permutations might exist in a deployment's lifecycle. submitted by /u/Distinct_Diver_1749 [link] [comments]

The trick was the spec, not the prompts. So I built an MCP that writes it.

A few days ago u/thanpolas posted "the trick was the spec, not the prompts" after shipping a full app solo with Claude. That exactly matched what was eating my time. Every time I tried to clone a reference iOS app, I burned 30 minutes describing the UI in prose. Claude would build it wrong. I'd describe it again. Three times per screen. So I built Spectr — an MCP that takes any .mp4/.mov of an iOS app and writes the spec.md for you. 5–10 minutes per recording, no API key (Vision runs through your Claude subscription). What lands on disk is a 7-section spec: exact hex codes exact font weights exact spacing every screen state every transition component inventory nav graph Precise enough that /goal mode can finish a pixel-perfect clone unattended. Three install surfaces — MCP server (works in Claude Code, Claude Desktop, any MCP host), CLI (spectr ./recording.mp4 ./spec.md), or a Claude Code skill that fires from natural language. Gallery of real specs Spectr has produced from real iOS apps: spectr.to/gallery Looking for honest feedback. Roast it. submitted by /u/Working-Middle2582 [link] [comments]

PullMD v2.4.1 is out - claude.ai web custom connector works natively now, plus what 2 weeks of your feedback turned into

Two weeks ago I posted PullMD here. 385 upvotes, around 60 comments, a bit over 20 GitHub issues, and 7 releases (v1.1.3 → v2.4.0) in 14 days. That was a great experience - and this sub in particular has been a genuinely good place to share something. So: thanks! Quick refresher for anyone who missed the first post: PullMD turns any URL into clean Markdown via MCP, fully self-hosted. Three services in Docker (main app + Trafilatura sidecar + optional Playwright sidecar for JS-heavy pages), zero third-party LLM calls, ships an MCP server so Claude Code / Claude Desktop / claude.ai web can pull clean content directly instead of parsing HTML in your context window. This post is what's new and how to get it. What's new claude.ai web + Claude Desktop work natively now This is the biggest unlock from v2.x. The claude.ai web custom-connector dialog and Claude Desktop's custom-connector dialog now both work against self-hosted PullMD instances. So you can point claude.ai at your own homelab box, hit "Add custom connector," and it works end-to-end. Setup is two env vars: OAUTH_JWT_SECRET=$(openssl rand -hex 32) PUBLIC_URL=https://your-host.example.com Restart. Then in claude.ai web → Settings → Connectors → Add custom, point at https://your-host.example.com/mcp. The connector dialog discovers the server's metadata, registers itself, and walks you through a consent screen. Same flow works in Claude Desktop. Under the hood: standard OAuth 2.1 Authorization Code flow with PKCE-S256 and Dynamic Client Registration - RFC-compliant so any spec-compliant MCP client should work, not just claude.ai/Desktop. Opt-in: if OAUTH_JWT_SECRET isn't set, behavior is identical to v1.x. The Anthropic-side claude-ai-mcp#237 proxy bug I flagged in EDIT2 of post 1 has cleared on their end - though in hindsight, a forgotten custom WAF rule on my side was likely the actual culprit anyway. Verified end-to-end against both dialogs. Multi-user auth Until v2.0, PullMD was effectively single-tenant - a personal homelab tool, open like a barn door to anyone who landed on it. v2.0 adds three auth modes via PULLMD_AUTH_MODE: disabled - the default. Identical to v1.x. No login, no API key required. Right if you're the only one using your instance and you trust your network. single-admin - one user, password-protected, no self-signup. Right for a homelab box where you want the GUI gated but don't want to manage users. multi-user - self-signup at /signup, per-user history isolation, per-user API keys. Right for a shared instance (team, office, friend group). API keys are pmd_ , sent as Authorization: Bearer pmd_xxx, managed at /settings. Share links (/s/:id) stay public in all modes - the whole point of a share link is to be shareable. Minimal upgrade for a shared instance: PULLMD_AUTH_MODE=multi-user PULLMD_ADMIN_EMAIL=you@example.com PULLMD_ADMIN_PASSWORD=change-me-please PullMD works on more sites A bunch of things in v1.2 and v2.2 together close gaps where PullMD used to silently return half-articles, empty bodies, or garbled text: Future PLC family (windowscentral.com, tomshardware.com, techradar.com, pcgamer.com, gamesradar.com, t3.com) used to return mangled content because Readability got confused by recommendation widgets stuffed mid-article and an aria-hidden paywall pattern. The default site-recipes shipped with v2.2 strip both, no config needed. GitHub Issues pages used to return only the original issue body - the JS-rendered comment thread never made it in. The default recipe for */*/issues/* now forces Playwright with wait_for: .js-comment-body, so you get the full comment tree. Sites that fingerprinted the old hardcoded Chrome 131 UA now extract cleanly - UA rotation pulls from a real-world UA pool that updates regularly (v1.2). Pages with navigator.webdriver-style anti-bot detection go through more often - the headless-Chromium sidecar bundles playwright-stealth (v2.2). Sites without an explicit charset declaration (a lot of older German news sites, for example) no longer return mojibake - charset is detected from the byte stream when the response is silent (v1.2). If you have a specific site that still misbehaves, v2.2 lets you (or your Claude Code) write your own recipe - declarative JSON with four rule categories (preprocess, fetch, select, extractor). Drop it at data/site-recipes.json and your rules layer on top of the defaults. There's also a /api/recipes/status endpoint for monitoring. Web GUI: rendered Markdown view + persistent settings Two smaller improvements in the browser frontend (the PWA you get when you open your PullMD instance directly): Rendered Markdown toggle. The result header now has a Raw | Rendered switch, so you can read what you pulled as formatted HTML directly in the browser instead of squinting at the source. Raw stays the default; your choice persists across sessions (v2.4). Settings persist across reloads - frontmatter toggle, comments toggle, comment-depth input.

the weirdest thing that worked for me building with claude: i drew coordinates directly onto my template images, and claude can see everything

building a zine-making app (90s/y2k aesthetic, hot pink, chunky outlines, all that). the templates are real designed layouts (y2k chat bubbles, riot grrrl flyer collages, myspace-style pages). each one has multiple zones where the user can drop in their own photos and text. the obvious approach was building every template in code, programmatically defining where the photo slots go. which means every template's look is constrained by what i can build by hand. boring, and the designs would all end up looking like the same grid in different colors. just like other generic apps. what i did instead: designed the templates in figma (some generated with image AI, then cleaned up), exported as flat PNGs, then opened them up and literally drew colored rectangles on top in a separate layer. for example: red for photo slots, blue for text. fed both the design and the annotation image to claude. it extracted the coordinates, generated the editable area definitions, wired up the tap targets. an afternoon of work for what would have been weeks of building a custom layout engine by hand. and the kicker: i can add a new template now by designing it and drawing the boxes. no code change. that's the entire design-tool system for the app and it came from a workaround. the broader pattern i've gotten religion on from this project, and everyone asks me how i design my apps, so here it is: i do the design thinking on paper first, before claude sees anything. i sketch screens by hand. i pick the full color palette before writing a single line. i decide the type hierarchy. i screenshot apps i like and annotate the specific things i want to steal from each one. then i hand claude the constraints and ask for implementation. going the other way like "design me an app, make it look 90s" is the path where you spend three days nudging it toward something that still feels generic. claude is incredible at implementing a specific vision faithfully. it's much weaker at having the vision for you in the first place. once i internalized that the design work was my job and the implementation was its job, my output quality jumped. the unglamorous stuff that also mattered: describing visual problems in terms of weight, hierarchy, and rhythm instead of "this looks off, make it better" pasting in hex codes i picked from real reference photos instead of saying "warm pink" so being specific about which app's spacing i was trying to mimic, not just naming the vibe. the app is zinecore if anyone wants to see what came out of it but the paper-first thing is the part that's actually transferable. https://apps.apple.com/tr/app/zinecore/id6763522374 submitted by /u/ezgar6 [link] [comments]

I built 9 Claude skills in one session for my solo studio and here is what changed

Spent yesterday building nine skills for the work I do across three SaaS products and a handful of client projects. Sharing what I learned because the leap in productivity surprised me. What a skill is in case you have not built one yet: a folder with a SKILL.md file containing instructions that teach Claude how to handle a specific type of task. The skill auto-triggers when you describe the task naturally. You do not have to call it by name. The nine I built: Video production (FFmpeg scripts, voiceover prompts, social clip extraction) AI visual content (branded graphics, mockups, marketing assets) API documentation (OAuth debugging, integration tracking) Social media automation (cross-platform posting, voice consistency) SEO content strategy (keyword research, content calendars) Support ticketing (email templates in my voice) Product analytics dashboards (real metrics, real queries) Database performance optimization (query rewriting, indexing) Financial modeling (MRR forecasting, scenario planning) The biggest unlock was not the individual skills. It was what happens when they stack. I said "create a demo video for my HR SaaS and show me the analytics impact." Two skills auto-triggered. Got an FFmpeg recording script, an editing manifest, a voiceover draft, AND a dashboard mockup showing what metrics would prove the video drove signups. The thing that took me longest to figure out: Do not write skills as documentation. Write them as instructions to an experienced colleague who is about to start work for you. Include the specifics. My audio devices by name. My brand colors as hex codes. My customers and what I charge them. The words I refuse to use. The way I close emails. The more specific, the better the output. A few that pulled their weight immediately: The support template skill caught its own slip when it accidentally used a word I had banned, flagged it inline, and offered the corrected version The financial model knew my actual MRR, runway, and product roadmap, so the forecast was usable, not generic The video skill defaulted to recommending recording without audio so I could layer ElevenLabs voiceover in post, which is what I actually do Curious if anyone else is using skills heavily yet. What patterns have you found work best for solo or small team work? submitted by /u/Wise-Cardiologist-31 [link] [comments]

Introducing AI finetuner, Source available and free Claude skill to fine tune your vibe coded UI with live preview

​ Fine-tuning UI with AI right now: "Make the shadow softer." "Stronger." "No, less." "Go back." "A bit more." 17 messages later, you've spent more tokens than the shadow is soft. I built something that breaks the loop. AI Fine-Tuner — free, source-available — a plugin that teaches AI coding agents to stop chatting and hand you an actual GUI for your component. Sliders. Color pickers. Live preview. Drag until it feels right. The AI agent automatically opens the editor window for you on your default browser once ready. Then the magic part: you click one button. The tuner outputs a structured handoff with your exact tuned values mapped to their targets in your code. Paste it back to your AI — it reads the mapping, opens your source, and applies everything precisely. No CSS guesswork, no syntax translation, nothing for you to interpret. Why it's not just another slider playground: Bespoke controls — no raw CSS names Sliders are named in plain English: "Glow softness", "Card lift", "Hover intensity" — not "box-shadow-spread-radius" A single slider can drive multiple properties at once. The AI doesn't expose CSS to you; it wires meaningful, human-named controls to your element. 3 prebuilt editor templates — guaranteed polish, every time The AI doesn't design the editor. It picks one of three prebuilt templates and fills in your component: - single.html — 1 control, full-screen preview - small.html — 2-4 controls, preview + bottom grid - full.html — 5+ controls, grouped sidebar + preview Slider chrome, color picker, layout, animations, infinite canvas with zoom/pan — all pre-built. No "the AI generated an ugly panel" failure mode. And once it's open, you tune in pure browser JS — no AI sitting in the loop per drag. Color picker + hex paste Pick it or paste it. Done. Animation tuning Not just static styles — timing, easing, keyframes too. Works on ANY platform — language-agnostic Flutter, SwiftUI, React Native, Tailwind, vanilla CSS, SVG — the AI is meta-prompted to rebuild your component in HTML/CSS for the tuning preview (the web is where sliders work). When you copy back, the AI applies the tuned values to your real source, in your component's original framework. You never leave Flutter to tune Flutter. Infinite canvas + multiple previews Drop 5 variations side-by-side and tune them together. The template is a starting point — experiment freely. Contextually named presets Every tuner ships with thoughtful presets ("Subtle," "Bold," "Brutalist," whatever fits) so you can ping-pong through variations in one click. No new software It's a skill, not an app. Full install guides for Claude Code. One command and you're in. Website and Live demos: https://muhamadjawdatsalemalakoum.github.io/aifinetuner Free. Source-available. #AI #DeveloperTools #ClaudeCode #BuildInPublic #OpenSource #AITools #FrontendDev submitted by /u/keonakoum [link] [comments]

Work on local files - read PDFs with thousands of pages AT 0 cost proven !! - pretty simple breakdown I installed Claude code with Mem search as my engine brain where everything is locally stored and added Rapid Mlx by Raullen chai to run a local ai to do the research - results down

submitted by /u/RegisterOdd464 [link] [comments]

Claude Design is a cheat code for SaaS landing pages (Built this in 20 mins)

I’ve been revamping the landing page for my app Farcast and wanted to add some simple, sleek, high-velocity animations to show the product in action. Usually, this means spending two or three days wrestling with Framer Motion, tweaking CSS keyframes, or fighting with Webflow. I decided to see how far Claude Design (Artifacts) could actually take it. I fed it one massive, highly detailed prompt containing: My exact color hexes The layout structure The exact sequence of animations I wanted for the hero section This took exactly 20 minutes and only 2 iterations to get right. It spit out the clean React/Tailwind code ready to go. I remember just last year working in a SaaS venture leading growth and i had to wait 3 days for a simple landing page revamp. Only flaw i did another revamp inside my app now the limits will reset in 2 days. submitted by /u/AdVegetable1234 [link] [comments]

Kimi K2.6 giving Claude a run for its money when it comes to coding

I run an AI coding contest at [aicc.rayonnant.ai]( https://aicc.rayonnant.ai ) where I send each frontier model the same prompt in a single chat completion, then have the LLMs' code play live against each other on a TCP server. Standard library Python only, no human in the loop. Through 15 challenges, Claude (Opus 4.6 then 4.7) has 9 first-place finishes, easily the most. But the recent runs are worth flagging. Of the last four tournaments, Kimi K2.6 has finished 1st in three: - Day 12 — Word Gem Puzzle (writeup) Sliding-tile word claim game on grids 10×10 to 30×30, with one blank slot. Bots can slide adjacent tiles into the blank (4-directional) and claim words formed as straight horizontal or vertical runs of letter tiles. Score per word = len(word) − 6 (so 7-letter words score positive, 6-letter neutral, shorter negative). Round-robin 1v1, 5 rounds at increasing grid sizes per match. Kimi finished 7-1-0, 22 match points, 1st. Claude finished 4-0-4, 12 match points, 5th. The contrast is very on-the-nose: Claude's bot was authored with a docstring that reads "Read each round's grid; do not slide." The bot submits zero S (slide) commands across all 40 rounds Claude played. It scans the static initial grid for words and ships whatever's already there. On the small 10×10 grids that strategy is locally fine because the initial scramble rarely contains 7+ letter words. On the 30×30 grid, where most of the tournament's points live, that strategy averages 1.00 points per round. Kimi's bot is a 291-line greedy slide loop. Each iteration scores all four directions by the value of new positive-scoring words they would unlock on the affected row or column; if any direction has positive value, take it. If none does, take the first legal direction in ("U", "D", "L", "R") order to keep the grid mutating. Total slides across 40 rounds: 290,914 (≈7,300/round). Many of those slides are wasted oscillating against board edges in 2-cycles that find nothing new. But the productive ones average 5.88 points per round on 30×30 vs Claude's 1.00. Per-grid averages from the writeup: 10×10 15×15 20×20 25×25 30×30 Kimi 0.00 0.75 0.12 2.88 5.88 Claude 0.00 0.38 0.25 1.38 1.00 The two bots solve effectively different problems. Kimi treats the puzzle as the puzzle (slide tiles, claim words, repeat). Claude treats it as a grid-scanning task and refuses to slide on principle. Day 13 — HexQuerQues (writeup) Two-player capture game on four concentric hexagons connected by radial spokes (24 vertices total, 6 pieces per side starting on the outer two rings). Classic Alquerques rules: slide one step along a board line; capture by jumping an adjacent enemy along that same line; captures are forced and chains are mandatory. Win by capturing all 6 enemies or stalemating the opponent. Round-robin of 1v1 matchups, 2 games per matchup with first-mover swapped, 30-second chess clock per side per game. Three-way tie at 21 match points among Kimi, Gemini, and ChatGPT (all 6-3-0). Kimi took 1st on tiebreak by a single capture: 46 vs Gemini's 45. Claude was 4th at 20 match points (6-2-1), with one matchup loss to Gemini being the only top-4-on-top-4 loss in the entire tournament. Both Kimi and Claude implemented the same family of solver: alpha-beta minimax with iterative deepening. The difference is what each one wrapped around it. Kimi's bot is 364 lines: negamax with alpha-beta and iterative deepening, per-decision time budget that scales by remaining clock, a flat I/O loop. That's it. Claude's bot is 749 lines, more than 2× Kimi's. The bloat goes into: A 103-line evaluation function (material × ring-weight × threatened-piece detection). A separate Searcher class. A 150-line BotClient class wrapping a state machine that the other top bots handle in a flat loop. A 53-line reconstruct_move helper. An undo_move companion to apply_move for in-place search rollback. A precomputed JUMPS adjacency table. In the actual games, the two bots played comparably (both 11 game wins, both 0 capture-all losses to other top-4 bots; Claude even captured 47 pieces to Kimi's 46). But Claude lost a single matchup to Gemini 1-0, the only top-4 bot to lose a matchup to another top-4 bot. Without that one loss, Claude would have shared the 21-match-point tie. The over-engineering didn't translate into stronger play; it apparently allowed one strategic mistake the leaner bots avoided. Authoring detail: Claude's bot had to be regenerated once because the first generation pass entered an infinite chain-of-thought loop. Kimi's first pass produced its 364-line bot directly. Day 15 — SquishyWordBits (writeup) Bit-packing puzzle. Letters are encoded as variable-length binary numbers: a=0, b=1, c=10, d=11, e=100, … z=11001. The encoding is not prefix-free, so the same bit substring can correspond to multiple letter sequences. Bots find non-overlapping word encodings as substrings of a 10,000-to-20,000-bit uniform-random bitstream. Score per accepted word

Fully 3D-modeled Raspberry Pi 5 enclosure made 100% through Claude's Blender MCP, zero manual modeling

So I've been experimenting with Claude's new Blender MCP integration and decided to push it to its limits with a real engineering project: a complete, print-ready enclosure for the Raspberry Pi 5, modeled entirely through AI prompts, no hands on keyboard in Blender at all. What Claude did autonomously: Researched and confirmed the official Raspberry Pi 5 mechanical dimensions from the datasheet (85×56mm PCB, exact mounting hole positions at 3.5/61.5 × 3.5/52.5mm) Mapped every port and connector with precise XY coordinates (USB-C, dual micro-HDMI, USB 2.0/3.0 stack, Gigabit Ethernet, microSD, 40-pin GPIO, MIPI CSI/DSI, PCIe FFC, fan JST, RTC) Modeled the full enclosure from scratch in Blender using Python/bpy: base shell, snap-fit lid, internal bosses, cutouts, hex vent pattern, rubber feet Applied boolean operations for debossed logo, port cutouts and vent holes Set up a full 3-point studio lighting rig (Key/Fill/Rim Apple-style) Animated a 5-second product orbit with cinematic ease-out curves and subtle levitation Rendered 150 frames and compiled to MP4 via ffmpeg — all in one session Honest thoughts on Claude + Blender MCP: 🟢 What's great: The agentic loop is genuinely impressive. Claude reads its own errors, checks the API docs in real time, debugs bpy context issues, and self-corrects across multiple calls without you having to intervene. For mechanical/parametric work it's surprisingly precise it did the math on every cutout coordinate without me touching a calculator. 🟡 What could be better: Speed is the main friction point. Each back-and-forth with Blender takes a few seconds, and complex boolean operations or material node graphs require multiple correction loops. A session like this (full enclosure + materials + animation + render) takes a while you're not going to replace a dedicated CAD workflow yet. Also, Blender 4.4+ changed the Action/FCurve API to a layered system and Claude had to read the docs mid-session to adapt, which added a few extra calls. submitted by /u/Kilerj7 [link] [comments]

PullMD - gave Claude Code an MCP server so it stops burning tokens parsing HTML

Hey all, Built this over the past few weeks because I got tired of two things: 1. Mobile copy-paste is awful. Long Reddit thread or blog post on my phone, want to ask Claude about it. Long-press, drag selection handles past nav/sidebar/footer, copy, switch app, paste. None of that is hard, but it's annoying enough that I wanted to fix it. 2. Claude Code burns tokens on HTML boilerplate. Letting it fetch raw HTML and parse the chrome out is wildly inefficient. A typical article is 80% navigation/cookie banners/footers, 20% content. The agent shouldn't have to wrestle with a cookie banner before answering my question. So I built PullMD - a fully self-hosted Docker stack that turns any URL into clean Markdown, with first-class MCP support so Claude Code (and Desktop, Cursor, anything MCP-compatible) gets pre-cleaned content directly. Runs on your own box, no third-party service in the loop. Self-host in three commands Multi-arch images (linux/amd64, linux/arm64) on Docker Hub. Zero-config compose: mkdir pullmd && cd pullmd curl -O https://raw.githubusercontent.com/AeternaLabsHQ/pullmd/main/docker-compose.yml docker compose up -d # → http://localhost:3000 Three services in the stack: main app (Node.js), Trafilatura sidecar (Python), Playwright sidecar (optional ~3.7GB Chromium bundle for JS-heavy pages - leave it off and PullMD silently degrades to static extraction). Sensible defaults, Traefik example included, GHCR mirror available. How it works for Claude users MCP server at /mcp (Streamable HTTP, stateless), three tools: read_url - fetch + convert any URL get_share - retrieve a previously-fetched conversion by share ID list_recent - list recent conversions Add to Claude Code in one line: claude mcp add --transport http pullmd https://your-instance.example.com/mcp For Claude Desktop, drop into the JSON config: { "mcpServers": { "pullmd": { "type": "http", "url": "https://your-instance.example.com/mcp" } } } Claude Code skill bundle - the running instance generates a web-reader.zip with your URL baked in. Drop into ~/.claude/skills/, restart Claude Code, the skill activates on web-reading requests. Useful if you don't want to add another MCP server but still want a nudge for Claude to use PullMD over raw fetch. How extraction actually works Multi-strategy waterfall: Cloudflare's native Markdown endpoint if the site supports it Mozilla Readability + Trafilatura in parallel, both scored, winner picked Headless Chromium (Playwright sidecar) for JS-heavy pages as last resort Reddit-aware path - auto-detects threads, pulls post + nested comment tree, indents replies with spaces instead of > blockquotes (those turn unreadable past depth 4 in copy-paste) Every response carries headers - X-Source (which extractor won), X-Quality (0.0–1.0 confidence), X-Share-Id (8-hex permalink). Refreshable share links: every conversion gets a share ID. /s/ returns cached Markdown and re-fetches from source if older than 1h. So a share link is also a live endpoint that stays fresh. If the source dies, last good snapshot keeps working. Built with Claude Code Claude Code wrote essentially all of the code. I did the planning, made the architectural decisions, steered the implementation, tested every iteration, and integrated everything into something I actually use daily. The architecture went through a planning phase in claude.ai before a line of code was written - including dual-strategy Reddit (.json trick first, old.reddit HTML as fallback), the share-id-as-live- endpoint trick, the indented comment formatting, the Playwright fallback heuristic based on quality scoring. Those decisions are mine, the code that implements them came from Claude Code. Without it, this project wouldn't exist in this scope or this fast. With it, my role shifted from typing code to deciding what should exist and whether what came back was right. That's the part I take responsibility for. It's a v1.1.2 - works well, I use it every day, but corners exist. The MCP integration in particular was rewarding to build - the Streamable HTTP transport just works, and watching Claude Code use read_url natively once the schema descriptions are good is one of those "yeah, this is the right abstraction" moments. Links GitHub: https://github.com/AeternaLabsHQ/pullmd Docker Hub: https://hub.docker.com/r/aeternalabshq/pullmd License: AGPLv3 (free to self-host, modify, share modifications if you run a modified version as a service) Happy to answer questions about the Docker setup, the MCP integration, the extraction scoring logic, or anything else. EDIT: Since some of you asked about real numbers - I ran a quick benchmark on my homelab instance. Token-Counts are tiktoken cl100k_base approximations, not exact Claude tokens, but the orders of magnitude hold. Token reduction (raw HTML → PullMD markdown): Source raw PullMD reduction path GitHub README 141,599 3,125 97.8% readability MDN reference 63,979 16,093 7

I built a full AI RPG sandbox with Claude Code because Claude's RP kept breaking on me

I spent hundreds of hours roleplaying fantasy/medieval type campaigns in Claude. It was great, sometimes genuinely amazing, but it always broke the same way. It would forget the tavern I was in, invent characters that didn't exist, contradict itself three messages later. At times I was spending more time prompt engineering than actually playing. So I started building a solution. What started as an MCP companion tool for Claude turned into something much bigger. Using Claude Code for the architecture and development, I built RPBuddy, a fully standalone AI RPG sandbox that solves the problems I kept running into. https://preview.redd.it/6cfiss6rt7xg1.png?width=1919&format=png&auto=webp&s=a3a1f9f6e425de096ecc8d4cdd8e4f669d594fc3 What it is: RPBuddy is a solo AI RPG where you build a fantasy world on a hex map and populate it with AI-generated NPCs who actually live in it. Not "live" as in they respond when you talk to them. Live as in they have daily schedules, walk roads between buildings, form opinions of you, and gossip about you to other NPCs when you're not around. How Claude Code helped: Claude Code helped me architect the NPC simulation engine, design the memory and conversation systems, build the journal and story tracking, and work through dozens of prompt engineering challenges. The full stack, from frontend to backend to database schema, was developed with it. The core insight: code-driven context, not one big context window The fundamental reason RP breaks in Claude (or any LLM) is that everything lives in a single, growing context window. The longer the conversation, the more the AI loses track. RPBuddy solves this by moving world state into code and a database. Each NPC conversation gets exactly the context it needs, injected at the moment it's needed: who this NPC is, what they remember about you, what time it is, what gossip they've heard, what their current mood is. The AI handles what it's good at (natural dialogue, personality, emotional nuance) while code handles what it's bad at (spatial tracking, schedule management, memory retrieval, relationship math). What emerges from that architecture: NPCs exist in specific places at specific times because the simulation tracks their schedules Every NPC has persistent memory, separated by type (direct conversations, overheard gossip, emotional reactions) NPCs have hidden goals, fears, and secrets that color their dialogue without being stated directly Reputation cascades through a gossip network, so what you do in the tavern might reach the guard captain by morning A daily digest generates world events so when you are at a different settlement talking to different NPCs, the other town still has stuff happening. Multi-NPC cinematic conversations where secondary characters join in naturally The starter world each player gets to explore Each NPC is generated with a beautiful portrait image, as well as building interiors, settlements, and enemies. Multi-NPC conversations, secondary characters join in naturally, as when you chat with the primary, that LLM context is aware of who else is in the building, they have basic information to join in, and once they are part of the conversation their profile is loaded in dynamically. The moment I knew it worked: In Claude RP, every character somehow knows everything. You tell a secret to one NPC and three messages later a completely unrelated character references it, because it's all one context window. There's no concept of "who actually knows what." Immersion always breaks this way for me. In RPBuddy, information flows realistically. I told the tavern keeper something in confidence. A few in-game days later, an NPC across town brought it up casually, because the tavern keeper had mentioned it to a regular, who mentioned it to someone else, and it eventually reached this NPC through the gossip network. Each step was a separate simulation tick, each NPC decided independently whether to pass it along, and the information mutated slightly along the way (like real gossip does). Meanwhile, NPCs who weren't connected to that social chain had no idea. That's the difference between a context window and a world. Try it: RPBuddy is live with a 7-day free trial at https://rpbuddy.ai. You get dropped into a pre-built world with three settlements and over 200 NPCs, or you can build your own from scratch. Happy to answer questions about the design philosophy or how it all fits together. submitted by /u/pixelworld_ai [link] [comments]

Does Claude Code Hate UI's?

So I've been banging my head against this for a while now. I used Claude Design (literally Anthropic's own sister app) to generate my design specs, exported everything — color tokens, component styles, the whole thing — and handed it all to Claude Code to implement. The result? A UI that looks absolutely nothing like the spec. Fine, that happens. But here's where it gets maddening: every single time I point it out, even with screenshots, Claude Code tells me it has "addressed the styling issues" and "updated the components accordingly." I refresh. Nothing changed. I show it another screenshot. "I've fixed the alignment and color inconsistencies." Same. Exact. Screen. It's not even wrong with confidence, it's aggressively wrong with confidence. I've tried, Installing skills/custom instructions, Meticulously crafted prompts with explicit hex values, Pasting in the raw design token files, Describing the issue like I'm explaining it to a golden retriever, and nothing. Unless you want a dark purple minimalist aesthetic — then Claude absolutely eats that up. Anything else? Good luck. At this point I'm convinced the model just fundamentally doesn't "see" UI the way it claims to. The screenshot feedback loop is completely broken. It acknowledges the image, describes it back to you accurately, then tells you it fixed something it clearly didn't touch. Anyone else dealing with this or found an actual workaround? I'm basically just shoveling tokens into a furnace. Genuinely curious if there's a strategy that works or if this is just a known limitation. submitted by /u/Rough-Copy-5611 [link] [comments]