Use this when you're deciding whether to build internal tooling, designing developer platforms, or trying to figure out when your infrastructure will hit the wall. It pushes you to abstract common capabilities instead of rebuilding the same thing across teams, and it's surprisingly opinionated about stuff like server-side tracking over client-side SDKs. The real value is in the questions it asks: who's actually using this platform, what's your doomsday clock for current infrastructure, how will you measure adoption. It won't let you build platforms for theoretical future needs, which is the right kind of annoying. Draws from product and engineering leaders who've scaled platforms at companies that actually had to solve these problems.
npx -y skills add refoundai/lenny-skills --skill platform-infrastructure --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
microsoft/azure-skills
zxkane/aws-skills
awslabs/agent-plugins
microck/ordinary-claude-skills
microsoft/github-copilot-for-azure
zxkane/aws-skills