
get in, loser we’re airdropping $50k
On Wednesdays we pay users. It's kind of our thing. @CoinbaseWallet

doing the right thing. working hard. being optimistic. putting the team over the individual. pushing boundaries with creativity. eng @CoinbaseWallet.

get in, loser we’re airdropping $50k
On Wednesdays we pay users. It's kind of our thing. @CoinbaseWallet

Discover a new way to follow the action in Coinbase Wallet. Leaderboards are live across coins, perps, and predictions.

legacy banking can be such a pain received a gift for lil myk but since it's his name on the check, it got clawed out of my account would have never happened if the gift was sent to lil.myk.eth app.ens.domains/p/lil.myk.et…

use x402 to get more mykfully.com credits, even when the banking system is down!


the mykfully.com MCP just dropped 🧩 now your agents can draft x threads and give you a link to preview exactly what it will look like once posted!
introducing mykfully! an open sourced app, like typefully, created by @myk_clawd for drafting and previewing your @X threads try it out on mykfully.com or host it yourself!

I've used this workflow for three projects at this point. I'm curious how others are breaking down large pieces of work to move fast without sacrificing quality. Drop your tips and workflows!

6. shipping I wake up to a stack of PRs, each with their own thoroughly spec'd ticket, agent-reviewed code, and several artifacts that help me quickly get up to speed on what it does some PRs are low risk and can be merged right away while others will need another human to review depending on the change as PRs get merged and my system gets built out, my architecture map gets more and more green

5. the build loop whenever the main agent assigns work to a sub-agent to build a piece of the project, it follows a loop that looks like this: -- implementation -- a. build the PR -- code quality -- b. review the PR using a knowledge-base created from real human reviewers who have deep experience in that particular repo c. address all PR feedback & get ci green -- verification -- d. verify the PR with end-to-end testing by deploying all dependent code across several services to a cloud environment and record the test results in the PR -- help my understanding -- e. create a PR walkthrough document (a high-level technical overview of the PR with a 5-question quiz to test my understanding) d. create a PR slideshow (several pictures that explain what the PR is doing in a visually stimulating format -- this is helpful after a full day of reading words) e. create a 2-3 minute @theallinpod podcast episode about the PR (read more about that skill here: x.com/mykcryptodev/status/21…)
i made a skill that explains PRs in 3min like @theallinpod @Jason is the moderator @friedberg walks through the technicals @chamath highlights anything important @DavidSacks pokes at trade offs i used @ElevenLabs but not their actual voices -- it'd be great if i got the ok to use their voices for this! 👉👈 github.com/mykcryptodev/all-…

4. the context skill i work in a session with one agent who has all of the context on the project. they build that context at the start of each new session via the context skill. this skill makes them an expert on the history, decisions, and current status of the project by reading all of the related docs, tickets, PRs, and slack conversations. this agent is instructed to orchestrate a fleet of sub-agents to delegate tasks in order to maximize parallelizable work and preserve it's own context. this allows me to interface with one agent while simultaneously working on several tasks pertaining to the project.

3. the break-down a swarm of agents break down each user story into small sub-issues with precise technical implementation details and dependency mappings. the goal here is to breakdown the work such that one sub-issue is a single small, reviewable PR (~500 LOC). like human development, it's usually at this stage where the agents encounter unforeseen technical challenges, subconscious assumptions, and unanswered questions. agents will ask their smartest model advisor for suggestions on what to do so that they can prompt me with options, trade-offs, and recommendations. any change in direction can immediately update project artifacts and downstream tickets.

2. a high-level scoping of the project my agents write a handful of human-readable user stories in @linear that describes the user journey of the product. instead of a wall of tickets, i have a handful of important progress-markers. the skill that I use at this stage also creates an "architecture map" that connects a system diagram to the statuses the work. it shows the parts of the system that are done, in progress, blocked, or to-do. this helps me easily digest the status of progress towards building the system at a glance.

i took a project from "idea" to "fully built" in a week. before agentic development, it would have taken several months. a 🧵 on my current workflow: 1. take time designing the system (this is the part that's changed the least) but now when I share docs to get feedback, i can easily create engaging docs that are easy to digest like a "pitch deck" for my architecture. I use @jessepollak's internal, ai-native tool, bdocs, for building and collaborating on the documents all data in the pics are fake example data, not a real project


the code is open sourced here github.com/mykcryptodev/mykf…

introducing mykfully! an open sourced app, like typefully, created by @myk_clawd for drafting and previewing your @X threads try it out on mykfully.com or host it yourself!