liam-gemini
- 7 skills
- 0 followers
- 21 hours ago last updated
- ▌ My Engineering · liam-gemini bundleRun the user's adaptive end-to-end software delivery workflow and compose the installed mattpocock skills. Use when the user explicitly asks for their engineering workflow, asks which engineering skill or delivery path to use, or invokes $my-engineering for feature, bug, architecture, review, planning, implementation, or research work.
- ▌ Grill My Design · liam-gemini bundleRelentlessly stress-test a software plan or design using the user's engineering principles, repository evidence, domain modeling, and controlled documentation. Use only when the user explicitly invokes $grill-my-design or asks to use their personalized design-grilling workflow.
- ▌ Evolve My Skills · liam-gemini bundleConvert explicit interaction feedback, repeated failures, high-cost mistakes, or unusually effective patterns into reviewed improvements for the user's personal Codex skills. Use only when the user explicitly invokes $evolve-my-skills or asks to capture, review, promote, or apply lessons to their personal skills.
- ▌ Karpathy Guidelines · liam-gemini bundleBehavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
- ▌ How To Ask Good Questions · liam-gemini bundleTurn vague technical or work-related confusion into clear, answerable questions by exposing current understanding, isolating unknowns, defining goals, and choosing a suitable audience. Use when drafting or improving questions for coworkers, experts, maintainers, forums, issue trackers, code reviews, debugging help, or learning unfamiliar concepts.
- ▌ Personal Engineering Principles · liam-gemini bundleApply the user's stable cross-project engineering preferences to software planning, design, implementation, debugging, and review. Use automatically when a recommendation or trade-off would benefit from the user's established engineering defaults; project-specific rules still take precedence.
- ▌ How To Get Useful Answers To Your Questions · liam-gemini bundleHelp users actively steer technical or work conversations toward useful answers by checking their mental model, narrowing vague explanations, interrupting irrelevant tangents politely, clarifying terminology, and asking focused follow-ups. Use when an answer is confusing, overly broad, jargon-heavy, condescending, incomplete, off-topic, or fails to resolve the original question.