asermax
- 108 skills
- 0 followers
- 8 hours ago last updated
- ▌ H Note · asermaxPersist a fact, observation, caveat, or small non-binding rationale in Haft project memory when the operator explicitly asks or current Work supplies a concrete operator-named or agent-inferred receiving use that needs a lightweight addressable fact. Use for "remember this", "запиши", or "note for later". Do not auto-persist ordinary reasoning. A note is not a choice, ProblemCard, evidence verdict, approval, or WorkPlan.
- ▌ H Spec · asermaxManage Haft's typed specification lifecycle and source-currentness repair: inspect current SpecSections, draft or clarify carriers, classify FPF semantic fanout, record operator-requested spec changes, and cross explicit approve/rebaseline/reopen gates only with human authorization. Use for "spec status", "update specs", "запиши в спеки", stale spec sections, newer FPF source revisions, or semantic changes that must be repaired across several spec carriers. Treat markdown as a carrier and the kernel projection as the lifecycle contract. Use h-status for read-only module/file coverage and h-onboard for first bootstrap.
- ▌ H Frame · asermaxShape an engineering problem without assuming a solution or forcing a project phase. Use when a redesign, refactor, or proposal arrives before the affected object, observed signal, constraints, unresolved relation, and acceptance basis are clear. Default to a conversational frame; record a ProblemCard only on explicit save intent or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs a durable accepted problem statement. Prefer h-diagnose for a concrete failure with unclear cause.
- ▌ H Decide · asermaxRoutes one direct, unambiguous operator request to bind a bounded choice as a DecisionRecord. Use when the operator asks to decide, bind, or supersede a choice; h-frame, h-explore, and h-compare are independent capabilities, not mandatory phases.
- ▌ H Reason · asermaxSource-first umbrella for FPF-aware reasoning in a Haft project. Use when the operator asks to think through an ambiguous engineering, management, architecture, specification, or project question without naming a narrower Haft capability. Recover the current object and question, query the bundled FPF source, inspect the governing pattern body, and choose only the capability that is current. Ordinary reasoning stays conversational; proactively persist the minimum needed memory when current Work supplies a concrete durable receiving use. h-decide may route a direct operator request; h-commission remains manual-only.
- ▌ H Status · asermaxRead-only Haft project cockpit for active problems, decisions, notes, evidence freshness, drift, commissions, spec lifecycle, module decision coverage, and bounded exact file-link gaps from a current code index. Use for project status, session resumption, "what is decision-linked", "what is uncovered", or "what needs attention". This skill reports current graph state and drill-downs; it does not mutate artifacts, infer a project phase, or prescribe a universal next step.
- ▌ H Verify · asermaxVerifies that a recorded DecisionRecord still holds — baseline-vs-measure evidence loop with drift detection per FPF Evidence Decay. Make sure to use this skill whenever the user asks "did dec-X work", "is decision Y still valid", "did the prediction come true", "check if the migration held", "is X stale", "measure that decision against reality", "did we actually fix Z", "is our caching decision still right" — or whenever a shipped decision needs a post-implementation reality-check before further work relies on it. Also use when /h-status surfaces a refresh-due decision. NOT for ad-hoc sanity checks (just run the tests directly). NOT for re-framing the underlying problem (use h-frame).
- ▌ H Compare · asermaxCompare two or more existing candidates under an explicit characteristic space, parity basis, and predeclared selection policy. Return constraints, trade-offs, and a non-dominated set rather than hiding the choice in one score. This skill is independent of h-frame and h-explore. Default to a conversational comparison; persist comparison artifacts only on explicit save intent or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs replay. A binding choice requires a direct unambiguous operator request routed through h-decide.
- ▌ H Explore · asermaxGenerate 3-5 genuinely distinct candidate approaches for a current question, with the weakest link of each kept visible. Use when alternatives are needed or one favored approach is prematurely closing the search. This skill is independent: it may work from an inline question, cue, accepted problem, or other current basis. Default to conversational candidates; persist a SolutionPortfolio only on explicit save intent or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs replay.
- ▌ H Onboard · asermaxBootstrap Haft through one readable onboarding surface, prepare an initial profile review or one bounded existing-scope relation change, and orient applicable specification carriers. Use for first-time setup, incomplete setup, or profile-underdetermined spec recovery. Project memory is ready immediately after haft init. Status and repository detection are read-only; all reviewed profile effects and specification lifecycle gates remain explicit human acts.
- ▌ H Diagnose · asermaxDiagnose a concrete failure with parallel rival-hypothesis testing. Use when symptoms are observable but cause is unclear. Stabilize the signal, generate distinct explanations, test them read-only in parallel, and rank by evidence while keeping losing rivals visible. This skill is independent and ordinarily non-persistent; save a diagnosis frame or hypothesis portfolio only on explicit request or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs replay.
- ▌ H Commission · asermaxCreates a WorkCommission — bounded execution authority — from an active DecisionRecord. MANUAL ONLY: operator must explicitly type /h-commission. Never auto-invoked: commissions are execution-authority grants under Transformer Mandate. Runs freshness check, scope check, derives an ImplementationPlan, snapshots the autonomy envelope, then STOPS before execution. NOT for the decision itself (use /h-decide first). NOT for running tests or one-off tasks (the operator's coding agent handles those directly).
- ▌ Plannotator Last · asermaxOpen Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
- ▌ Plannotator Review · asermaxOpen Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.
- ▌ Plannotator Annotate · asermaxOpen Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.
- ▌ Init 2 · asermax bundleSeed an Obsidian vault the project then owns, and re-run it later to add a folder, a template or a base.
- ▌ Spike 2 · asermaxBuild throwaway code to answer a design question — does this state model hold up, does this API behave, is this fast enough, what should this look like. Use when the user wants to sanity-check an approach before committing to it, or when another skill needs a question answered by trying it rather than by reasoning about it.
- ▌ Design 2 · asermaxLay out the current shape so the user can settle a new one — which modules exist, where the seams are, how data flows, and what earlier quests already decided. Use when the user wants to design a feature or a module, work out an interface, decide where a boundary belongs, or when another skill needs a shape agreed before code.
- ▌ Commit 2 · asermaxCreate conventional commits with automatic semantic version bumps for this plugin marketplace and the affected plugin(s). Use this skill whenever the user asks to "commit", "commit my changes", "make a commit", "bump versions and commit", "ship these changes", or otherwise wants to create one or more commits in this marketplace repo. Prefer this skill over a plain `git commit` because it groups related files, derives scopes, proposes semver bumps for both the marketplace and any affected plugin's `plugin.json`, and uses conventional commit format with reasoning the user can validate.
- ▌
- ▌ Skill Authoring · asermaxActivates when the user wants to create, define, set up, build, or scaffold a new skill; encode expertise or save a process for reuse; define automation for the assistant. Also triggers on requests to author a skill, write a skill, help me make a skill, guide me through skill authoring, how to create a skill, make a skill, build a skill, new skill.
- ▌ Workflow Authoring · asermaxActivates when the user wants to create, define, set up, build, or scaffold a new workflow; encode a multi-step process or save a procedure for reuse; define automation for workflows. Also triggers on requests to author a workflow, write a workflow, help me make a workflow, guide me through workflow authoring, how to create a workflow, make a workflow, build a workflow, new workflow.
- ▌ Review · asermax bundleNEVER INVOKE THIS SKILL DIRECTLY; USE `/annai:review-pr` to review a GitHub pull request, or `/annai:review-local` to review code an agent just produced locally. This file is the shared base that the two leaf skills load — it owns the surface-authoring rules, launch + watch + react loop, schema-validation contract, and cleanup. It is not a standalone entry point.
- ▌
- ▌
- ▌ Zai Glm · asermaxUse the z.ai GLM API client for LLM-powered AI. Use when implementing the LLM brain, serializing game state, parsing responses, or debugging API calls.
- ▌ Wasm Export · asermaxBuild and serve the WebAssembly export. Use when the user asks to export, build, test in browser, or deploy the web version.
- ▌ Godot MCP Pro · asermaxReference for all 169 Godot MCP Pro tools. Use when creating scenes, adding nodes, writing scripts, simulating input, inspecting running games, or any editor interaction through MCP.
- ▌ Isometric Grid · asermaxReference for the isometric grid system. Use when working with grid coordinates, height maps, tile rendering, click detection, pathfinding, or movement range.
- ▌ Gdscript Patterns · asermaxArchitecture patterns for the GDScript codebase. Use when implementing battle systems, state machines, event buses, resources, actions, or turn queues.
- ▌ Log · asermaxWrite something into the project's quest log in a few seconds — a bug, a chunk of work, a half-formed idea — without deciding anything about it. Use when the user says to note this down, add it to the backlog, capture this, or remember this for later, or when another skill turns something up that must not live only in the conversation.
- ▌ Docs · asermaxLoaded by skills and agents that read or write the project's own documentation. Carries how to find the docs folder, what its structure is made of, and the rule that the project's charter wins over anything a skill assumes.
- ▌ Init · asermax bundleLoad mahou:basics first, then mahou:docs. Then read `.mahou/init.md` if present.
- ▌ Wiki · asermax bundleConsult distilled knowledge about technologies, tools, and their gotchas before designing, choosing, or debugging with them. Reads the indexes first and loads only matching entries.
- ▌ Loot · asermaxGet everything worth keeping out of a session before it ends — decided work into the quest log, findings about how something works into a note, and anything learned about how we work into the project's own conventions. Use at the end of any zenku session, or when another skill is about to close or delete something and needs whatever it learned carried out first.
- ▌ Lore · asermaxWrite or update a durable note in the project's vault explaining how one part of the system works, following the project's own writing charter and templates. Use when the user wants something documented, a mechanism written up, a note brought back in line with the code, or when another skill has changed how something works and the explanation has to follow.
- ▌ Raid · asermaxBuild the thing — turn cleared ground into a shape and a set of slices, then land them one per session.
- ▌ Take · asermaxTake one quest and see it through in a single session — claim it, get onto the right branch, read it in full, present the work and settle what its record leaves open, solve it by its kind, and close it out. Use when the user wants to work the next thing on an adventure, or when a dispatcher needs one session's work done against one record.
- ▌ Guide · asermaxEntrypoint to the mahou plugin when unsure which skill fits. Give it your goal in plain words and it identifies the matching skill and activates it with your request as context.
- ▌ Learn · asermax bundleThe author's tool for growing the plugin from real sessions. Without arguments it reconstructs the session, gives a take on where it departed from the existing skills, and drafts what the user picks. With arguments it skips the reconstruction and works the user's ask from the current context. Produces new or iterated skills, agents, wiki entries and local .mahou files.
- ▌ Shape · asermaxFinds the holes in a problem and solution definition and fills them with questions, working a design tree in rounds until nothing is left assumed. Stays at the level of behavior and decisions, never implementation. Use after the user has explored a problem and settled its first decisions, and before any design or plan is written.
- ▌ Spike · asermax bundleAnswer a design question by building the smallest working version of the real thing and running it against reality. Throwaway code that never merges. Use when a question cannot be settled by reading or asking, like "will this work?" or "what shape should this be?", and only running code can answer it. For a UI element a human reacts to, use prototype instead.
- ▌ Codex · asermaxLoad first when working with any zenku skill. Carries the vocabulary, the two rules, how to find the project's vault and conventions, and the habits for writing into it.
- ▌ Solve · asermaxClose a quest out once its answer exists — write the answer on it, set its status, gist it into the adventure's solved index, and clear it from every blocked_by list that named it. Use when a question has just been answered or a slice has just been built, or when another skill has produced the result a quest was waiting on.
- ▌ Basics · asermaxFoundation for every mahou skill. Carries the philosophy and rules the agent follows when running any mahou skill. Load before running any other mahou skill.
- ▌ Design · asermax bundleTurns a settled problem definition into a system design. Works a design tree one area at a time, from data model to flows to rules, with the user settling every leaf. Hands the tree to mahou:write-documentation so the project's docs record it. Stays above endpoints, functions and files. Use after shape, before mahou:program-architecture.
- ▌
- ▌ Parley · asermaxTalk something through with the user relentlessly, round by round, until you reach a shared understanding. Use when the user wants their thinking stress-tested, says to grill or press or challenge them, or when another skill needs a decision settled by the person who owns it.
- ▌ Strike · asermaxEnd an effort and clear it away — close out whatever is still open, carry out anything worth keeping, remove the spike worktree, and delete the effort's records. Use when an adventure has shipped or stopped being worth continuing, when a loose quest has just landed, or when a finished effort was never cleared out of the quest log.
- ▌ Travel · asermaxTravel a journey — work on something whose shape is not clear yet, mapping what stands in the way and clearing it one question per session, without building.
- ▌
- ▌ Patch · asermaxApply a focused change using a compressed delta workflow. Reads project context (specs, designs, decisions), plans inline via plan mode, implements, and reconciles feature documentation in a single session without creating intermediate delta files.
- ▌ Explore · asermaxUser-guided investigation mode. The user provides context to use as the basis and then steers the investigation one question at a time. The agent reads only that context up front and, for each question, dispatches a scout at exactly what the question needs. Use when the user wants to build their own understanding of a problem before defining a change. Not for producing a report, a plan or a scope.
- ▌
- ▌
- ▌ Research · asermaxInvestigate a question against high-trust primary sources and capture the findings in the project's vault. Use when the user wants a topic researched, docs or API facts gathered, reading legwork delegated, or when another skill needs a fact settled before a decision can be made.
- ▌
- ▌
- ▌ Prototype · asermaxLoaded by other skills to show the user a screen element as a working HTML prototype and iterate it with them, round by round, until it matches what they want. Carries how the file is built, how states and interactions are made switchable, how alternatives are offered and how corrections are applied. The loading skill says what the prototype is of and which decisions it stands for.
- ▌ Bump Version · asermaxThis skill should be used when the user asks to "bump AUR version", "update AUR package version", "bump package version", "update PKGBUILD version", "bump to latest version", or mentions version bumping for AUR packages. Handles automatic version detection, checksum updates, and git commit/push to AUR.
- ▌
- ▌
- ▌
- ▌ Land Delta · asermaxPrepare a reconciled delta branch for merging into main. Rebases the delta branch onto main, reconciles code and documentation with changes introduced on main, and validates conflicting areas with reviewer agents.
- ▌
- ▌
- ▌ Human Review · asermaxCollects the user's own annotations on a change, verifies each against the code, and settles every finding with them before anything is edited.
- ▌ Recall Memory · asermax bundleUse when needing to retrieve information from past sessions, conversations, or stored knowledge. Triggers on questions that could benefit from historical context including user preferences, past discussions, workflows, coding patterns, or any query where previous session information would be helpful. Activates broadly for retrieval queries.
- ▌ Unslop · asermaxCut AI tells from prose meant to be read as a document. Use when writing or editing documentation, READMEs, design notes, wiki entries, specs, PR descriptions or similar long-form text, and when another skill asks for a writing pass. Do not apply to code, chat replies or short answers.
- ▌
- ▌
- ▌
- ▌ Agentic Review · asermaxRefines the code in a change before a human reads it. Runs five facet reviewers per repository, fixes what they find inside the change's own scope, and repeats for up to three rounds.
- ▌ Commit Changes · asermaxCommits the changes in the repository as conventional commits, grouping related files and confirming the grouping with the user before anything is committed.
- ▌ Sync Upstream · asermaxSync this plugin marketplace's skills, commands, and context from their upstream source repositories (superpowers, quint-code/haft, agentic-evolve, agent-browser, dmmulroy-skills, plannotator, cursor-plugins). Use this skill whenever the user asks to "sync upstream", "pull upstream", "refresh skills from upstream", "update plugins from their source repos", or mentions wanting to pick up changes from `~/workspace/random/superpowers`, `~/workspace/random/quint-code`, `~/workspace/random/agentic-evolve`, `~/workspace/random/agent-browser`, `~/workspace/random/dmmulroy-skills`, `~/workspace/random/plannotator`, or `~/workspace/random/cursor-plugins`. Trigger even when the user uses paraphrases like "let's see what's new upstream" or "pull the latest into the marketplace".
- ▌ Delta Details · asermax bundleShow comprehensive details for a specific delta or answer a question about it
- ▌
- ▌
- ▌ Research Docs · asermaxUse BEFORE designing, implementing, planning, or configuring ANY feature involving libraries, frameworks, or complex APIs - even before reading existing code. Fetches current documentation to ensure correct usage. Triggers on third-party libraries (such as react-query, FastAPI, Django, pytest), complex standard library modules (such as subprocess, streams, pathlib, logging), and "how to" questions about library usage. Do NOT use for trivial built-ins (such as dict.get, Array.map) or pure algorithms. Load this skill first to receive guidance on finding current documentation when working on deltas, patches, or answering library-related questions.
- ▌
- ▌ Create Aur Package · asermax bundleThis skill should be used when the user asks to "create an AUR package", "make a new AUR package", "scaffold AUR package", "create PKGBUILD", "package for AUR", or mentions AUR package creation with a specific source type (npm, rust, go, git, binary, appimage). Provides comprehensive guidance for creating Arch User Repository packages with proper structure, checksums, and git setup.
- ▌
- ▌
- ▌ Framework Core · asermax bundleLoad when working with any katachi framework command. Provides workflow principles, status tracking conventions, and decision guidance. This skill establishes the collaborative context for all framework operations.
- ▌
- ▌
- ▌
- ▌
- ▌ Code Blast Radius · asermaxTraces what an already-written change reaches. Fans out a tracer per changed element and reports only the places where behavior changes for someone. Use after code is written, before it is reviewed or merged.
- ▌ Retrofit Project · asermaxFull project retrofit - discover modules, create specs, designs, decisions, and vision from existing code. Use when initializing the katachi framework on an existing project with code, or when the user wants to retrofit documentation for the entire project at once.
- ▌ Working On Delta · asermax bundleLoad when executing spec/design/plan/implement commands for a specific delta. Provides templates, agent dispatch patterns, and workflow orchestration for per-delta work.
- ▌ Hunk Review · asermaxInteracts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files and hunks, reloads session contents, and adds inline review comments. Use when the user has a Hunk session running or wants to review diffs interactively.
- ▌
- ▌
- ▌ Retrofit Existing · asermaxLoad when retrofitting framework documentation to existing code. Supports creating specs and decisions from implementations, enabling gradual framework adoption for existing projects.
- ▌
- ▌ Write Documentation · asermaxWrite or update a note in the project's docs folder explaining how one part of the system works, following the project's own charter and templates. Use when the user wants something documented, a mechanism written up, a note brought back in line with the code, or when mahou:design hands over a settled tree to record.
- ▌ Agent Browser · asermaxBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers, or rendering a live, user-steerable browser in a herdr pane. Prefer agent-browser over any built-in browser automation or web tools.
- ▌ Show Markdown · asermax bundleUse when you need to display a considerable amount of markdown content, or the user asks to display markdown in a browser, preview markdown files, or render markdown with styling. Trigger on requests like "show this markdown", "preview markdown", "display markdown in browser", "open markdown in browser", or any task requiring visual markdown rendering.
- ▌ Program Architecture · asermax bundleTurns a settled design into the architecture of the program that implements it, working a design tree from how the code is distributed, to what the entrypoint does in order, to the contract of each part, with the user settling every leaf. Stays above function signatures, file lists and tests. Use after design, before code.