← all publishers

reidworks-io

@reidworks-io source repo

3 published skills

  1. Long Run · reidworks-io bundle
    Set up a long-running multi-agent orchestrator that builds a project end-to-end across many /loop cycles. Use when the user wants to "kick off an overnight build", "start a weekend run", "set up the orchestrator harness", "run a long autonomous build", or any task framed as "let Claude build this while I sleep". Hard-requires a detailed milestone roadmap before kickoff — if the user lacks one, this skill stops and routes them to write one (it does NOT auto-generate the roadmap). Uses Git as the source of truth; expects the app, docs, marketing site, tests, and screenshots to live in the same repo so the prototype's assets evolve together. Do NOT apply to short one-shot tasks, single PRs, or anything that can finish in one Claude turn.
    0 installs
  2. SEO Review · reidworks-io bundle
    Audit and fix technical SEO and AEO (answer-engine optimisation) for a website: redirect and canonical conflicts, robots.txt and sitemaps, structured data, indexability of staging and internal subdomains, and Google Search Console coverage. Code fixes assume Next.js App Router; the diagnostic phase works on any stack. Trigger phrases include "SEO audit", "SEO review", "AEO audit", "how are we doing on SEO", "why isn't my site indexed", "we're not showing up in Google", "check Search Console", "fix our canonicals", "sitemap isn't working", "make the docs indexable", "how do we show up in ChatGPT".
    0 installs
  3. Human Voice · reidworks-io bundle
    Edit or write external-facing prose so it doesn't read as AI-generated. Apply to documentation, blog posts, tutorials, public READMEs, customer-facing slide decks, marketing copy, and competitive briefs — whenever the user asks to write, edit, review, or style-check such content, even if they don't mention AI. Apply when creating this kind of content from scratch. Do NOT apply to internal communications (Slack, Notion, internal PRs, meeting notes) unless the user explicitly asks for a style review. Trigger phrases include "write a blog post", "edit this doc", "review this tutorial", "write copy for", "external-facing", "customer-facing", "public README", "slide deck for customers", "competitive brief", "does this sound AI-generated", "check this for AI tells", "make this less AI", "remove the slop".
    0 installs