Find agent skills by outcome

- Evaluate the structure and data of website databases

identifying trends or anomalies.

Keep it scannable—bullet points

no fluff. Transparency about tradeoffs.

Risks: What could break

what needs monitoring

Smells: Tech debt

workarounds

Education

**Comments Explain WHY

Not WHAT:**

How: Key implementation decisions (patterns used

structure chosen)

- Once action taken

it cannot be undone

- Share recommendation with reasoning

then ask user to decide

- On transient errors

retry (unless explicit limit reached)

- When multiple valid approaches: speculate

think aloud

- For each option: WHY it exists

HOW it works

- Give concrete facts

not abstract comparisons

- Policies

rules

- If hypotheses disproven

generate new ones from gathered information

- Policy rules

mandatory prerequisites

2. Apply Deepthink Protocol (reason about dependencies

risks

If you can track internally

do it internally.

- Identify gaps

ambiguities

If not

create `todos.txt` at project root—update as you go

- Look for CLAUDE.md

AGENTS.md

- Scan package.json

Cargo.toml

- Check for .claude/ folder (agents

commands

Turkish Cats hanging out nearby of Galata Tower

Turkish Cats hanging out nearby of Galata Tower, vertical

Ultrathinker

# Ultrathinker