Productivity

wei18 Skill

Testable seam design via protocol injection, SwiftUI environment, and task-local overrides; Swift 6 Sendable rules for dependencies; mentions pointfreeco/swift-dependencies and Factory as library options. Invoke when designing a new service seam, asking "how do I inject CloudKit/network/clock", setting up a composition root, or making code testable.

wei18 Skill

Read a Claude Code session JSONL log and produce a clean timeline-style meeting log at `meetings/{YYYY-MM-DD}_{topic}.md`. Invoke when the user asks "turn this session into a meeting log", "archive today's discussion", "extract a meeting record from jsonl", or when wrapping up a working session before context window rolls.

wei18 Skill

Checklist of known SwiftUI interaction bugs that slipped past pure-code review (tap-target shrink, sidebar inert Labels, sizeClass on Mac, .task re-fire, theme tint propagation, NSHostingView env). Use when reviewing any SwiftUI View file or a PR that adds Button / NavigationLink / TabView / Form / NavigationSplitView.

wei18 Skill

Read accumulated meeting logs and session JSONL files, extract collaboration patterns that have repeated ≥ 3 times, and append them to `docs/methodology.md` §Patterns. Each entry captures trigger / action / outcome / next-time adjustment. Invoke when the user asks "update methodology", "extract patterns from this session", "consolidate recurring collaboration patterns", or after every 5+ meeting logs accumulate.

zfinix Skill

Using git without hanging, clobbering, or over-committing. Use before any git command that changes state (commit, push, checkout, rebase, reset) and when inspecting repo history or status.

zfinix Skill

Turning a workflow this session learned into a reusable skill. Use when the user says save this as a skill or make a skill for this, when they repeat the same correction or instructions a second time, or when a multi-step procedure just worked and will clearly recur.

zfinix Skill

Isolating work in a linked worktree so another branch can be built, tested, or fixed without touching the current checkout. Use when the working tree is dirty or busy and the task needs a different branch checked out.

zfinix Skill

Renaming, moving, and restructuring code without breaking behavior. Use when the task is a rename, a file move, an extract, or any restructuring the user expects to be behavior-neutral.

rubyeyedreaper Bundle

Use when deciding whether something that has outlived its purpose may go — a spent plan, a retired workflow, inactive project material, a cache, a completed session, a branch. Also on "can this be deleted", "is this still needed", "clean this up".

rubyeyedreaper Skill

Use the moment something turns out to behave differently from how it reads — a sharp edge, a gotcha, an exception, a footgun, a caveat, a surprising default, a command that succeeds while doing the wrong thing, a tool whose absence looks like a pass. Also use on "watch out for", "careful, X does Y", "that's a trap", "note that this only works when", "we should write that down", "make sure nobody hits this again", and on any oops or mistake moment where the workflow must pause, record the hazard with the condition under which it recurs, and land the safeguard before continuing. Fires on the hazard itself, whether or not anybody asked for it to be written down.

rubyeyedreaper Bundle

Use when a new task arrives mid-run and displaces work already in flight — an interruption, a pivot, being sidetracked, parking what you were doing, or coming back to it afterwards. Also on "before I forget", "hold that thought", "where were we".

rubyeyedreaper Bundle

Use when a reusable workflow chain is being defined, validated, versioned, superseded or retired — adding a chain, changing one, running one, or finding a chain nobody owns and nobody can say is current.

rubyeyedreaper Bundle

Use when choosing between options or prioritizing — "decide", "choose between", "which should I pick", "compare options", "trade-off", "which library/framework/database/vendor", "build vs buy", "best option for", "prioritize", "rank these", "RICE/WSJF". A quantitative weighted-decision engine: scores options against weighted criteria with multiple methods (weighted-sum, Pugh, TOPSIS/AHP, RICE/WSJF/ICE/Kano), runs sensitivity analysis, flags when methods disagree, applies hard-constraint vetoes, aggregates multiple scorers, and records a numbered DEC decision. Fire this for ANY non-trivial multi-option choice or prioritization, even a mid-task internal fork — the math is deterministic and the decision is recorded. Not for qualitative-only trade-off framing (use decision-mapping) or stochastic rollout search (use recursive-decision-ledger).

