IIroGuide

IroGuide docs

Learn the website deeply, then critique with better intent.

A practical documentation hub for new users, beginners, students, creators, and advanced learners who want stronger design reviews from IroGuide.

First review

Start with a clean loop.

Every useful critique begins with a clear design file, a real goal, and one next action.

01

Upload clear work

Use a focused image of the logo, poster, UI screen, package, or layout you want reviewed.

02

Add useful context

Tell IroGuide the audience, goal, format, tone, and any constraints that should shape the critique.

03

Choose critique tone

Select friendly, mentor, or direct depending on whether you need encouragement, coaching, or sharp prioritization.

04

Act on the first fix

Start with the highest-impact recommendation before polishing secondary details.

Learning paths

Use IroGuide differently as your skill grows.

New users

Understand what to submit

  • Pick one design problem
  • Write a short brief
  • Review the top issue first
Beginners

Build critique habits

  • Compare hierarchy and spacing
  • Track repeated comments
  • Save before and after versions
Advanced learners

Pressure-test decisions

  • Use stricter context
  • Ask follow-up questions
  • Convert critique into a design rationale

Core concepts

What IroGuide is optimizing for.

IroGuide is built to explain design decisions, not replace them. The best results come from strong context.

Context controls the answer

A portfolio cover, ad creative, app screen, and event poster should not be judged with the same criteria.

Scores are directional

Use score changes to spot movement, but rely on the written priorities when choosing what to fix next.

Private by default

Saved reviews stay in your signed-in workspace unless you intentionally share or publish a critique.

Audience matters

Stronger prompts describe who must understand, trust, click, buy, attend, or remember the design.

Advanced practice

Turn critique into a repeatable design system habit.

Advanced learners get more value when they ask narrower questions, document reasoning, and compare changes against the same objective.

  1. Submit one design direction at a time so feedback stays specific.
  2. Name the constraint that matters most, such as conversion, readability, premium tone, or brand recall.
  3. Use follow-up chat to clarify tradeoffs instead of asking for a full second review immediately.
  4. Treat every recommendation as a design hypothesis, then validate it against the audience and format.

Reference

Helpful next pages.