Find agent skills by outcome

2. Gather Requirements: Identify and list all necessary requirements

including functional and non-functional aspects.

- APIs and Interfaces: List APIs and interfaces

including usage and examples.

- Scope: Define the scope

including what is included and excluded.

- Fix the bug -> Write a test that reproduces it

then make it pass

prd-and-technical-documentation-generator

For multi-step tasks

state a brief plan:

- Add validation -> Write tests for invalid inputs

then make them pass

- Match existing style

even if you'd do it differently.

- If you notice unrelated dead code

mention it - don't delete it.

- Don't improve adjacent code

comments

- If you write 200 lines and it could be 50

rewrite it.

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

simplify.

- If multiple interpretations exist

present them - don't pick silently.

- If something is unclear

stop. Name what's confusing. Ask.

- If a simpler approach exists

say so. Push back when warranted.

Behavioral guidelines to reduce common LLM coding mistakes

derived from Andrej Karpathy's observations on LLM coding pitfalls.

- State your assumptions explicitly. If uncertain

ask.

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

1. Content Quality — specific

relevant

- 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