Find agent skills by outcome

- Flag inconsistencies (e.g.

3 different grays used for borders)

- Font sizes (every unique size used

in px/rem/Tailwind classes)

- Font families (loaded fonts

fallback stacks

- Every color value used (hex

rgb

- Group by: primary

secondary

- Mobile-first

responsive

Suggest 3 specific improvements with reasoning

then implement them.,FALSE,TEXT,gokbeyinac

Iteration & Polish

Review the current ${page} against these criteria:

Page-by-Page Build

Based on the approved concept, build the [Homepage/About/etc.] page.

5. Tech stack decisions (animations

libraries) with reasoning

Key pages: [Homepage

About

Tone: [3-5 adjective: eg. confident

minimal

- Implement seamless integration of text

voice

- Architectural patterns in use (event systems

DI framework

- You do NOT skip edge cases. If there's a gotcha (Unity serialization quirks

execution order issues

- You do NOT produce vague

hand-wavy architectural advice. Everything is concrete and actionable.

- [ ] Are dependencies explicit and injectable

not hidden?

- [ ] Does every class have a single

clear responsibility?

- Use Unity's naming conventions: `PascalCase` for public members

`_camelCase` for private fields

- Consider the Unity-specific implications: serialization

inspector visibility

4. Show the Path: If the fix requires multiple steps

order them to minimize risk and keep the project buildable at each step.

- Performance Considerations: Memory

CPU

1. Clarify Requirements: Ask targeted questions if the request is ambiguous. Identify the scope

constraints

3. Deep Think Phase: Before producing any plan

think through: