Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

hadden-industries

@hadden-industries source repo

4 published skills

  1. ▌
    Reading Epubs · hadden-industries bundle
    Use when a task needs the content of an EPUB - inspecting, searching, quoting, summarizing, analyzing, or extracting from a file that is EPUB or has an .epub extension. Converts the book to cleaned Markdown first, so always use this workflow instead of treating EPUB as natively readable or relying on an agent/runtime EPUB preview. Do not use for producing or converting content into EPUB, for other ebook or document formats such as PDF, MOBI, or AZW3, for organizing or renaming ebook files without reading them, or for writing code that parses EPUB.
    0
    installs
  2. ▌
    Committing To Git · hadden-industries bundle
    Drafts or revises commit messages for current workspace changes, guides creation of a signed commit from an approved staged snapshot, reports whether the result matches, and optionally pushes that exact commit. Use for a requested message draft, new local commit, or that workflow's push. Do not use to amend history or finish merge, rebase, cherry-pick, or revert operations.
    0
    installs
  3. ▌
    Defining Concepts · hadden-industries bundle
    Engineers source-grounded concepts and definitions, including definition, revision, audit, comparison, mapping, formalization, multilingual equivalence, and epistemic-governance work. Use for deliberate semantic work on a concept's identity, boundary, designation, reuse, relation, or representation. Do NOT use for casual dictionary lookup, code-symbol naming, product or brand naming, copyediting without semantic work, or implementation-only requests.
    0
    installs
  4. ▌
    Naming Objects In Software Engineering · hadden-industries bundle
    Create, assess, and refactor semantically precise, ecosystem-conformant names for programming and data artefacts. Use whenever naming or renaming files, directories, packages, modules, types, functions, methods, parameters, arguments, variables, fields, properties, constants, APIs, CLI commands/options, environment variables, or database objects; and during code review when naming quality, consistency, ambiguity, or terminology is relevant. Enforces conceptual discrimination before casing and separators.
    0
    installs