[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f387rf6k9r7mzv":3},{"code":4,"message":5,"data":6,"timestamp":38},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":22,"summary_md":23,"topic":24,"github_topics":27,"license":28,"homepage":29,"updated_at":30,"history":31},"Nutlope\u002Fhallmark",4,"Anti-AI-slop design skill for Claude Code, Cursor, and Codex.","CSS",32153,1653,455,180,[16],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},49058547,"Hallmark – Anti-AI-Slop Design Skill for Claude Code, Cursor, and Codex",7,9,"2026-07-26","A design skill for coding agents that blocks the visual tells of AI-generated pages and ships themes instead.","## The problem\n\nAsk Claude Code, Codex, Cursor or OpenCode to build a landing page and you get the same page again: eyebrow label above every heading, tracked capitals, one coloured word in the headline, a hero that does not fit the first screen, and a newsletter box at the bottom. The output is functional and instantly recognisable as machine-made. Hallmark attacks this at the prompt layer: it gives the agent a curated theme catalog, a page anatomy derived from what the visitor is there to do, and a browser-based lint pass against those specific tells before anything ships.\n\n## What's different\n\nMost attempts at \"make AI output look good\" are prompts pasted into a system message or a component library the agent has to be told to use. Hallmark is a skill package with state: a deal of three themes from forty-eight single-file materials, a pre-flight that reads the existing project (fonts, palette, framework) and asks for real assets instead of inventing them, and `sloplint`, which renders the page at eight widths in a real browser and fails on the specific patterns it targets. The three-tier gate model (Floor never ships, Reflex can be overruled on the record, Finish never blocks) is a more honest version of \"design rules\" than a flat checklist. It also ships redesign and audit paths that verify every link, field and handler survived the rebuild.\n\n## Who it's for\n\nDevelopers who use a coding agent for marketing pages, docs landing screens or small product sites and are tired of reviewing the same template. It fits solo builders and small teams without a designer. It is a poor fit for teams with an existing design system: the forty-eight themes are opinionated materials and a full redesign will fight your tokens. It is also not a general UI library and does not help inside an app's component work.\n\n## Cost of adoption\n\nInstall is `npx skills add nutlope\u002Fhallmark -g`; Node 18+ is required, and the browser checks need puppeteer-core plus Chrome, without which only static checks run. Output is self-contained HTML and CSS, so integrating into a React codebase is manual. The photo library lists Wikimedia Commons images with per-image licences that must be honoured; stock sites are deliberately excluded. MIT licence, no vendor lock. Maturity is the main risk: the README is detailed but describes a young, fast-moving skill format tied to specific agent harnesses.\n\n## Verdict\n\nHallmark is a brand-new project, created in April 2026 and at roughly 32k stars within six months, with a single day on the trending board and a quiet Hacker News thread. That shape — huge star count, thin external discussion — suggests a launch spike rather than established adoption, so treat the star number as attention, not proof. The idea is genuinely useful and the lint-in-a-real-browser approach is the right instinct. The thing to watch is whether the theme catalog and gate rules keep up as agent harnesses change their skill formats.",{"slug":25,"name":26},"developer-tools","Developer Tools",[],"MIT","https:\u002F\u002Fwww.usehallmark.com\u002F","2026-10-24T20:36:11Z",[32,36],{"date":33,"stars":34,"stars_gained":35},"2026-10-24",32105,570,{"date":37,"stars":11,"stars_gained":13},"2026-10-25",1792890697]