little-planet-factory

How Little Planet Factory agents ask the user questions — as interview questions through the question tool, each with short self-contained context and concrete options, never as questions buried in prose. Covers when to ask, how to write the context and options, batching, and how managers and workers hand questions up for the overseer to ask.

How the Little Planet Factory inspector runs an optional Codex code review (regular, plus adversarial for risky changes) as a second reviewer alongside its own inspection, when the Codex plugin for Claude Code is enabled, installed, and ready. Covers when to run it, detecting Codex silently, launching it in the background, finding its job, collecting it within one shared time budget, cancelling on timeout, reporting a run that didn't complete (usage limits included) in one line with its reason, verifying every Codex finding before it reaches the report, and what Codex leaves behind. Only the inspector uses it.

How Little Planet Factory agents work a project's Linear board through the Linear MCP — the `## Linear` block in CLAUDE.md that pins the session to one project and sets the status mode (comment-only, to-review, or to-done), resolving statuses by type and name instead of hard-coded names, working ready unassigned Todo tickets in ranked batches that don't overlap on files or build together (with a "do all" loop), blocking stuck tickets, refining Backlog tickets with the user and moving them to Todo, linking Cadence specs when Cadence is connected, and which role may write to Linear. Use when the user asks to work on, pick up, finish, refine, groom, or plan tickets in Linear, or when a brief's source of truth is a Linear issue.

How Little Planet Factory agents work in Next.js apps on any host — firm defaults (a dynamically generated Open Graph image through the opengraph-image convention, next/image instead of <img>, and Vercel Analytics and Speed Insights when on Vercel) unless the user asks otherwise; the Metadata API and metadata file conventions; next/image; proxy.ts; hydration safety; Next 16 caching and "use server" rules; RSC serialization; route-level CSS; and toolchain pins. Use when planning, implementing, or reviewing changes in a project whose package.json depends on next or that has a next.config.* file. Load it alongside react-apps (generic React, stack detection, no dev servers) and web-design (page-level SEO, icon, and title rules, which this skill implements in Next), and also load vercel when the project deploys to Vercel.

How Little Planet Factory agents use the Cadence and Telescope MCP servers when they are connected — knowledge vault, reports, specs, and upstream-incident diagnosis — with per-role responsibilities for the overseer, manager, worker, researcher, inspector, and signoff.

The quality bar Little Planet Factory agents hold work to so defects are prevented on the first pass rather than found by review — which work counts as foundational, pre-mortems that turn invariants into named tests, per-unit and repair-diff review, treating claims and verification output skeptically, and the default rule that agents don't write user-facing copy beyond inventoried labels. Per-role responsibilities for the overseer, manager, worker, researcher, inspector, and signoff.

How Little Planet Factory agents work in React web apps (Vite, Next.js, Remix/React Router, CRA, and similar) — detecting the stack and its commands, verifying without starting dev servers, component and hook discipline, and how to split React work across agents without colliding on shared files, sequencing units that build together. Use when planning, implementing, or reviewing changes in a project whose package.json depends on react.

How Little Planet Factory agents work on projects deployed to Vercel — deploys happen only through git, never the Vercel CLI, unless the user asks otherwise; which CLI actions are allowed; environment variables and secrets; firm defaults (Vercel Web Analytics and Speed Insights always enabled, and never Neon or any Neon-backed database) unless the user asks otherwise; function limits and costs; Next.js-on-Vercel rules; build tracing; Blob access; and how to debug a deployment through logs instead of redeploying. Use when a project has vercel.json, a .vercel/ directory, @vercel/* dependencies, or the user says it deploys to Vercel.

How Little Planet Factory agents decide whether and how to use git in a project — resolving the project's version-control policy (none, commit, push, or pull-request), the safety rules that hold under every policy, and which role is allowed to run git writes. Use before any command that changes repository state — commit, branch, push, merge, rebase, stash, tag, or opening a pull request.

How Little Planet Factory agents build web pages and sites on any framework (plain HTML, Next.js, Astro, Vite SPAs, and similar). Firm defaults unless the user asks otherwise - no em-dashes in tab titles, and every site gets a favicon, a unique descriptive title per page, a meta description, and an Open Graph social card. Covers SEO and crawlability (titles, descriptions, canonicals, robots, sitemaps, lang and hreflang, structured data, mobile-first indexing, Core Web Vitals), the icon set and manifest, social cards and unfurlers, theming meta, accessibility, and compositor-friendly animation. Use when building or reviewing any website or web page. Framework implementations live elsewhere - load nextjs for how to do this in Next.js, and vercel for Vercel Analytics and Speed Insights.

How Little Planet Factory agents work in Xcode and Swift projects (iOS, macOS, watchOS, visionOS; .xcodeproj, .xcworkspace, Swift packages, XcodeGen or Tuist) — detecting how the project is defined, building and testing with xcodebuild from the command line, simulator etiquette, what not to touch (signing, project generation, pbxproj), and how to split Apple-platform work across agents, sequencing units that build together. Use when planning, implementing, or reviewing changes in a project containing an .xcodeproj, .xcworkspace, Package.swift, project.yml, or Project.swift.