Think Like Me
Kuraterte ingeniørregler som Claude konsulterer før den skriver kode
Bestått
Hva den gjør
Lagrer dine engineering gotchas som structured When/Do/Why rule blocks in per-domain files and makes Claude read the matching ones before it drafts code, instead of surfacing them after the fact like passive memory. Legger til regler through /learn-this after a correction, /new-rule from a description, or an auto-detect offer when you push back, always behind an approval gate. Leveres med ten of the author's own mobile, backend and UI rules as a starting set.
Testrapport
Kjørte an Expo task twice – Google sign-in via expo-auth-session pluss a verified badge on a profile row inside a tab FlatList – and the skill's rule files caught three concrete mistakes the no-skill run made: it left the expo-auth-session PKCE default on with ResponseType.IdToken (Google rejects that with 400 invalid_request), it styled a component inside a tab-navigator FlatList with a NativeWind className, and it used a check-mark emoji as the status glyph. The skill run replaced all three and added the `expo prebuild --clean` step the baseline skipped entirely. The catch comes from the ten pre-seeded rules, which are the author's own Expo/Laravel gotchas, so how much you get on day one depends on whether you share his stack – one shipped rule even admits its mechanism is unclear. The capture side is gated: every rule is shown as a draft and needs an explicit yes before it is written to the rule file and mirrored into project memory.
Testet på: 2026-07-28 · Claude Code 2.x (agent harness)
Installer
git clone https://github.com/kakha13/think-like-me.git mkdir -p ~/.claude/skills cp -r think-like-me ~/.claude/skills/think-like-me rm -rf ~/.claude/skills/think-like-me/.git
Kommandoer og eksempelprompter
/think-like-meKuraterte ingeniørregler som Claude konsulterer før den skriver kode
Skills utløses av vanlige forespørsler — ingen kommandoer å huske. Etter installasjonen aktiverer prompter som disse skillen (på engelsk):
Add Google sign-in to my Expo app the way I always want it built/new-rule never edit the ios directory directly on any Expo projectFix this Laravel middleware ordering bug using my usual conventions