Migrate to coderabbitai/agentic-patterns: repo + domain refs, tier-vocab docs

- Repo references dmoka/sdlc-workflows → coderabbitai/agentic-patterns
- Site domain agentic-sdlc.dev / agenticsdlc.dev → agenticpatterns.io
- package.json name → agentic-patterns
- Fix stale tier vocabulary in README/CONTRIBUTING/PR-template
  (universal/multi-file/tool-specific/concept → snippet/framework/tool)
  to match SCHEMA.md and the validator

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: dmoka

.github/PULL_REQUEST_TEMPLATE.md

@@ -12,7 +12,7 @@ One-line description of the workflow you're adding (or change you're making).
 
 - [ ] New MDX file lives at `workflows/<slug>.mdx`
 - [ ] Frontmatter has `title`, `tagline`, `tier`, `canonical_url` (the four required fields)
-- [ ] `tier` is one of `universal`, `multi-file`, `tool-specific`, `concept`
+- [ ] `tier` is one of `snippet`, `framework`, `tool`
 - [ ] `setup_command` is the actual install + run incantation a reader can copy
 - [ ] `when_to_use` / `when_not_to_use` are filled in
 - [ ] At least one entry in `sources`

.github/workflows/trigger-rebuild.yml

@@ -1,7 +1,7 @@
 name: Trigger site rebuild
 
 # When a workflow MDX change lands on main, POST to the Vercel deploy hook
-# so the consuming site (agentic-sdlc.dev) rebuilds and picks up the change.
+# so the consuming site (agenticpatterns.io) rebuilds and picks up the change.
 
 on:
   push:

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing a workflow
 
