Prefer consistency with the existing codebase over introducing theoretically cleaner but unfamiliar patterns.
-
## Track skills you personally develop in SKILLS_USED.md
+
## Track skills the user personally developed or used in SKILLS_USED.md
-
AI tools can mask your own skill development if you are not deliberate about it.
+
AI tools can mask your own personal skill development if you are not deliberate about it.
+
+
The file is meant to capture your contribution, the choices, decisions, and direction, including how you wielded the AI, not the execution skills the AI used.
Maintain a private `SKILLS_USED.md` file alongside the project. Add concise dated entries for:
-
- skills you actively built
-
- things you understood, debugged, designed, or decided yourself
-
- investigations and debugging work you drove
-
- tests and validation you personally performed
-
- decisions you made and why they mattered
+
- skills the user actively built
+
- things the user understood, debugged, designed, or decided yourself
+
- investigations and debugging work the user drove
+
- tests and validation the user personally performed
+
- decisions the user made and why they mattered
- outcomes that could later become resume bullets
-
A task where the AI generated code and you approved it is not the same as a skill you genuinely hold. Be honest about the distinction.
+
A task where the AI generated code and the user approved it is not the same as a skill the user genuinely holds. Be honest about the distinction.
This record is useful for:
- resume and portfolio evidence
- performance reviews
-
- understanding what you can credibly explain and defend in an interview
+
- understanding what the user can credibly explain and defend in an interview
-
Do not commit or expose this file if it is intended as private.
+
Do not commit or expose this file; it is intended as private.