receptron/mulmoterminal agent skills

Help desk for "MulmoTerminal is broken". An agent skill from receptron/mulmoterminal.

receptron/mulmoterminal

Check what this project's humans have already been asked, and how they answered, before asking them something similar.

receptron/mulmoterminal

Help desk for questions about MulmoTerminal itself — what it can do, how a feature or a part of the screen works, how to set something up, what is new in this version or in the latest one.

receptron/mulmoterminal

Decide which moments MulmoTerminal beeps or pushes for, and what each one plays — soundKinds, sounds and pushKinds in ~/.mulmoterminal/config.json, plus a per-project sound / sounds in…

receptron/mulmoterminal

Build a colour scheme of your own for MulmoTerminal — one that joins Midnight, Nord, Daylight and Solarized in Settings' theme picker and can then be pinned per project.

receptron/mulmoterminal

Answer each question from the named documents only, quoting where the answer is written, or saying plainly that the documents do not say — changing nothing yet.

receptron/mulmoterminal

Review the finished Worker against OWASP Top 10:2025, fix what is exploitable, prove each fix with a test, and report.

receptron/mulmoterminal

Pair every article of the old version with its article in the new one, and say whether each changed, was added or was removed — writing .blueprint/comparison.json and changing no document.

receptron/mulmoterminal

When the person asked, put the glossary's spellings and jargon into the folder's chaff.yaml without losing what it had; then write the glossary up for them.

receptron/mulmoterminal

Collect the terms the documents define, the ways each word is spelled, and the jargon, each quoted where it was found, into .blueprint/glossary.json — changing no document.

receptron/mulmoterminal

Review the finished app against OWASP Top 10:2025, fix what is exploitable, prove each fix with a test, and report.

receptron/mulmoterminal

Polish the next file on the list to the house style without changing what it says, keep the original, and check it.

receptron/mulmoterminal

Measure the named documents with chaff and choose which to polish, within the agreed number — changing nothing yet.

receptron/mulmoterminal

Find what is worth tidying in this repository, measure each candidate's value and risk, and write a plan the person approves — including what to leave alone and why.

receptron/mulmoterminal

Take ONE target from the plan and land it without changing behaviour: guard it on the untouched code, move it verbatim, prove the equivalence by running both, mutation-sweep the tests, pass every…

receptron/mulmoterminal

Read the named documents closely, address every structure problem chaff reports, find contradictions and ambiguities, and quote the text for each finding — changing nothing yet.

receptron/mulmoterminal

Measure the models with chaff, then write the style twice: chaff.yaml for what a machine checks, STYLE.md for what the writer reads — with a reason for every decision.

receptron/mulmoterminal

Collect the texts the person wants as models into .blueprint/sources/ as Markdown, and record where each came from.

receptron/mulmoterminal

Summarize the named documents to the agreed length, one sentence at a time, each backed by quotations, citing every part or leaving it out with a reason — writing .blueprint/summary.json and…

receptron/mulmoterminal

Review the built app against OWASP Top 10:2025 as an attacker would, fix what is exploitable, prove it on the local stack, and write the report.

receptron/mulmoterminal

Extract every dated event, time and amount from the named documents into .blueprint/facts.json, each with a quotation it was read from — deciding nothing yet.

receptron/mulmoterminal

Write the next part of the outline to the house style, check it with chaff, cite what came from the sources, and mark it done.

receptron/mulmoterminal

Measure what chaff reports on the named documents today, as the kind the person chose, and propose the setup — changing nothing yet.

receptron/mulmoterminal

Lay out a Worker with D1 and static Vue assets, with tests that run inside the Workers runtime.

receptron/mulmoterminal

Create the app skeleton: Express API, SQLite through node:sqlite, a Vue screen, and the test harness, following the layout the later checks rely on.

receptron/mulmoterminal

Find the repository's own gates — install, format check, lint, typecheck, build, test — record them, and prove they all pass before anything is touched.

receptron/mulmoterminal

Prove the style bites: write texts that deliberately break the guide and confirm chaff reports them.

receptron/mulmoterminal

Lay out a Vue app on the local Supabase stack, served as static files by wrangler, with tests that run against the local stack.

receptron/mulmoterminal

Set chaff up in the folder: chaff.yaml for the chosen genre, today's findings shelved in .chaff-baseline.json, and, when asked, a GitHub workflow that puts new findings on the pull request's lines.

receptron/mulmoterminal

Propose a fix for each finding and write a corrected copy of each document beside the original, leaving the original untouched.

receptron/mulmoterminal

Turn the interview into a brief — purpose, audience, key points, facts from the sources, open questions — and collect the sources.

receptron/mulmoterminal