Open-source toolkit for shipping real products with coding agents: durable product contracts, cross-host skills, resumable service connections, and deterministic verification gates.
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
This skill should be used when the user asks to "configure Claude, Codex, Cursor, Hermes, or OpenClaw", "sync agent adapters", "check agent portability", "add an MCP server for every host", or diagnose why rules, skills, subagents, hooks, or OAuth-backed tools behave differently across AI coding hosts.
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for…
Reverse-engineer a live website and rebuild it in the product stack — extraction-first, spec-driven, section by section. Use when the user wants to clone, replicate, rebuild, migrate, or closely follow an existing site or use one as the visual base for the product. Rights decide fidelity; the pipeline is the same…
How Convex is structured inside Agentic Ship — file layout, function shape, naming, the data-access decision tree, and the auth seam. Use before writing any backend code, adding a table, or wiring a component to data.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Frontend security posture for AI-assisted projects — secret handling, supply chain, untrusted component code, prompt injection, XSS, response headers. Use before shipping, after adding dependencies, and whenever pasting code from a registry or the web.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…
Invoked by /plain-language. Reviews project text for plain-language compliance and produces structured findings with rewrites. Does not auto-activate on natural-language requests.
Turn a product request into durable contracts, role-owned work, dependency-aware handoffs, human-input pauses, and evidence-backed completion. Use when starting a product, planning a feature, coordinating multiple agents, resuming work in another AI coding host, or replacing an ad-hoc prompt-only build loop.
The go-live gate. Verify the selected billing provider is live, email leaves testMode with verification on, URLs are real, and no test-seed backdoor exists. Run before the first deploy and after any money, email, or auth change.
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO,"…
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel,"…
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking,"…
Add and maintain SEO-ready MDX articles — metadata, structured data, sitemap, OG images, internal linking. Use when writing a blog post or auditing a page's search surface.
Use when connecting, authorizing, provisioning, resuming, verifying, canceling, or diagnosing an external service such as Convex, Stripe, GitHub, Resend, PostHog, Netlify, Vercel, or Cloudflare, especially when browser consent or another human-only step must pause an agent running in Claude Code, Codex, Cursor…
This compatibility skill should be used when the user asks to "run setup health", "check every connection", "verify Agentic Ship setup", or invokes the former all-in-one health workflow; it routes the request to workspace-health, agent-compatibility, service-connections, upstream-sync, or production-preflight without…
The verification gates, test-data rules, and the self-healing loop — unit tests with vitest/convex-test, e2e with Playwright, tier-1 deterministic repair via pnpm heal, and the healer guardrails. Use when writing tests, when any gate is red, or when a repair is needed.
Establish and enforce the project's visual system — design tokens, typography, radius, spacing, dark mode — and route component sourcing and asset work. Use when starting a project, changing the theme, adding a new interface piece or visual asset, or when generated UI starts looking like every other AI-built site.
Check every vendored skill, MCP server, registry, and version pin against its official upstream; report drift; apply clean updates; three-way merge anything patched. Run monthly, or when a tool ships a major version.
Turn product intent and attributed visual references into a validated visual plan, then review implemented UI for generic generated-page residue. Use before creating a route, page, section, component family, theme, or substantial visual revision, and when an existing interface feels generic or AI-generated.
10 4d agoA57 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: