菜单
Enforce project coding conventions: reduce duplication, keep naming/file placement consistent, and minimize regression risk. Includes React component and layout guidelines. Use when writing or reviewing code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
When asked to review a PR or branch ("review this PR", "PR review", "argus", before merging), fan the diff out to parallel read-only reviewers and return a severity-ranked verdict; optionally post inline via gh.
When the user has reviewer feedback on a GitHub PR (human or bot like gemini-code-assist) and wants the pertinent items fixed — "j'ai des retours sur la PR", "résous/corrige ce qui est pertinent", "lis les commentaires de la PR via gh" — triage every comment thread via gh, apply only the pertinent fixes (drop nits), then reply to and resolve each triaged thread. Not for publishing our own review findings — that is argus-review --post.
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
Generate a Product Requirements Document from user instructions using the PRD template. Outputs a human-readable self-contained HTML file plus a markdown source for implementation tooling. Includes a macro-level task checklist at the end.
After modifying code, map all consumers of changed symbols and flag unhandled mismatches. Not for debugging (use systematic-debugging).
Review changed code (session, current branch, or colleague's branch) for principle violations, reinvented wheels, and dead code. Trigger after coding, before merge, or for PR review.
| name | coding-convention |
| description | Enforce project coding conventions: reduce duplication, keep naming/file placement consistent, and minimize regression risk. Includes React component and layout guidelines. Use when writing or reviewing code. |
When writing a React component, prioritize existing project libraries (shadcn, Phosphor icons, Tailwind) over custom implementations if they speed up implementation and produce clean results.
Use flexbox (flex, flex-col, flex-row) by default for layouts.
Only use grid when the layout is truly tabular (columns and rows aligned across independent rows) or when CSS grid offers a concrete advantage that flex cannot easily reproduce.
// ✅ DO — layout avec label fixe + contenu flexible
<div className="flex gap-5">
<h2 className="w-55 shrink-0">Section</h2>
<div className="flex-1">...</div>
</div>
// ✅ DO — paires label/valeur
<div className="flex gap-4">
<dt className="w-40 shrink-0 text-sm font-medium text-gray-500">Label</dt>
<dd className="flex-1 text-sm text-gray-900">Valeur</dd>
</div>
// ❌ AVOID — grid pour un layout simple à deux colonnes
<div className="grid grid-cols-2 gap-4">
<dt>Label</dt>
<dd>Valeur</dd>
</div>
Checklist: See checklist.md for a consistency reference.