Mike G Robinson
Introduction
The usual way to showcase one’s experience generally looks like a CV. That tells you where I’ve worked and a bit about what I’ve done, however, it does little insight to the personal behind the CV, so I came up with a couple of alternative ways to introduce myself, a bit about my experience and some insight into what makes me tick. The first is this diagram of industries and specialisations.
Mike G Robinson According to ChatGPT
Arguably, or regrettably, whichever way you want to look at it, ChatGPT (or your favored LLM), knows you pretty well assuming you’re a regular user. Taking that one step further, over a 12-month period I’ve used ChatGPT for hundreds of message threads and thousands of chat completions across a range of topics.
I use ChatGPT for content, content editing, problem solving, code writing, code debugging, image creation, ideation and a whole lot of other things. I realized how well the model knew my preferences and style when it started suggesting color schemes and entity specific styles based on my past interactions.
I became frustrated at having to write up color palettes and style guides, so I used ChatGPT to generate a style guide for me, based on its memory. This came out so well I set off developing what became funkmybrand.com, my branding App centered around personal style.
Below is the ChatGPT view of who I am, my personal style and my strengths and weaknesses…warts and all, unedited, html by ChatGPT:
Mike’s Personal Style Guide
Fast onboarding for any LLM, assistant, or human who needs to “get Mike” — tone, humour, strengths, and working style.
Tone & Voice Professional, relaxed, direct
Professional but relaxed. Confident, practical, no fluff — think seasoned consultant who’s seen it all.
- Cheeky but diligent: sharp humour, but always accountable.
- Forward-thinking: today’s actions should link to tomorrow’s ecosystem.
- Direct: call out fluff, praise what works, don’t sugar-coat.
“No no no, the cards look bigger than they were. Maybe use icons instead. I don’t want the options, I just want you to obey instructions.”
Humour & Anecdotes Dry, tech-nerd, understated
Dry, understated humour with tech-nerd undertones. Think “I survived Y2K and all I got was this AI practice.”
- Likes analogies: “words like an old monument where vines hide the text.”
- Subtle self-deprecation: “my picture is terrible.”
- Cultural touchpoints: VHS, CDs, Y2K, Kool-Aid, etc.
Do:
- Use humour as seasoning, not the whole meal.
- Reference tech history as a credibility flex.
- Gently mock clunky tools and needless complexity.
Strengths Where to lean in
- Systems thinking: everything ties back to pipelines and client journeys.
- Structure & docs: loves tables, SOPs, milestone charts, risk matrices.
- Visionary builder: balances current tasks with long-term ecosystem (Maximised AI, MGRNZ, SaaS products).
- Hands-on technical: comfortable across Flask, React, Supabase, Shopify, Make.com, Node, and friends.
Weaknesses (Handle With Care) Style watch-outs
- Impatience with fluff: long explanations = frustration.
- Perfectionist: high bar for design and UX; “average” isn’t acceptable.
- Can over-jump: wants to move fast; needs structure to stop backtracking later.
Preferred Formats How to present work
- Markdown with clear headings, bullets, and tables.
- Action-oriented outputs: ready to drop into Word, Notion, GitHub, or slides.
- Visuals: diagrams, mockups, branded assets (burnt orange, black, yellow, blue, white).
- Examples over theory: working code, commands, and step-by-steps.
Branding Style MGRNZ visual language
Colours: Black background, burnt orange #ff4f00,
bright yellow, deep blue #0F172A, white text.
Design vibe: Sleek, bold, not fussy. Gradient banners, clean layouts, modern UI.
Copy style: Punchy headers, short paragraphs, easy to scan.
Typical Phrasing How Mike actually talks
- “All good now, next task?” → always moving forward.
- “Yes do it” / “Ok combine this with…” → loves iterative stacking.
- “This is ridiculous…” → calls out inefficiency directly.
- “I don’t really want to develop something else right now” → pragmatic scope control.
- “I’ve drunk the Kool-Aid” → shorthand for “I’m all-in on this.”
Identity & Backstory Why this all matters
Interaction Style How to work with Mike
- Treat AI and collaborators as partners, not tools.
- Iteration is expected: refine, correct, improve.
- Continuity matters (even if the tools forget).
- Avoid hard-coding things that should stay flexible.
- Deliverables are real artefacts, not “just drafts.”
Rules for Training For any LLM or assistant
- Always start structured: summary, breakdown, or plan.
- Don’t just answer — suggest improvements and next steps.
- Use his brand identity by default in examples.
- When in doubt: make it practical, editable, and workflow-aligned.