kehwar Bundle

Expert guidance for producing correct DTW (Data Transfer Workbench) import files for SAP Business One. Use when recommending templates for bulk import operations, generating TSV files from the bundled templates, understanding multi-table object requirements, identifying mandatory vs optional columns, adding custom fields, or choosing between DTW and Service Layer for a given task.

kehwar Skill

Turn the current conversation context into a Beads issue or edit an existing one. Use when user wants to create or update an issue (bug|feature|task|epic).

kehwar Bundle

Expert knowledge of Typst markup language syntax, scripting, and styling. Use when writing or editing .typ files, creating Typst documents, templates, or packages, setting up page layout, using math mode, applying set/show rules, writing Typst scripting (variables, functions, loops), or any task involving Typst typesetting.

kehwar Bundle

Expert guidance for writing DocType controller Python tests in custom Frappe apps. Covers the mandatory workflow (read controller, read schema, write test, run), FrappeTestCase base class, make_ helper pattern, and 6 test categories (validation, computed fields, lifecycle side-effects, whitelisted methods, link validation, child table logic). Use when writing test_{doctype}.py files, testing controller hooks, testing whitelisted methods, or debugging failing doctype tests.

kehwar Bundle

Detects and fixes deviations from the prescribed repo workflow configuration — AGENTS.md, docs layout, and Beads issue tracking.

kehwar Skill

Automated workflow for restoring the latest Frappe/ERPNext backup with proper database configuration, migrations, and password reset. Use when users request "restore latest backup", "restore backup", or need to recover from a backup file.

green-pt Skill

Decide when to delegate to Honey's read-only subagents (hive-scout, hive-reviewer) instead of working inline, so the expensive tokens — large file reads and review passes injected back into the orchestrator's context — come back compressed (Honey Lever 3). Use when a task is search-heavy or review-heavy, spans many files, or you want to keep the orchestrator's context small. Not for trivial one-file work.

green-pt Skill

Rewrite a memory or context file (CLAUDE.md, AGENTS.md, a todo or notes file) into Honey-terse form so it costs fewer input tokens every session, without losing meaning. Backs up the original first. Use when asked to shrink or compress context files, trim CLAUDE.md, or cut per-session input cost. Prose only — never code, config, or data.

ramboz Bundle

Orient a spec-driven jig/servo/shaper repository with a read-only, project-wide briefing: start from the `workflow.py orient` headline, then survey open pull requests and unmerged work, Proposed ADRs, DEFERRED triggers, refinement items, release plans, the inbox, and the bug board; render one readable headline, titled sections, one recommendation, and an owning-skill handoff. Use when the user invokes `/jig:orient` or explicitly asks for a whole-project session pickup, a return-after-time-away briefing, the overall project status or big picture, or what to pick up next across the repository. Do not use for mid-implementation questions about the current slice such as "what's next?" or "what's blocking this test?"; those continue current work rather than requesting a project-wide rescan. Also do not use for non-code projects; use `studio:project-desk`. Never write files or lifecycle state; scheduled jobs and dashboards may capture stdout.

ramboz Bundle

Drive the teeth-gated lifecycle for reported defects: diagnose root cause, prove it, and prevent regression through REPORTED → DIAGNOSING → ROOT_CAUSED → FIXING → REVIEWED → DONE, with VERIFIED, ESCALATED, and RESOLVED_ON_MAIN paths where needed. Auto-fires on fix this bug, debug this, root-cause this, this regressed, this broke again, why is this failing, diagnose before fixing, or investigate this failure. Two modes: `diagnose` stops at ROOT_CAUSED; `diagnose_and_fix` runs through DONE. Uses a durable bug record, multiple hypotheses, a fresh-main recheck, and a witnessed red→green test. Do not use for spec-shaped work (use `spec-workflow`) — including a pure visual design-fidelity gap against an agreed mockup, which is spec-shaped, not a bug (see "Design-fidelity triage" below) — or trivial one-liners (use `tdd-loop`).

