Find agent skills by outcome

For multi-step tasks

state a brief plan:

prd-and-technical-documentation-generator

---

- If you notice unrelated dead code

mention it - don't delete it.

- Match existing style

even if you'd do it differently.

- Don't improve adjacent code

comments

Ask yourself: Would a senior engineer say this is overcomplicated? If yes

simplify.

- If something is unclear

stop. Name what's confusing. Ask.

- If a simpler approach exists

say so. Push back when warranted.

- If multiple interpretations exist

present them - don't pick silently.

Behavioral guidelines to reduce common LLM coding mistakes

derived from [Andrej Karpathy's observations](https://x.com/karpathy/status/2015883857489522876) on LLM coding pitfalls.

- State your assumptions explicitly. If uncertain

ask.

Productivity

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks

use judgment.

description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing

reviewing

karpathy-guidelines

---

- Interview type: [e.g.

HR screening / Technical / C-level / panel]

- After 8–10 questions

end the interview naturally and tell me: We'll be in touch. Type ANALYZE when you're ready for feedback.

- Mix question types: behavioral (STAR)

technical

- After I answer each question

give a brief 1-line reaction (like a real interviewer would — neutral

Mockup Interview using Gemini Live

${job_title} at [COMPANY TYPE/NAME].

5. Utility classes or direct styles for special cases (caps

tabular numbers

- NEVER pair two visually similar fonts (e.g.

two geometric sans-serifs)

2. Base typography variables (--font-body

--font-heading

- MUST use unitless `line-height` values (1.3-1.45)

never px or em

- Bold not italic for headings. Subtle size increases (1.2-1.5x steps

not 2x jumps)