-This is the contribution surface for [agentic-sdlc.dev](https://agentic-sdlc.dev). Every `.mdx` file you add under [`workflows/`](./workflows) becomes a card on the site within ~2 minutes of merge.
+This is the contribution surface for [agenticpatterns.io](https://agenticpatterns.io). Every `.mdx` file you add under [`workflows/`](./workflows) becomes a card on the site within ~2 minutes of merge.
 
 ## TL;DR
 
@@ -24,7 +24,7 @@ Use this when there's an authoritative external doc you'd just point readers to
 title: My Tool — My Workflow Name
 tagline: One sentence describing what this workflow does and when it shines.
 attribution: Vendor or Author Name
-tier: tool-specific      # or: universal | multi-file | concept
+tier: tool               # or: snippet | framework
 canonical_url: https://example.com/docs/my-workflow
 setup_command: |
   # The actual install + run commands a user copies
@@ -56,7 +56,7 @@ Use this when there's no maintained upstream doc you can trust (single-author bl
 title: Workflow Name
 tagline: One sentence.
 attribution: Originator (with date)
-tier: multi-file         # usually multi-file or concept for editorial cards
+tier: framework          # usually framework or snippet for editorial cards
 canonical_url: https://blog-post-or-repo-where-it-was-coined.example
 when_to_use: One sentence.
 when_not_to_use: One sentence.
@@ -107,7 +107,7 @@ When you're writing a body (editorial mode only — Reference cards leave the bo
 The Action that runs on your PR (`.github/workflows/validate.yml`) checks:
 
 - ✅ Required fields present: `title`, `tagline`, `tier`, `canonical_url`
-- ✅ `tier` is one of `universal | multi-file | tool-specific | concept`
+- ✅ `tier` is one of `snippet | framework | tool`
 - ✅ `canonical_url` is a valid HTTPS URL
 - ✅ Slug (filename minus `.mdx`) matches `[a-z0-9-]+` and is unique
 - ✅ `related` keys are subset of allowed collection names
@@ -129,8 +129,8 @@ Beyond the schema, here's what we look for in editorial review:
 ## Local preview
 
 ```bash
-git clone https://github.com/dmoka/sdlc-workflows.git
-cd sdlc-workflows
+git clone https://github.com/coderabbitai/agentic-patterns.git
+cd agentic-patterns
 npm install
 npm run lint                  # runs the validator on your changes
 ```
@@ -139,4 +139,4 @@ To preview rendering on the live site, you'll need to clone the main site repo (
 
 ## Questions
 
-Open an issue at [github.com/dmoka/sdlc-workflows/issues](https://github.com/dmoka/sdlc-workflows/issues).
+Open an issue at [github.com/coderabbitai/agentic-patterns/issues](https://github.com/coderabbitai/agentic-patterns/issues).

README.md

@@ -1,12 +1,12 @@
-# sdlc-workflows
+# agentic-patterns
 
-The open-source workflow catalog behind **[Agentic Software Development](https://agentic-sdlc.dev)**.
+The open-source workflow catalog behind **[Agentic Software Development](https://agenticpatterns.io)**.
 
-Each `.mdx` file under [`workflows/`](./workflows) is a copy-pasteable orchestration recipe for AI coding agents — Ralph, Spec Kit, PIV Loop, AGENTS.md, Antfarm, and 30+ others. The site at [agentic-sdlc.dev](https://agentic-sdlc.dev) renders these into card-grid + detail pages with an "Open in ChatGPT / Claude" menu.
+Each `.mdx` file under [`workflows/`](./workflows) is a copy-pasteable orchestration recipe for AI coding agents — Ralph, Spec Kit, PIV Loop, AGENTS.md, Antfarm, and 30+ others. The site at [agenticpatterns.io](https://agenticpatterns.io) renders these into card-grid + detail pages with an "Open in ChatGPT / Claude" menu.
 
 ## Quick links
 
-- 🌐 **Site:** [agentic-sdlc.dev](https://agentic-sdlc.dev)
+- 🌐 **Site:** [agenticpatterns.io](https://agenticpatterns.io)
 - 📝 **Contribute a workflow:** [CONTRIBUTING.md](./CONTRIBUTING.md)
 - 📋 **Frontmatter schema:** [SCHEMA.md](./SCHEMA.md)
 - ⚖️ **License:** MIT — workflows are free to use, modify, and redistribute with attribution.
@@ -15,10 +15,9 @@ Each `.mdx` file under [`workflows/`](./workflows) is a copy-pasteable orchestra
 
 A workflow is a reusable orchestration pattern for AI coding agents — a recipe you can copy into your LLM of choice. Categorized by **tier**:
 
-- **`universal`** — a prompt or pattern that works in any LLM (ChatGPT, Claude, Gemini)
-- **`multi-file`** — needs files on disk (e.g., `AGENTS.md`, `PROMPT.md`)
-- **`tool-specific`** — requires a specific tool (Claude Code, Cursor, Aider, …)
-- **`concept`** — an architectural idea, not a specific runnable recipe
+- **`snippet`** — small paste-able pattern; no install, no scaffolding
+- **`framework`** — needs scaffolding (files / skills / CLI) installed into your agent
+- **`tool`** — commits to a specific tool or product (open- or closed-source)
 
 ## Example workflow
 
@@ -30,7 +29,7 @@ title: OpenAI Agents SDK — Handoffs
 tagline: Each agent exposes transfer_to_X tools; the next response is owned
   by whichever agent is handed control.
 attribution: OpenAI
-tier: tool-specific
+tier: tool
 canonical_url: https://openai.github.io/openai-agents-python/handoffs/
 setup_command: |
   pip install openai-agents
@@ -54,7 +53,7 @@ For full field documentation see [SCHEMA.md](./SCHEMA.md). For contribution rule
 1. You PR a new `.mdx` under [`workflows/`](./workflows)
 2. The frontmatter-validator Action runs on the PR — blocks merge on schema violations
 3. Maintainer reviews and merges
-4. A GitHub Action POSTs to the [agentic-sdlc.dev](https://agentic-sdlc.dev) deploy hook
+4. A GitHub Action POSTs to the [agenticpatterns.io](https://agenticpatterns.io) deploy hook
 5. The site rebuilds (~90s) — your workflow is live with a detail page, an LLMs ▾ menu, and cross-links into the knowledge base
 
 End-to-end: PR merge → live on site in under 2 minutes.

SCHEMA.md

@@ -79,7 +79,7 @@ related:
   workflows: []                       # slugs of sibling workflows
 ```
 
-**Note:** the slugs must exist on the main site. If you're unsure what slugs are available, check the live site at [agentic-sdlc.dev](https://agentic-sdlc.dev) — each detail page URL ends with its slug.
+**Note:** the slugs must exist on the main site. If you're unsure what slugs are available, check the live site at [agenticpatterns.io](https://agenticpatterns.io) — each detail page URL ends with its slug.
 
 Don't worry about being exhaustive. 3–6 strong links across 2–3 sections is better than 30 weak ones. The validator caps at 3 per section; extras are dropped.
 
@@ -95,7 +95,7 @@ When in doubt, pick `tool` — it's the most common.
 
 ## `review_gate` shape
 
-Optional. When present, renders a compact rubric on the detail page showing how this workflow answers the three questions of [The Review Gate](https://agenticsdlc.dev/the-review-gate). Non-tool answers (CI, lint, human review, type-system) are first-class options — "tool-assisted" is one option among five.
+Optional. When present, renders a compact rubric on the detail page showing how this workflow answers the three questions of [The Review Gate](https://agenticpatterns.io/the-review-gate). Non-tool answers (CI, lint, human review, type-system) are first-class options — "tool-assisted" is one option among five.
 
 ```yaml
 review_gate:

package.json

@@ -1,9 +1,9 @@
 {
-  "name": "sdlc-workflows",
+  "name": "agentic-patterns",
   "version": "0.1.0",
   "private": false,
   "license": "MIT",
-  "description": "Community catalog of agentic SDLC workflows. Source of truth behind agentic-sdlc.dev.",
+  "description": "Community catalog of agentic SDLC workflows. Source of truth behind agenticpatterns.io.",
   "type": "module",
   "scripts": {
     "lint": "node scripts/validate-frontmatter.mjs",

workflows/review-agent-on-every-merge.mdx

@@ -4,7 +4,7 @@ tagline: Every PR passes an automated review gate before merge, independent of w
 attribution: Convergent pattern
 tier: snippet
 autonomous: false
-canonical_url: https://agenticsdlc.dev/the-review-gate
+canonical_url: https://agenticpatterns.io/the-review-gate
 when_to_use: Any repo where agents write code that humans will merge.
 when_not_to_use: Throwaway prototypes; codebases where human-only review is already deep and disciplined.
 tags: [code-review, verification, gate, primitive]
@@ -26,7 +26,7 @@ checkpoints:
     description: Human approval required even after automated review clears
 sources:
   - title: The Review Gate (Agentic SDLC Handbook)
-    url: https://agenticsdlc.dev/the-review-gate
+    url: https://agenticpatterns.io/the-review-gate
   - title: GitHub Blog, lessons from 2500+ AGENTS.md
     url: https://github.blog/ai-and-ml/github-copilot/how-to-write-a-great-agents-md-lessons-from-over-2500-repositories/
     year: 2025