Tools that survived reuse.

Subskill of site-health — AI/agent indexing audit (llms.txt, /api/ai, markdown negotiation, robots vs AI crawlers, SPA-fake detection). Route here from site-health for "can AI read my site" checks.

Create a read-only local disk-usage report whose scan JSON, classified evidence, and static HTML stay under Fleet Workspace. Use when the operator asks what is consuming storage, says a disk is full, wants storage or cache analysis, asks for cleanup candidates, or wants a storage report. Do not use for RAM or process-memory diagnosis.

Build, review, test, and qualify Swift or SwiftUI applications across iOS, iPadOS, macOS, and watchOS. Covers Xcode and XcodeGen projects, platform boundaries, entitlements, simulator and physical-device QA, native accessibility, lifecycle, sync, and release preparation. Also the entry point for Apple work in general: it routes archive, signing, upload, TestFlight, App Store, and notarization work to apple-release.

Qualify and deliver Apple applications end to end: Xcode archives, signing and entitlements, App Store Connect uploads, TestFlight internal and external testing, App Review submission, Mac App Store distribution, Developer ID signing, notarization, stapling, Gatekeeper checks, and Apple account/support diagnosis. Use when the user explicitly authorizes an Apple-side release action or asks for release readiness.

Orchestrate Codex work with an Astra root and bounded Luna subagents when the user explicitly asks for agents, delegation, parallel work, or independent multi-agent review, or when current project instructions require it. Skip ordinary root-only work and tasks that cannot benefit from independent workstreams.

Delegate work to a fresh headless Claude Code instance as a teammate — a parallel worker in a worktree, a fresh-context review unbiased by the current conversation, or a run under the other profile (personal ~/.claude vs work ~/.claude-work, separate auth/config). Use when the user asks to call/delegate to claude or claude-work, or when you want an independent Claude with clean context.

Delegate repo-local coding work to OpenAI Codex CLI as a teammate agent — scoped implementation, mechanical refactors, test-fix loops, or an independent second-opinion code review from a different model family. Use when the user asks to call/delegate to codex, wants a second opinion on a diff, or when a well-scoped implementation task can run in parallel (e.g. in a worktree) while you do other work. Not for strategy, taste-heavy UX, or vague requirements.

Delegate coding work to Cursor Agent CLI (cursor-agent) as a teammate — fast scoped implementation with a clean JSON envelope, read-only plan/ask modes, or access to Cursor's model roster (GPT, Claude, Gemini variants) under a separate subscription quota. Use when the user asks to call/delegate to cursor, or as an implementation fallback when other teammates are quota-limited.

Optional proprietary Devin teammate. Use only when the user explicitly asks for Devin or approves the spend/lock-in tradeoff.

