457 karma · joined April 15, 2013
> We helped prepare the manuscripts and formalize the proofs in Lean, and we take responsibility for their correctness
Offering to take responsibility for the correctness of a proof written in Lean feels like volunteering to be the fall guy in case someone finds a flaw in basic arithmetic, no?
> description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
> - *PREMIUM-CONSUMER PALETTE BAN (mandatory, second-most-recurring AI-tell):* - For premium-consumer briefs (cookware, wellness, artisan, luxury, heritage craft, DTC home goods, etc.)... - Backgrounds: `#f5f1ea`, `#f7f5f1`...
> Landing pages and portfolios are *visual products*. Text-only pages with fake-screenshot divs are slop.
https://github.com/yc-software/qm/blob/7f2c916360f1797a8ff2a...
I'd be interested to see what comes out, but it also highlights an curious prompt-control-comparison question
Why? The exfiltration vector was known, the sample size was small, and the safety instructions were likely statically positioned. In regular operating practice, none of these three guarantees may hold.
Gotta love it when agent instructions get blurted out in user-facing documentation