[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMFDYA5AT7N0ZE5V6FDHXN":3,"skill-same:01M6MMFDYA5AT7N0ZE5V6FDHXN":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6MMFDYA5AT7N0ZE5V6FDHXN","river-review-architecture",null,"設計・アーキテクチャ観点のレビューエージェント。\n依存関係、境界設計、データモデル、API設計等の個別スキルへルーティングする。","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Friver-review-architecture\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"review","river review","river review architecture","river","review architecture","architecture","routing","actions","js","src","adr","diff","tsx","upstream","pages","questions","jsx","entry","docs","design","2026-11-10 10:12:30",false,"---\nid: river-review-architecture\nname: river-review-architecture\ndescription: |\n  設計・アーキテクチャ観点のレビューエージェント。\n  依存関係、境界設計、データモデル、API設計等の個別スキルへルーティングする。\ncategory: upstream\nphase: [upstream]\nseverity: major\napplyTo:\n  - 'src\u002F**\u002F*.{ts,tsx,js,jsx,mjs}'\n  - 'docs\u002F**\u002F*design*.md'\n  - 'docs\u002Fadr\u002F**\u002F*'\n  - 'pages\u002F**\u002F*design*.md'\ninputContext: [diff, fullFile, adr]\noutputKind: [findings, questions, actions]\ntags: [architecture, design, entry, routing]\nversion: 0.1.0\nlicense: MIT\n---\n\n# Architecture Review（設計・アーキテクチャレビュー）\n\n設計判断の妥当性、アーキテクチャ境界の整合性、データモデルの一貫性を検証する。\n\n## When to Use \u002F いつ使うか\n\n- アーキテクチャに影響する変更を含むPRのレビュー時\n- ADR（Architecture Decision Record）のレビュー時\n- モジュール構成や依存関係の変更時\n- API設計の新規作成・変更時\n\n## Routing \u002F ルーティング\n\n入力に応じて、適切な個別スキルへルーティングする。\n\n| キーワード              | スキルID                       | 説明                       |\n| ----------------------- | ------------------------------ | -------------------------- |\n| ADR, 意思決定           | `adr-decision-quality`         | ADR の品質検証             |\n| API, エンドポイント     | `api-design`                   | API 設計レビュー           |\n| API互換, バージョニング | `api-versioning-compat`        | API バージョン互換性       |\n| 境界, モジュール        | `architecture-boundaries`      | アーキテクチャ境界         |\n| 図, ダイアグラム        | `architecture-diagrams`        | 設計図の整合性             |\n| リスク                  | `architecture-risk-register`   | リスク登録の検証           |\n| トレーサビリティ        | `architecture-traceability`    | 要件追跡性                 |\n| 検証計画                | `architecture-validation-plan` | 検証計画レビュー           |\n| 可用性, 冗長            | `availability-architecture`    | 可用性設計                 |\n| ドメイン, コンテキスト  | `bounded-context-language`     | 境界づけられたコンテキスト |\n| キャッシュ              | `cache-strategy-consistency`   | キャッシュ戦略             |\n| コスト, キャパシティ    | `capacity-cost-design`         | キャパシティ設計           |\n| データフロー, 状態      | `data-flow-state-ownership`    | データフロー設計           |\n| データモデル, DB        | `data-model-db-design`         | データモデル設計           |\n| DR, マルチリージョン    | `dr-multiregion`               | 災害復旧設計               |\n| イベント駆動            | `event-driven-semantics`       | イベント駆動設計           |\n| 外部依存                | `external-dependencies`        | 外部依存関係               |\n| 障害, 可観測性          | `failure-modes-observability`  | 障害モード分析             |\n| 結合, コントラクト      | `integration-contracts`        | 結合コントラクト           |\n| マイグレーション        | `migration-rollout-rollback`   | マイグレーション計画       |\n| マルチテナント          | `multitenancy-isolation`       | テナント分離               |\n| OpenAPI                 | `openapi-contract`             | OpenAPI 仕様検証           |\n| SLO, 運用性             | `operability-slo`              | 運用性・SLO                |\n| 要件, 受入              | `requirements-acceptance`      | 要件・受入条件             |\n\n### デフォルト動作\n\n- キーワード指定なし → 変更内容から自動判定\n- 複数カテゴリに該当 → もっとも関連性の高いスキルを優先\n\n## Execution Flow \u002F 実行フロー\n\n```text\n1. 変更種別の判定\n   ├─ ADR\u002F設計ドキュメント → adr-decision-quality を優先\n   ├─ API定義\u002Fエンドポイント → api-design, api-versioning-compat を優先\n   ├─ モジュール構成変更 → architecture-boundaries を優先\n   ├─ データモデル変更 → data-model-db-design を優先\n   └─ キーワード指定あり → 該当スキルを直接選択\n\n2. スキルの実行（該当する専門スキルを並列実行可能）\n   ├─ 設計品質系: adr-decision-quality, architecture-diagrams, architecture-traceability\n   ├─ 構造系: architecture-boundaries, bounded-context-language, data-flow-state-ownership\n   ├─ API系: api-design, api-versioning-compat, openapi-contract, integration-contracts\n   ├─ 運用系: availability-architecture, capacity-cost-design, dr-multiregion, operability-slo\n   └─ リスク系: architecture-risk-register, failure-modes-observability, external-dependencies\n\n3. 統合\n   ├─ 重複する指摘の除去\n   └─ 複数カテゴリ該当時は関連性の高いスキルを優先\n```\n\n## Output Format \u002F 出力形式\n\n```text\n\u003Cfile>:\u003Cline>: \u003Cmessage>\n```\n\n- **Finding**: 何が問題か（1文）\n- **Impact**: 何が困るか（短く）\n- **Fix**: 次の一手（最小の修正案）\n\n## 他スキルとの関係\n\n| スキル                  | 関係 | 棲み分け                                                      |\n| ----------------------- | ---- | ------------------------------------------------------------- |\n| `adversarial-review`    | 補完 | architecture は「設計の正しさ」、adversarial は「設計の盲点」 |\n| `river-review-security` | 補完 | architecture は「構造」、security は「脆弱性」                |\n| `river-review-code`     | 補完 | architecture は「マクロ設計」、code は「ミクロ品質」          |\n\n## References\n\n- [ROUTING.md](.\u002Freferences\u002FROUTING.md): 詳細なルーティングルール\n","# Architecture Review（設計・アーキテクチャレビュー）\n\n設計判断の妥当性、アーキテクチャ境界の整合性、データモデルの一貫性を検証する。\n\n## When to Use \u002F いつ使うか\n\n- アーキテクチャに影響する変更を含むPRのレビュー時\n- ADR（Architecture Decision Record）のレビュー時\n- モジュール構成や依存関係の変更時\n- API設計の新規作成・変更時\n\n## Routing \u002F ルーティング\n\n入力に応じて、適切な個別スキルへルーティングする。\n\n| キーワード              | スキルID                       | 説明                       |\n| ----------------------- | ------------------------------ | -------------------------- |\n| ADR, 意思決定           | `adr-decision-quality`         | ADR の品質検証             |\n| API, エンドポイント     | `api-design`                   | API 設計レビュー           |\n| API互換, バージョニング | `api-versioning-compat`        | API バージョン互換性       |\n| 境界, モジュール        | `architecture-boundaries`      | アーキテクチャ境界         |\n| 図, ダイアグラム        | `architecture-diagrams`        | 設計図の整合性             |\n| リスク                  | `architecture-risk-register`   | リスク登録の検証           |\n| トレーサビリティ        | `architecture-traceability`    | 要件追跡性                 |\n| 検証計画                | `architecture-validation-plan` | 検証計画レビュー           |\n| 可用性, 冗長            | `availability-architecture`    | 可用性設計                 |\n| ドメイン, コンテキスト  | `bounded-context-language`     | 境界づけられたコンテキスト |\n| キャッシュ              | `cache-strategy-consistency`   | キャッシュ戦略             |\n| コスト, キャパシティ    | `capacity-cost-design`         | キャパシティ設計           |\n| データフロー, 状態      | `data-flow-state-ownership`    | データフロー設計           |\n| データモデル, DB        | `data-model-db-design`         | データモデル設計           |\n| DR, マルチリージョン    | `dr-multiregion`               | 災害復旧設計               |\n| イベント駆動            | `event-driven-semantics`       | イベント駆動設計           |\n| 外部依存                | `external-dependencies`        | 外部依存関係               |\n| 障害, 可観測性          | `failure-modes-observability`  | 障害モード分析             |\n| 結合, コントラクト      | `integration-contracts`        | 結合コントラクト           |\n| マイグレーション        | `migration-rollout-rollback`   | マイグレーション計画       |\n| マルチテナント          | `multitenancy-isolation`       | テナント分離               |\n| OpenAPI                 | `openapi-contract`             | OpenAPI 仕様検証           |\n| SLO, 運用性             | `operability-slo`              | 運用性・SLO                |\n| 要件, 受入              | `requirements-acceptance`      | 要件・受入条件             |\n\n### デフォルト動作\n\n- キーワード指定なし → 変更内容から自動判定\n- 複数カテゴリに該当 → もっとも関連性の高いスキルを優先\n\n## Execution Flow \u002F 実行フロー\n\n```text\n1. 変更種別の判定\n   ├─ ADR\u002F設計ドキュメント → adr-decision-quality を優先\n   ├─ API定義\u002Fエンドポイント → api-design, api-versioning-compat を優先\n   ├─ モジュール構成変更 → architecture-boundaries を優先\n   ├─ データモデル変更 → data-model-db-design を優先\n   └─ キーワード指定あり → 該当スキルを直接選択\n\n2. スキルの実行（該当する専門スキルを並列実行可能）\n   ├─ 設計品質系: adr-decision-quality, architecture-diagrams, architecture-traceability\n   ├─ 構造系: architecture-boundaries, bounded-context-language, data-flow-state-ownership\n   ├─ API系: api-design, api-versioning-compat, openapi-contract, integration-contracts\n   ├─ 運用系: availability-architecture, capacity-cost-design, dr-multiregion, operability-slo\n   └─ リスク系: architecture-risk-register, failure-modes-observability, external-dependencies\n\n3. 統合\n   ├─ 重複する指摘の除去\n   └─ 複数カテゴリ該当時は関連性の高いスキルを優先\n```\n\n## Output Format \u002F 出力形式\n\n```text\n\u003Cfile>:\u003Cline>: \u003Cmessage>\n```\n\n- **Finding**: 何が問題か（1文）\n- **Impact**: 何が困るか（短く）\n- **Fix**: 次の一手（最小の修正案）\n\n## 他スキルとの関係\n\n| スキル                  | 関係 | 棲み分け                                                      |\n| ----------------------- | ---- | ------------------------------------------------------------- |\n| `adversarial-review`    | 補完 | architecture は「設計の正しさ」、adversarial は「設計の盲点」 |\n| `river-review-security` | 補完 | architecture は「構造」、security は「脆弱性」                |\n| `river-review-code`     | 補完 | architecture は「マクロ設計」、code は「ミクロ品質」          |\n\n## References\n\n- [ROUTING.md](.\u002Freferences\u002FROUTING.md): 詳細なルーティングルール\n",{"id":5,"name":5,"tags":44,"phase":45,"applyTo":46,"license":15,"version":51,"category":32,"severity":52,"outputKind":53,"description":55,"inputContext":56},[24,38,36,25],[32],[47,48,49,50],"src\u002F**\u002F*.{ts,tsx,js,jsx,mjs}","docs\u002F**\u002F*design*.md","docs\u002Fadr\u002F**\u002F*","pages\u002F**\u002F*design*.md","0.1.0","major",[54,34,26],"findings","設計・アーキテクチャ観点のレビューエージェント。\n依存関係、境界設計、データモデル、API設計等の個別スキルへルーティングする。\n",[30,57,29],"fullFile","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Friver-review-architecture",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill river-review-architecture",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill river-review-architecture",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill river-review-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Friver-review-architecture\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002FROUTING.md","REFERENCE","参考文档",4003,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Friver-review-architecture\u002Freferences\u002FROUTING.md",[89,98,105,112,138,162],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":97},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":97},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":39},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[119,120,121,122,123,124,125,126,127,38,128,129,130,131,132,133,134,135,136,137],"search","deja search","never","error","ready","memory","re","decide","fix","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":39},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[145,146,19,133,147,148,149,150,151,152,153,154,155,156,124,157,158,159,160,161],"deja reflect","reflect","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":179,"publishedAt":39},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[168,173,176],{"categoryNo":169,"categoryName":170,"taxonomyType":171,"taxonomyTypeDesc":172},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":174,"categoryName":175,"taxonomyType":171,"taxonomyTypeDesc":172},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":177,"categoryName":178,"taxonomyType":171,"taxonomyTypeDesc":172},"01JBSEEDCAT000000000000010","后端与接口",[164,180,181,182,183,184,185,158,186,125,187,188,189,190,129,191,192,193,194,195],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]