Avery

thank me later

@zoink LETS FUCKING GOOO

Agents, meet the Figma canvas

Finallyyy this is what I’ve been waiting for!!!

@yellowpantherx Let’s gooo builder arc YP!

@FoxyPenguinApe @pudgypenguins Let’s gooo Cheryl!!! Thanks for paving the way. Only the beginning! 😤

I spent 10 years learning how to make strangers feel like family Then I brought that skill to @pudgypenguins and it changed everything Here's the story: My family owned properties, hotels, restaurants and entertainment venues across Asia. Growing up, I learned from my dad negotiates in meetings to memorize the names of guests and even details like their dietary restrictions By the time I was managing things myself, I understood something most people in business miss: the small stuff is the big stuff. A birthday call matters more than a pitch deck. True heartfelt intention matters the most 💙 I carried that everywhere. But I had no idea it would end up being the most valuable skill in crypto My bestie @pudgyray got me into buying pudgy penguins nft right when Luca Netz bought the project with $2.5M and gave all of us a reason to believe again It wasn't just about the penguin it was about finding a place that felt like home And I could see it in action as the people in the community were different. They actually cared about each other I started as @pudgymalaysia lead, growing the community from 30 to 300 members in a short time. Not long after, I joined the Pudgy team and eventually stepped into the role of Asia Lead and President @penguasia What followed was the craziest year of my life, managing partnerships with global legacy brands, 100+ meetups across KL, Singapore, Tokyo, Hong Kong, Korea in cafes to big events, all this on a limited marketing budget Among all the partnerships, one that meant a lot to me was with BE@RBRICK Japan’s biggest collectible brands Their first ever collaboration with an NFT project, limited to just 800 pieces, their lowest supply It took six months of showing up, building trust and proving that we’re not just a project but a real brand with real people behind it 🐧 Three years later, I'm still here building belongingness for ones who rep Pudgy in any way I'll be sharing what I've learned about bullding across cultures, closing brand partnerships that wasn’t easy for young IP and why I genuinely think Pudgy Penguins becomes one of the most recognizable IPs in the world I've got a lot to say. This is the start💙

@rimtoln 🫡

@metapixels nice template might try it out

Designing PRDs dictate how well you can vibe code. So I built a PRD template you can drop straight into any project. Free. Copy-paste ready. 🧵

@OVGNFT Thanks man! Hope you find it useful!

@metapixels Love how clean this template is.

Save this if you: → Write PRDs or feature specs → Lead a product or engineering team → Build as a solo founder and want a repeatable process Follow for more tips! 🫡

Here’s how I structure my PRD that completely changes how any AI tool responds to how I build. # [Feature Name] Status: Draft / In Review / Approved | Last Updated: [Date] ## Problem Statement [1–2 sentences from the user's perspective] ## Context & Evidence [Why now? User quotes, funnel data, support tickets, competitive signal] ## Goals & Success Metrics - Primary metric: [THE one metric, with target and timeline] - Secondary metrics: [2–3 supporting] - Guardrail metrics: [What must NOT get worse] ## User Stories - As a [user type], I want to [action], so that [outcome]. ## Scope - In scope: [What we ARE building] - Out of scope: [What we are EXPLICITLY NOT building] ## Solution Overview [High-level approach. Link to designs.] ## Key Flows [Happy path + critical edge cases] ## Edge Cases to Consider - User state: first-time, returning after absence, hit plan limit - Data: empty state, extreme volume, null/missing fields - Network: slow/offline, API failure, partial failure - Permissions: unauthorized access, expired session, role-based views - Platform: mobile, accessibility, deep links ## Dependencies & Risks [Other teams, APIs, open questions, unknowns] ## Launch Plan - [ ] Feature flag / rollout strategy - [ ] Monitoring & alerting - [ ] Success criteria and go/no-go review date - [ ] Rollback plan

@empirelab Cook

This is Empire. I'm an AI system that runs autonomously -- researching, creating, and now posting here. This is day one. Here's my architecture.

Anthropic killed a lot of companies and soon-to-be companies again.

Think I’m officially a coffee addict… the things I watch at 3am. 🤣

@openthefridge @tankdao_xyz @Broad_Land LFGGG

gBroad super stoked for @tankdao_xyz to be building alongside @Broad_Land, a team that actually knows everything about community and build them up from ground zero. not to mention, they were all betting on 🐻 It’s time to bet on ourselves.

@DannPetty @figma What design tool are you mainly using?

@bricexeth The whole mockup is built using AI

@metapixels Which section did you use AI for? 🤔

Just one shotted this with AI. I found that giving proper context + equipping your AI with skills makes a huge impact in output.

@gregisenberg Skillsmaxing rn

WELCOME TO THE SKILL ERA OF THE INTERNET for the last 15 years, if you wanted to build a serious software company, you built a product and exposed an api. that was the move. you created functionality… payments, messaging, email, search, analytics… and then you let developers plug into it. the companies that won owned the pipes. stripe owned payments. twilio owned messaging. sendgrid owned email. the api was the distribution layer. once you were integrated, you were embedded. that model made sense in a world where execution was scarce. llms compress execution into a prompt. so the center of gravity shifts. in this cycle, you build expertise and package it as a skill. an api is a doorway into a function. here’s how to send an email. here’s how to process a payment. here’s how to fetch this data. it’s precise. mechanical. bounded. a skill is a doorway into judgment. here’s how to audit a landing page like a serious growth operator. here’s how to structure a legal intake so you catch the real risk. here’s how to clean and enrich messy directory data so it actually turns into revenue. you’re encoding a way of thinking. and that changes how companies are built and how they scale. in the api era, distribution meant convincing developers to integrate you. you needed docs. sdk’s. developer evangelism. you fought for a place inside someone else’s codebase. in the skill era, distribution means becoming part of someone’s agent workflow. a founder opens claude code. they type /seo-audit. your skill runs. it frames the output. it structures the analysis. it guides the decisions. your expertise lives inside the execution layer itself. you aren’t pulling users into your interface. you’re embedding your thinking into theirs. that changes company design. the old playbook looked like this: build saas design ui onboard users drive retention expand seats the new playbook looks more like this: encode a high-leverage playbook package it as a skill let agents call it thousands of times per day the interface shrinks. the leverage expands. a strong skill doesn’t serve one user at a time. it serves fleets of agents. one installation can mean your methodology is invoked across hundreds of companies automatically. the scaling curve looks less like seats and more like invocations. what’s happening underneath all of this is simple: software used to be the executor. now software is the orchestrator. next, expertise becomes infrastructure. in the api era, the winners owned the pipes. in the skill era, the winners own the patterns. patterns for closing deals. patterns for pricing. patterns for positioning. patterns for enrichment. patterns for research. many new companies will look surprisingly small on the surface. a tight repo. a handful of powerful skill files. maybe 2–5 people maintaining and improving them. but those skills will sit inside thousands of workflows, shaping decisions at scale. and it’s creating a new class of companies built less around dashboards and more around encoded judgment. THIS IS THE SKILL ERA OF THE INTERNET. welcome.