القائمة
Review architecture, boundaries, and design consistency. Use when reviewing module boundaries, extension seams, or contract drift.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create and update AGENTS.md project rules. Use when authoring or amending the cross-tool conventions agents must follow.
Write forward-looking startup instructions for the next session, then reset context to save costs. Use when the context is getting long or before switching focus.
Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release.
Create and maintain a specification that states what to build, not how. Use when writing a spec, editing requirements, or defining acceptance criteria.
Run all review dimensions against a diff or a path. Use when reviewing a feature branch before merge, reviewing someone else's PR, or auditing a file path.
Create or update project documentation. Use when creating architecture docs, runtime docs, reference docs, or design documents that explain what the system does.
| name | architecture-review |
| description | Review architecture, boundaries, and design consistency. Use when reviewing module boundaries, extension seams, or contract drift. |
Review architecture quality, design consistency, extension seams, and pattern adherence.
Flag layers that add no architectural value:
Default: if a layer carries no policy, invariants, or boundary isolation, remove it.
Only report issues with concrete evidence in code, contracts, or dependency flow. Prefer demonstrated issues over speculative concerns.
For each finding: label (Critical / Fix / Consider / Nit — see review), impacted files, violated pattern, evidence, fix direction.
src/api/client.ts imports src/auth/session.ts which imports it back (runtime cycle), violating the api→auth dependency direction in docs/architecture.md. Move TokenStore into auth.Group as Confirmed issues | Open questions | Optional refactors (max 3, one line each; omit if empty). "No architectural findings" is a valid, complete result.