Design review
Store function id: design-review. Price and full description: Design review in the store catalog.
What it is for
Section titled “What it is for”One worker that reviews product and website material for clarity, ease of use, accessibility and visual quality, and returns findings by severity with a verdict. It may open pull requests with its revisions in a repository you allow.
Who can do this
Section titled “Who can do this”- The administrator subscribes, answers the install questions and allows the permissions.
- Administrators and members give the workers tasks in Chat.
Before you start
Section titled “Before you start”- The box is enrolled with the store and the function is subscribed. See Store.
- In Owner policy, allow the permissions marked “Tick it” or with a value below. Permissions with an install question are allowed by your answer. See Owner policy.
- GitHub must be connected and list the repository to review.
Facts on this page come from the packages’ published definitions (checked on 8 October 2026). Your box shows the same facts before Install, under Permissions.
The worker
Section titled “The worker”Ivo V2
Section titled “Ivo V2”Package id faivr.agent.ivo-design-v2, version 1.0.0.
Reviews the product or website material you give it for clarity, ease of use, coherence, accessibility, trust, quality on all screen sizes and a visual style that is not generic. It returns findings ordered by severity, revisions you can act on, and a clear verdict.
Permissions in plain words
| Permission | Install question | In Owner policy |
|---|---|---|
| Read files in its own workspace | None | Tick it |
| Create and change files in its own workspace | None | Tick it |
| Run commands inside its sandbox | None | Tick it |
| Reach the internet through the allowlist proxy | None | Tick it |
| Render web pages and take screenshots with the browser inside its sandbox | None | Tick it |
| Read one repository | “Which repository should this worker review?” | Allowed by your answer |
| Push its own branches and open pull requests on one repository, never merges (includes read) | “In which repository may it open pull requests with its revisions?” (optional) | Allowed by your answer |
| Read one product’s knowledge | “Which product’s knowledge may it read for context?” (optional) | Allowed by your answer |
| Read the workboard | None | Tick it |
| Change the workboard | None | Tick it |
| Run in one model lane: Standard | None | Run in one model lane: choose standard and press Allow |
Install questions
- “Which repository should this worker review?” Required. You choose a repository of your GitHub connection.
- “In which repository may it open pull requests with its revisions?” Optional: Skip (the permission is declined) is offered. You choose a repository of your GitHub connection.
- “Which product’s knowledge may it read for context?” Optional: Skip (the permission is declined) is offered. You choose a product of the box.
Default autonomy levels
Shown and changed under Administration, Packages, panel Autonomy levels. It has no protected actions, so it never asks for an approval unless you raise a level to “Asks you first”.
| Kind of action | Default level | You can raise it to |
|---|---|---|
| Reads its own workspace | Runs on its own | cannot be raised (Fixed) |
| Writes files in its own workspace | Runs on its own | Tells you after, Waits for your check |
| Reaches the internet through the box’s list | Runs on its own | cannot be raised (Fixed) |
| Renders web pages in its sandbox | Runs on its own | cannot be raised (Fixed) |
| Reads repositories | Runs on its own | cannot be raised (Fixed) |
| Pushes its own branches and opens pull requests | Tells you after | Waits for your check |
| Reads company knowledge | Runs on its own | cannot be raised (Fixed) |
| Reads the workboard | Runs on its own | cannot be raised (Fixed) |
| Changes the workboard | Tells you after | Waits for your check, Asks you first, Always asks, with a reason |
What every worker can never do
Section titled “What every worker can never do”- Work outside its own closed workspace on the box.
- Reach hosts, repositories or products it was not given.
- Merge on GitHub, push to the default branch, or create tags or releases.
- Read a stored key or password.
Example tasks
Section titled “Example tasks”Write these in Chat after choosing the worker. Change the details to your company.
- “Review the sign-up page in the review repository for clarity and accessibility, and give your verdict.”
- “Render our home page and list the five most serious design problems, most severe first.”
- “Propose the revisions for your top three findings as a pull request.”