Github Pages Generation
Michel's methodology for spinning up a beautiful, low-maintenance GitHub Pages site for a repository — static HTML + TailwindCSS CDN by default, Jekyll only when needed. Use whenever the user asks to "create GitHub Pages", "publish docs", "make a landing page for the repo", "set up a project website", "enable Pages", "deploy a docs site", or wants a public showcase / index of repo contents (skill…
Pr And Branch Hygiene
Michel's standards for branch naming, commit discipline, and pull-request authoring across all projects. Use whenever the user creates a branch, opens or updates a pull request, prepares a commit, drafts a PR description, or asks how to organize work for review. Triggers on phrases like "open a PR", "push the branch", "create a commit", "draft PR description", "ready for review", "merge this", an…
Eval Development
Michel's personal methodology for eval-driven development of AI translation (and similar AI service) fixes in <your AI services project>. Use whenever the user asks to "build an eval", "set up an eval", "write an eval suite", "evaluate translation quality across models", iterate on translation/post-processing fixes with measurable results, or work on PBIs that follow the same eval-first pattern (…
Mermaid Diagrams
Always prefer Mermaid diagrams over ASCII art in markdown documents (READMEs, specs, ADRs, PR descriptions, reports). Use whenever the user asks for a diagram, flow, architecture sketch, sequence, state machine, ER diagram, or class diagram — and whenever you (the assistant) are about to draw boxes-and-arrows in a markdown file. Triggers on phrases like "draw a diagram", "show the flow", "archite…
Local Git Excludes
Use `.git/info/exclude` (per-clone, never pushed) or a global gitignore for personal / machine-local files instead of polluting the team `.gitignore`. Use whenever the user wants to ignore a file privately, asks "will my colleagues see this?", adds personal tooling / IDE configs / symlinks / scratch files to a shared repo, or any time you (the assistant) are about to add a line to a tracked `.git…
Research And Report
Michel's standard format for investigations, comparisons, benchmarks, experiments, and any "go look into X and tell me what you find" task. Use whenever the user asks to investigate, compare, evaluate, benchmark, analyze, audit, profile, measure, or "find out" something — and a written deliverable (markdown report) is appropriate. Triggers on phrases like "investigate", "compare", "benchmark", "e…
Spec Before Code
Michel's lightweight design-doc workflow — write a markdown spec under `specs/` before implementing any non-trivial feature, including a threat model. Use whenever the user proposes a new feature, a non-trivial refactor, a new service / endpoint / data flow, an integration with an external system, or anything touching auth, secrets, PII, or multi-tenant data. Triggers on phrases like "let's add",…
Docs Sync On Change
Whenever code, configuration, or content in a repository changes, also update the corresponding documentation surfaces — README, GitHub Pages site (`/docs/`), wiki, CHANGELOG, and any embedded examples — in the same commit/PR. Use whenever the user adds/removes/renames a feature, module, skill, package, endpoint, CLI flag, or config option, and whenever any change would make the existing docs sta…
Debugging Discipline
Michel's bug-fixing methodology — root cause first, minimal upstream fix, no over-engineering. Use whenever the user reports a bug, asks to investigate a failure, says something is broken / not working / unexpected, asks why a test is failing, requests a hotfix, or describes flaky behavior. Triggers on phrases like "this is broken", "fix the bug", "investigate", "why does X happen", "regression",…