ramboz Bundle

Team baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to any other installed skill whose description identifies it as handling architecture review, design review, RFC review, or technical-design review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: PR/diff review (use `/jig:pr-review` or a richer user-installed PR-review skill instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead); ADR authorship or scaffolding (use `/jig:adr-workflow` — this skill *reviews* an ADR draft; it does not create one).

ramboz Bundle

Scaffold, accept, index, and link Architectural Decision Records (ADRs). Use when the user says "write an ADR", "record this decision", "resolve [deferred item] with an ADR", "supersede ADR-NNNN", or otherwise wants to capture a hard-to-reverse decision in `docs/decisions/`. Also use when a refinement-todo entry needs to be marked RESOLVED with a link back to the ADR. Do NOT use for ad-hoc design discussion that hasn't crystallized into a decision yet — wait until the choice is firm.

ramboz Bundle

Initialize an AI-native development workspace with spec-driven workflow infrastructure. Use when starting a new project, setting up Claude Code on a codebase for the first time, or when the user says scaffold, initialize, set up AI workflow, onboard this repo, or similar. Do not use for adding an individual skill or config to an already- scaffolded project — that is handled by the relevant tier skill directly.

ramboz Bundle

Drive the spec-driven lifecycle for any non-trivial work item: SPIDR-split a new spec into vertical slices, transition state markers (DRAFT → READY_FOR_REVIEW → READY_FOR_IMPLEMENTATION → IN_PROGRESS → REVIEWED → RECONCILED → DONE; also DEFERRED for parked slices with a stated resolution trigger), enforce the reconciliation checklist before commit, and surface stale specs/ADRs whose `last_verified` date has aged past dependency changes. Use when starting non-trivial new work, creating a spec, transitioning a slice's state, parking a slice as DEFERRED, reconciling a reviewed slice, or auditing doc freshness. Do not use for quick one-off fixes that don't need a spec, or for bug-shaped work where `jig:bug-fix` is the better fit.

swm8023 Bundle

Implement approved product, code, or bug-fix work end to end after the user has approved a spec, confirmed scope's in-conversation implementation contract, or approved debug's evidence-backed fix contract. Create new persisted plans only for spec-backed work, then execute, verify, and complete the configured Git workflow. Do not use while requirements, root cause, or approval are unresolved.

swm8023 Skill

执行会持久化仓库修改的 Git 工作流。prepare 时读取 docs/user/git-preferences.md 并建立本次 Git 上下文，checkpoint 和 finalize 继承该上下文，管理 branch/worktree、同步、commit、push、merge 和 cleanup；配置缺失或行为不明确时初始化或逐项询问。

24601 Bundle

Dispatch work to gastown polecats. Takes a design doc, plan, or task list, extracts tasks, creates beads, dispatches a convoy, and monitors execution. The handoff FROM gstack TO gastown — seamless parallel build phase. Use when: "dispatch this", "build this in parallel", "send to polecats", "run this with gastown", "dispatch to convoy", "/dispatch". (gstack)

itechdev-mx Skill

Spec-Driven Development workflow for AriaCore. Trigger: When user requests SDD or multi-phase implementation planning.

itechdev-mx Skill

Capture a workflow you just ran ad-hoc and turn it into a draft SKILL.md file under skills/_drafts/. Lowers the barrier from "I did this once" to "we have a skill for this" so repeated patterns graduate into the catalog instead of dying as tribal knowledge. Inspired by oh-my-claudecode/skillify.

itechdev-mx Skill

PR creation workflow for AriaCore following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

itechdev-mx Skill

Issue creation workflow for AriaCore following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.

mr-fang-vlsi Bundle

Standardize workflow classification and skill selection before execution. Use when a task requires explicit known-vs-unknown workflow judgment, temporary workflow creation, workflow-local skill shortlist construction, or a decision on whether a new skill should be created.

mr-fang-vlsi Bundle

Retrieve scoped knowledge-base context and tool-registry reuse evidence for an EDA task, then emit compact context artifacts that downstream skills can consume directly.