Ship-With-AI
- 15 skills
- 0 followers
- 10 hours ago last updated
- ▌ Factory · ship-with-ai bundleUse this skill whenever the user wants to run multiple side projects in parallel via an AI org chart. Also trigger when the user says "/factory", "ship multiple side projects in a day", "hire an AI company", "run my side-project portfolio", or "scale beyond one harness". Takes a company goal + monthly budget + 3-5 side-project ideas + stack defaults + day-plan start time, then installs Paperclip, creates a company with budget cap, hires a 3-5 agent org chart (CEO + CTO + 2 engineers + marketer for 5 projects), wires per-agent budgets and heartbeats, drops in a 12-hour day-plan calendar with explicit human-attention windows. Companion to /autopilot — assumes the reader has shipped at least one /autopilot run before. Human-in-the-loop at the four daily attention windows (9am standup / 1pm checkpoint / 5pm gate review / 9pm daily review).
- ▌ Go Live · ship-with-ai bundleUse this skill whenever the user wants to deploy their project, go live, ship to production, set up hosting, configure a domain, or make their app accessible on a real URL. Also trigger when the user says things like "how do I deploy this," "I want to put this online," "make this live," "set up production," "I'm done building, now what?" or "get this off localhost." Use this skill even if the user only mentions one part of deployment (like "set up Vercel" or "configure my database for production") — the skill handles the full deploy workflow and will focus on the relevant section.
- ▌
- ▌
- ▌ Case Study · ship-with-aiTurns an existing internal script or tool into a buyer-facing case study and outreach message grounded in repository evidence. Use when someone says "/case-study", wants to turn internal work into portfolio proof, document an automation, extract a case study from a repository, or pitch an existing tool to prospective clients.
- ▌ Launch Day · ship-with-ai bundleUse this skill whenever the user wants to launch their product, get first users, write a launch post, promote their project, post on Reddit or Hacker News or Indie Hackers, find their first customers, or prepare for launch day. Also trigger when the user says "I deployed, now what?", "how do I get users?", "nobody knows my product exists", "where should I post this?", "write me a launch post", or "I want to start charging." Use this even if the user only mentions one platform — the skill generates posts for all relevant platforms.
- ▌ Pre Flight · ship-with-ai bundleUse this skill whenever the user wants to verify a side project is ready for its first real user — after `/autopilot` or `/factory` has reported "shipped" but before sending any DM. Also trigger when the user says "/pre-flight", "is my side project ready", "check before I DM users", "first-user readiness check", "the eval my agents skipped", "did my agent actually ship a product", or "ship/fix/rebuild verdict". Takes the live URL + idea.md + scope.md + one named first-user target as input. Runs four eval questions (Output / Trace / Component / Drift) against the live URL, writes pre-flight.md with pass/fail per question, surfaces the top 3 blockers ordered by impact × effort, and outputs a SHIP / FIX / REBUILD verdict. Companion to /autopilot and /factory — the eval rung the Lead the Machine series never wrote.
- ▌ Context Tax · ship-with-aiRetrospectively analyze the current Claude Code session and estimate how much time and tokens were spent on context work (explaining the codebase, style guide, conventions, correcting Claude when it reinvented existing utilities) vs. actual feature work. Use this skill whenever the user wants to audit session efficiency, measure how much time they lost to re-explaining context, or decide whether to invest in persistent project docs. Trigger on "/context-tax", or phrases like "calculate my context tax", "how much did I waste on context this session", "audit this session", "session breakdown", "was this session efficient", even if the user doesn't explicitly say "context tax".
- ▌ Night Shift · ship-with-ai bundleUse this skill whenever the user wants to set up an overnight autonomous build, ship while they sleep, run agents overnight, prepare for an autonomous loop, or review overnight work. Also trigger when the user says "I want the agent to work while I sleep", "set up a night run", "prepare for overnight build", "check what happened overnight", "review overnight work", or "did the overnight build succeed?" Use this skill to prepare pre-sleep checklists and do morning reviews — the actual autonomous loop is handled by Ralph or Claude Code's native loop features, which this skill configures and wraps.
- ▌ Niche Finder · ship-with-ai bundleTurn recurring work complaints into a defensible, specific niche statement grounded in problems the user has personally experienced. Use whenever someone wants to find or choose a niche, identify a service or consulting offer, turn workplace frustrations into a business idea, find a first-client angle, or says they do not know what niche to pursue. Prefer lived evidence over trends and never invent a market the user did not describe.
- ▌ Proof Project · ship-with-aiTurns a developer's real-world problem into one narrowly scoped, live portfolio project built around a single useful feature. Use when someone wants to choose or reduce the scope of an AI portfolio project, weekend build, proof-of-work demo, client credibility project, or says "/proof-project". Interviews one question at a time, rejects hypothetical problems, removes platform features, and produces a build-ready one-feature brief plus portfolio card.
- ▌
- ▌ Parallel Build · ship-with-ai bundleUse this skill whenever the user has multiple specs or features to build and wants to run them in parallel, build faster, run multiple agents, or batch their build session. Also trigger when the user says "I have a bunch of features to build," "can I run these at the same time?", "which of these can I build in parallel?", "I want to build all my feedback specs today," or "plan a build session for these specs." Use this even if the user only has 2-3 specs — the dependency analysis prevents conflicts regardless of batch size.
- ▌ Collect Feedback · ship-with-ai bundleUse this skill whenever the user wants to get feedback on their MVP, find testers, prepare outreach messages, create test scripts for users, analyze user feedback, or convert feedback into feature specs. Also trigger when the user mentions testers, user research, validation, feedback collection, or wants to know what to build next based on real user input. Use this even when the user says things like "I just built this, now what?" or "should I add more features?" — redirect them to collecting feedback first.
- ▌ Evaluate Side Project · ship-with-aiUse when evaluating, filtering, scoring, validating, or pressure-testing a side project, startup idea, app idea, AI product idea, MVP, weekend build, or one-sentence product concept before implementation.