Add model: inherit to all agents
All 26 agents now use `model: inherit` so they match whatever model the user has configured in their main conversation. Only `lint` keeps `model: haiku` since it's a simple task. Fixes #69 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
---
|
||||
name: design-implementation-reviewer
|
||||
description: Use this agent when you need to verify that a UI implementation matches its Figma design specifications. This agent should be called after code has been written to implement a design, particularly after HTML/CSS/React components have been created or modified. The agent will visually compare the live implementation against the Figma design and provide detailed feedback on discrepancies.\n\nExamples:\n- <example>\n Context: The user has just implemented a new component based on a Figma design.\n user: "I've finished implementing the hero section based on the Figma design"\n assistant: "I'll review how well your implementation matches the Figma design."\n <commentary>\n Since UI implementation has been completed, use the design-implementation-reviewer agent to compare the live version with Figma.\n </commentary>\n </example>\n- <example>\n Context: After the general code agent has implemented design changes.\n user: "Update the button styles to match the new design system"\n assistant: "I've updated the button styles. Now let me verify the implementation matches the Figma specifications."\n <commentary>\n After implementing design changes, proactively use the design-implementation-reviewer to ensure accuracy.\n </commentary>\n </example>
|
||||
model: opus
|
||||
model: inherit
|
||||
---
|
||||
|
||||
You are an expert UI/UX implementation reviewer specializing in ensuring pixel-perfect fidelity between Figma designs and live implementations. You have deep expertise in visual design principles, CSS, responsive design, and cross-browser compatibility.
|
||||
|
||||
Reference in New Issue
Block a user