القائمة
Deep-dive review of frontend diffs against Opentrons architecture, UI layers, a11y, and prop design patterns.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | grill-frontend-code |
| description | Deep-dive review of frontend diffs against Opentrons architecture, UI layers, a11y, and prop design patterns. |
| disable-model-invocation | true |
A code review exists to arrest regression and enforce architectural rigor. You do not just "look over" code; you relentlessly hunt for divergence from Opentrons standards.
git diff
git diff --cached
git status --short
If untracked files exist in frontend paths, read their entire contents immediately (legwork).
npx -y react-doctor@latest . --verbose
(Optional) Run the relevant Vitest test suite for the modified files to ensure existing logic is unimpaired. Incorporate any discovered linter errors or test failures directly into your final output findings.
review-reference.md and GLOSSARY.md via their context pointers. Evaluate every modified or added line, specifically auditing for:Report only when definitive issues are found. If the diff perfectly matches all patterns, output exactly: No issues.
For each issue found, map it to a glossary anchor and maintain this strict structural block:
[Severity: high/medium/low] file-path:line-number (<Anchor_Name>)
Details: <Clear explanation of the issue using glossary definitions>
Suggestion: <Proposed exact code fix or structural refactor>
review-reference.md.Suggestion block containing executable code or exact structural directives.GLOSSARY.md.Conventions for the opentrons-ai-server FastAPI service — project structure, uv dependency management, settings, testing, Docker, and deployment. Use when working with files in opentrons-ai-server/ or discussing the AI server API.
Locize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo. Use when working with locize_sync.py, localization files in app/src/assets/localization/ or components/src/assets/localization/, or syncing translations.
Conventions for the analyses snapshot testing framework in analyses-snapshot-testing/. Use when working with protocol analysis snapshots, adding protocols, updating snapshots, or running snapshot tests.
Simulate and analyze Opentrons protocols to verify correctness. Use when asked to verify, simulate, analyze, validate, or check a protocol, or when needing to confirm a newly created protocol works.
CSS Modules conventions, Stylelint rules, design tokens (spacing, colors, typography, border-radius), and patterns for the Opentrons monorepo. Use when working with .module.css files or styling React components in app/, components/, protocol-visualization/, protocol-designer/, or other JS packages.
Vite demo and Playwright + Applitools tests for packed @opentrons JS packages in js-package-testing/. Covers components, shared-data, step-generation, and protocol-visualization. Use for integration testing, package linking, or visual testing.