All authors
Claude Skills by sushi-killer
github.com/sushi-killer14 skills0 installs4 views
- Author And Verify ExtensionBuilds a new sushiAI extension end to end: designs the manifest, validates it with validateExtensionManifest, builds, and proves it loads in a real Electron smoke run against a throwaway extensions directory. Use when asked to add, scaffold or build an extension, plugin or surface.Votes: 0GitHub stars: 2
- AutoreviewFresh-context independent code review of a sushiAI diff before it is committed: correctness, root cause over symptom, callers and sibling paths, security boundary, test value. Use after implementation and deslop, before landing any nontrivial change, or when the owner asks for a review.Votes: 0GitHub stars: 2
- Cut ReleasePrepares a sushiAI release: runs scripts/release.mjs to compute the bump from merged history, folds docs/releases/unreleased/ fragments into the release note, opens the release PR. Use when asked to cut, prepare or ship a release or bump the version; never hand-edit package.json's version.Votes: 0GitHub stars: 2
- DeslopDiff-scoped AI-slop cleanup for sushiAI: strip narration comments, imagined-state guards, type laundering, one-use helpers and style drift from the current diff without changing behaviour. Use right before autoreview on any agent-written change.Votes: 0GitHub stars: 2
- Extension Manifest ChangeChanges what an extension manifest may contain: validator in electron/extensions/manifest.cjs, then the mirrored src/extensions/types.ts, then the probe fixture and contract-coverage tests, in that order. Use for any request to add, rename, narrow or remove a manifest field, or make the validator accept or reject something.Votes: 0GitHub stars: 2
- Figma To CodeTurn a Figma concept frame into exact code metrics and check the built screen against it: export a node dump to a snapshot, generate token-only CSS, measure the running app and compare, with a pass/fail table. Use whenever a screen must match a Figma frame 1:1, when the owner says a screen must look like the concept, or before design-critic reviews a converted screen.Votes: 0GitHub stars: 2
- Ship PrOpens a sushiAI pull request the way the release pipeline expects: <type>/<slug> branch paired with a conventional-commit title, a docs/releases/unreleased/ fragment when user-visible, npm run ci green first. Use whenever a change is ready to leave the working branch ("ship this", "open a PR", "push this up"). Never merges.Votes: 0GitHub stars: 2
- Sushiai TaskCarry an owner's sushiAI task to a verified local commit without supervision: scope it, delegate implementer, functional-qa, reviewer and design-critic lanes, loop on findings, and report back with only the questions the owner must answer. Use for any change bigger than one obvious edit; not for read-only questions or a one-line fix.Votes: 0GitHub stars: 2
- Sushiai TestingChoose proportional proof for a sushiAI change - which npm scripts, targeted node --test suites, desktop smoke or manual steps a diff needs - and read the results honestly. Use before claiming any change works, when a check fails, or when briefing functional-qa.Votes: 0GitHub stars: 2
- Sushiai UiThe sushiAI design code: tokens, type scale, the component catalogue and the recipes for new windows, taken from the shipped screens. Use before writing TSX or CSS for any change that adds or alters a screen, dialog, window, panel, menu, popover, list row, settings section or component in src/, and whenever Figma is unavailable. It replaces outside design skills for this repo.Votes: 0GitHub stars: 2
- Ui EvidenceProduce measured, looked-at evidence of the built sushiAI UI: drive the real Electron app with Playwright against a throwaway profile, measure geometry, capture screenshots and read them. Use whenever a change touches what a screen shows, including a second SSH host, before claiming it looks right.Votes: 0GitHub stars: 2
- Sushiai OrchestratorDrive the sushiAI orchestrator from any agent session in any repository - create, plan, route, watch and answer tasks that run in isolated worktrees, group them into one feature branch, park them in the backlog. Use when the owner asks to "make it a task", "queue it", "run this on codex/claude", "put it in the backlog", "what are my tasks", or to hand work to the orchestrator instead of editing files yourself.Votes: 0GitHub stars: 2
- ExtensionsShow the owner a document you wrote - a plan, research, report, deck or diagram - in a sushiAI Preview half of your own pane. Works for Claude Code and Codex, in any project and on any host. Use when the owner asks to show, open or "make it a doc", a presentation, a deck or a diagram, and after you write a plan or report the owner should read. Not for scratch notes.Votes: 0GitHub stars: 2
- ExtensionsBuild a sushiAI routine - a scheduled background agent run - from one sentence of the owner. Use when the owner asks to create, change or repair a routine, or says "every morning do X" or "run this on a schedule". Works for Claude Code and Codex. Not for one-off tasks the owner wants done now.Votes: 0GitHub stars: 2