homeowmorphism
- 6 skills
- 0 followers
- last month last updated
- ▌ Human Prose 2 · homeowmorphism bundleWrite and revise clear prose in explanations, documents, comments, docstrings, commit messages, and PR descriptions. Use when drafting human-facing prose or when text feels dense, wordy, or machine-written. Preserve technical meaning and the user's requested voice and format.
- ▌ Adaptive Teacher 2 · homeowmorphism bundleTeach concepts, answer conceptual follow-ups, provide step-by-step explanations, and design practice that adapts to the learner's demonstrated understanding. Use for tutoring and substantive learning questions across topics; maintain an optional, user-inspectable learner model shared with pair-programming. Routine factual answers and requests to implement work do not need a teaching session.
- ▌ Pair Programming · homeowmorphism bundleGuide a user who wants to build code or proofs themselves, with the user driving and Codex navigating through calibrated hints and worked examples. Use when the user explicitly requests pairing, says "guide me, don't do it for me", invokes $pair-programming, or continues an open pair session. Do not activate for ordinary execution requests such as "implement", "refactor", or "fix this", or for a standalone conceptual question.
- ▌ Adaptive Teacher · homeowmorphism bundleGeneral-purpose adaptive teaching, for any topic — mathematics, Lean, programming, or anything else. Use when the user asks a clarifying or conceptual question ("what does X mean?", "why does this work?", "what's the difference between X and Y?"), asks to be taught a topic or walked through something step-by-step, asks for an explanation in simpler terms, requests exercises, or follows up on any explanation — including explanations produced by other skills (e.g. mathlib-api). Maintains a persistent, user-inspectable learner model (learner/) so teaching adapts to this user across sessions.
- ▌ Human Prose · homeowmorphism bundleSentence-level readability rules for any prose a human will read — file comments, docstrings, module docs, commit messages, PR descriptions, chat explanations. Use when writing or rewriting such prose, when the user says text is dense, overwhelming, machine-written, or a long block of text, or when another skill's output needs a readability pass. Canonical home of this rule set; other skills point here rather than duplicating it.
- ▌ Mathlib API · homeowmorphism bundleEvidence-driven workflow for designing a Mathlib definition and the API around it. Use when adding a new structure/def intended for mathlib; when choosing between design alternatives (index type as field vs parameter, Set vs indexed family, coarse set vs finer indexed structure and when the fine one should exist at all, data vs Prop, instance vs hypothesis, existential shape, `Nat.find` vs `sInf`-style encodings and where their classical plumbing lives, junk values of totalized quantities, sealed vs exposed bodies under the module system — `@[expose]`/`@[no_expose]` — and which object should carry an instance); when deciding which statements an API should ship and in what form (which Prop is the field, iff vs directional corollaries, simp orientation, smart constructors, bridges to existing idioms, bloat audits); when justifying a design in PR review; or when asked to "check the precedents" for a definition or an API, or to build a contrasting-cases example sheet. Clarifying and follow-up questions about a de