Delegate coding work to Grok CLI (xAI's terminal agent) as a teammate — scoped implementation with native worktree isolation, best-of-N parallel attempts on hard tasks, or a cross-model second opinion. Use when the user asks to call/delegate to grok, wants N parallel attempts at one task, or wants an opinion from a non-Anthropic/non-OpenAI model family.

Delegate work to Codex, Grok, Cursor, a fresh Claude Code instance, Hermes, or optional Devin. Use for independent review, parallel attempts, bounded specialist work, and explicit-spend external agent runs.

Report on staleness and drift in the public catalogs — expired funding deadlines still marked open, launch destinations not verified recently, conflicting source claims, and (opt-in) live liveness probes that catch dead, parked, or hijacked domains. Use for "what's gone stale", "which deadlines passed", "re-verify the launch catalog", or scheduled refresh sweeps before updating launchdesk.json or funding.json.

Audit Microsoft Clarity across every Fleet product, including project-ID integrity, source wiring, desired capability coverage, provider settings, cached aggregate traffic, and explicit live traffic refreshes. Use for Clarity counts, fleet-wide Clarity health, missing analytics, feature adoption, or requests to test Clarity on all applications; for project creation or source installation, follow its rollout reference.

Audit Cloudflare costs, billable usage, free-tier or paid-plan exposure, quota exhaustion, project necessity, and safe optimization opportunities for Fleet. Use when the user asks whether Cloudflare is charging them, how likely a project is to cost real money, what is driving a bill, whether current Workers/Pages/D1/R2/KV/Queues/Durable Objects/AI usage is needed, which resources look wasteful, what can be optimized, or how to prevent surprise cloud spend.

Run Fleet code cleanup, dependency health checks, and guarded package upgrades in one place. Use for unused code or packages, outdated or vulnerable dependencies, Knip, lint/typecheck/test/format-check orchestration, Bundlephobia evidence, package recommendations, manifest or lockfile edits, and Fleet-wide dependency checks.

Audit whether a product has the SEO and search-intent pages expected in its category, find competitive content gaps, draft source-backed pages, and publish approved pages through the owning repository. Use for SEO article coverage, comparison/alternative/use-case/integration pages, content inventories, or requests to create missing durable search pages.

Fleet's single design entry point for visual or frontend work, and for when the owner calls a design ugly, generic, bland, or template-like. Default lane is PRESERVE (keep the established look, do good work, check the rendered result). OVERHAUL (3-4 rendered directions, owner picks) only for a brand-new surface or an explicit redesign request. Also routes specialist design references (inspiration, slop check, evidence interfaces, components, effects, 3D, Tailwind/markup mechanics).

Look up and track Domain Rating (DR) for any domain, or report DR history for the owner's Fleet domains. Uses the public drank endpoint at domains.sassmaker.com — no API key, no signup. Use for "what's the DR of X", "rank my domains by DR", "did codevetter.com's DR move", or comparing a domain against the fleet board.

Audit the fleet — git/CI health, PROJECT_STATUS sync, or full recurring audit. Use when the user asks "is the fleet healthy?", "what's the fleet status?", "what's everyone working on?", "audit the fleet", "check all projects", "what's broken?", or wants a fleet-wide snapshot before a deploy or audit pass.

Check whether live Fleet products match origin/main (SHA-tagged Workers at 100% traffic, green current-main Actions), and gate a single project's deploy readiness. Use for "is production in sync with main?", "what's not deployed?", "can I deploy X?", or "is X safe to deploy?".

Scaffold a new fleet project — create the GitHub repo, AGENTS.md, PROJECT_STATUS.md, .gitignore, and CI workflow. Use only when the owner explicitly asks to create a new project ("create a new project called X", "scaffold X", "init a new repo for X"). Never propose or start a new project on your own.

Route Fleet-wide audits, deploy checks, public-product smoke tests, spend reviews, project setup, and workspace decisions to the relevant subskill.

Use when working across the Fleet workspace, deciding whether work belongs in a child project, Fleet policy, or project-local task tracking.

Drive three experimental Google Ultra accounts in Flow (Nano Banana image generation + Veo video generation) via a browser agent, spending only included subscription Flow credits. Use when asked to generate images/videos with Flow or Veo, audit Flow credit balances, distribute generations across the Ultra accounts, batch creative briefs, or archive generated media. Never substitute paid APIs (Vertex/Gemini) for browser generation.

Subskill of site-health — recurring GEO/SEO outcome measurement: probe configured queries on live web search, classify A/B/C, append to the ledger, regenerate the trend report. Route here from site-health for "did results move" and scheduled weekly runs.

Use a pool of three Google Ultra Jules API accounts as asynchronous coding workers, primarily for high-value test generation across repos. Use when asked to run a Jules test-sweep, dispatch bounded tasks to Jules, poll Jules sessions, review Jules PRs, or check Jules account usage/quota. Jules is a batch worker, never the primary interactive agent and never an auto-merger.

Plan and run a one-off launch for a new product or major feature, including honest directory-submission runs with the launchkit toolkit. Use when the owner asks to launch a product, submit to directories, plan a launch run, or runs /launchkit. Builds one exact plan, gets owner approval of it, then executes only the approved items.

Inspect, diagnose, and safely clean local listening ports and development-server processes with the installed `ports` CLI. Use when a local port is occupied, stale or orphaned dev processes should be stopped, a project's ports need clearing before restart, or an operator asks what is listening locally. Preserve healthy Docker, database, system, and unrelated project listeners unless explicitly named.

Develop evidence-backed positioning, customer research, marketing copy and launch plans for Fleet products. Use for messaging and distribution work, not deployment, visual design or technical SEO audits.

Inspect or acquire public audio, video, subtitles, thumbnails, and media metadata with yt-dlp for an explicit research, archival, or product workflow; not for playback, private content, DRM bypass, or account scraping.

Start, supervise, and report durable Fleet work requested from Telegram or another chat surface. Use when the operator asks to spin up work, run something in the background, show task status, or test mobile control.

Generate tasteful, likely-available domain names for a startup idea. Orchestrated pipeline (run-pipeline.sh): taste scoring, collision scan, two-pass RDAP/DNS availability, markdown shortlist. Reads PROJECT_STATUS.md in fleet repos. Use for domain names, brandable domains, naming help, "name my startup", or /name-domains. No backend, no signup.

Wire a fleet app to App Health application logs (Slack-alertable events like signup, waitlist.join, payment.failed) or add a new alertable event. Use when asked to "alert on X", "notify me when someone signs up", "add a ping/log", or to add an app to the Logs tab.

Audit whether public websites actually work for users through bounded browser journeys. Use when the user asks to click around a site or the Fleet, verify guest usability, test each product's unique pages, find blank or broken routes, exercise search/detail/primary actions, or produce an actionable public-product repair queue. This is a read-only production audit, not SEO, performance measurement, native-app testing, or automatic repair.

Subskill of site-health — on-page SEO audit (title/meta/canonical/OG/hreflang/JSON-LD/sitemap/headings/alt/SSR leaks) for any URL list. Route here from site-health for "check my SEO" requests.

Research keywords, search competitors, backlink prospects, and local-search opportunities with evidence and optional provider metrics; use for SEO market decisions, not technical on-page audits, Search Console collection, or content publication.

Route site health, Microsoft Clarity traffic, AI indexing, technical SEO, competitive content coverage, performance, visibility trends, and public guest-journey audits to one relevant Fleet subskill.

Validate a Fleet agent skill by clean-room testing: a fresh agent with no session history attempts real work (or a zero-cost plan) using only the skill's text, and the run is graded against a rubric so failures become specific edits to the skill. Use for "validate this skill", "test the skill", "does this skill work", "skill QA", or before merging a new or changed skill under tooling/skills. Not for validating product code.

Opt-in spec workflow for large fleet features. Use only when the owner asks for spec-driven work, a spec, or a tracking issue, or when a feature is genuinely large or cross-repo. Writes the proposal, design, specs, and task checklist; creates a GitHub tracking issue only when the owner wants tracking. Small fixes and ordinary scoped changes skip it.

Identify high-value regression tests, review assertion quality, diagnose flaky or low-signal suites, and design replayable adversarial workloads. Use for concrete test-quality work, not general code cleanup, startup readiness, or release approval.

Extract structured public web content or build a bounded crawl when repeatable page data is needed; use for datasets and corpora, not ordinary web research, browser interaction, authenticated pages, or technical SEO audits.

Fleet operator script: Agent Stack.

apply-clarity-id.sh — replace CLARITY_PROJECT_ID placeholder with the real

Fleet operator script: Audit.

Credential-free availability checks may run daily when explicitly reviewed.

Fleet operator script: Fleet Capabilities.

Manage agent writer worktrees, pinned-pnpm installs and bounded commands.

Fleet operator script: Git Health.

Fleet operator script: Github Priority Queue.

Fleet operator script: Link Project Agent Assets.

Score rendered websites locally with pinned slop-detect rules and evidence.

Fleet operator script: Unlink Project Agent Assets.

Fleet operator script: Validate Tooling.

scripts/verify-local.mjs

{ "name": "example", "version": "1", "url": "https://example.com", "llms": "https://example.com/llms.txt", "llmsFull": null, "sitemap": "https://example.com/sitemap.xml", "markdown": { "suffix": ".md", "negotiation": true }, "surfaces": [ { "id": "home", "url": "https://example.c

{{SUMMARY}}

> {{SUMMARY}}

User-agent: ChatGPT-User Allow: /

/ Client-side API call timing via the Resource Timing API. Polls performance.getEntriesByType('resource') for fetch/XHR entries, groups them by normalized route, and emits apicalltiming events to PostHog with p50/p90/max duration + TTFB. This captures the full round-trip la

{ "$schema": "../../../nodemodules/@biomejs/biome/configurationschema.json", "root": false, "extends": ["ultracite/biome/core"], "vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true }, "files": { "ignoreUnknown": true, "includes": [ "", "!!/nodemodules", "!!/.next

<!-- Microsoft Clarity snippet — session replay + heatmaps.

{ "$schema": "fleet.design-review.v2", "version": 2, "project": "replace-with-project-id", "target": "replace-with-reviewed-surface", "surfaceMode": "operate", "mode": "preserve", "register": "product", "context": { "product": "PRODUCT.md", "design": "DESIGN.md" }, "direction": {

Status: retired 2026-08-30. This directory no longer contains a template. Do not copy anything from here.

import { defineConfig } from 'astro/config';

{ "name": "web-product-landing", "private": true, "type": "module", "packageManager": "pnpm@10.33.2", "scripts": { "dev": "astro dev", "build": "astro build" }, "devDependencies": { "@astrojs/check": "0.9.10", "astro": "7.2.0", "typescript": "6.0.3" }, "pnpm": { "onlyBuiltDepende

This is the canonical starting point for a Fleet web landing page. Use it for a web product, developer tool, internal utility, or dashboard that needs a clear public first view without phone screenshots.

<!doctype html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width" /> <meta name="description" content={description} /> <link rel="canonical" href={canonical} /> <meta property="og:type" content="website" /> <meta property="og:titl

<SiteLayout> <header class="shell nav"> <a class="brand" href="/">{site.name}</a> <nav aria-label="Primary"> <a href="#how">How it works</a> <a class="nav-action" href={site.primary.href}>{site.primary.label}</a> </nav> </header>

export type SiteConfig = { name: string; projectId: string; url: string; title: string; description: string; eyebrow: string; headline: string; lede: string; primary: { label: string; href: string }; secondary?: { label: string; href: string }; artifact: { label: string; title: s

@layer reset, base, components;

{ "extends": "astro/tsconfigs/strict" }

Make every public fleet surface readable by AI agents without scrolling or running JavaScript. Classic SEO (titles, OG, H1) is out of scope here — see seo-audit for that. Landing copy rules stay in LANDINGSTANDARD.md.

Use fleet-workspace for Fleet writer checkouts, dependency installs and heavy commands. It is a local Node CLI with no dependencies or provider access. Implementation tracking: SaaS Maker #179; lockfile-only follow-up: #195.

The working path is a local sitemap crawl of Site Health's canonical roots, then source actions for 4xx pages, missing titles, and missing h1s. A report without remediation is incomplete.

Status: ratified 2026-08-30 on issue #61; gateway policy revised 2026-10-04, superseding the 2026-08-29 no-gateway decision.

Fleet keeps one Microsoft Clarity project per catalog identity. Two skills own different halves of that, and they must not be confused:

Recorded: 2026-08-30. Refs sass-maker/saas-maker#62.

The gate list for a new Fleet product or project. New projects start only when the owner explicitly asks for one. Work top to bottom; skip a phase only with a recorded reason (for example no public surface, or a private tool). Each item points at its canonical doc or skill: this

The repository contains two intentionally different classes of tooling.

Selected on 2026-10-02: slop-detect, with Impeccable retained for source checks and wider design review. This is an advisory rendered-page fingerprint, not a design grade or authorship probability.