All authors
Claude Skills by mimukit
github.com/mimukit38 skills0 installs167 views
- How ToAdding a skill means creating one directory — but shipping one means updating up to six other files. Lint now checks most of them, but not all. Prefer to have this driven for you? `skillkit` runs the whole path, from naming through testing. This page is what it does by hand.Votes: 0GitHub stars: 2
- AfkkitRun a groomed `ready` GitHub issue through the whole build span unattended, covering worktree, implement, commit, QA plan, acceptance check, fix, and open PR, so one issue reaches a reviewable PR with no human at the keyboard. Use when the user says "run issue #N unattended" or "work the ready issues while I'm away". It starts from a groomed issue; planning and grooming stay attended.Votes: 0GitHub stars: 2
- CommitkitCommit this session's changes with Conventional Commits messages derived from the actual diff, then push them to origin. Use when the user asks to commit changes, says "commit this", runs "/commitkit", runs "/commitkit all" to commit every change in the tree, or wants a well-formed commit message written for staged work, even if they don't spell out the format. Also use when the user says "commit these, we'll review later" or "I reviewed the X plan", to stamp a doc for review or mark it revie...Votes: 0GitHub stars: 2
- DebugkitChase a symptom to its true cause: reproduce it, shrink it, write falsifiable hypotheses, and prove the cause by toggling the symptom on and off, then hand over a failing reproduction instead of a fix. Use when the user says "debug this", "why is this failing", "find the root cause", "what's causing this bug", "this test is flaky", "it broke after the upgrade", "it worked yesterday", "this got slower", or "/debugkit".Votes: 0GitHub stars: 2
- DesignkitDerive a project's design system from the UI it already ships and keep it true as the code moves, producing a spec-compliant DESIGN.md at the repo root, validated by the official linter. Use when the user says "write a DESIGN.md", "document our design system", "extract our design tokens", "our design system is out of date", "audit our design tokens", "what colors does this project actually use", "sync DESIGN.md to our Tailwind theme", or "/designkit".Votes: 0GitHub stars: 2
- DomainkitMaintain a project's domain model as a consented record of settled understanding: the CONTEXT.md overview and glossary of the ubiquitous language, and docs/adr/ decision records. Use when a domain term needs pinning down, when a hard-to-reverse trade-off decision gets settled, when the user says "update the glossary" or "write an ADR", or when another skill needs the domain model kept current; when the user says "set up CONTEXT.md" or "write the project overview"; or when the user asks "is CO...Votes: 0GitHub stars: 2
- GitkitThe shared git layer other skills borrow: the worktree path, name, and lifecycle, a worktree's declared setup and teardown, the base branch, rebase versus merge, branch sync, hotfix branches, merged-branch cleanup, lost-work recovery, and stacked branches. Use when the user says "make me a worktree for #42", "where's the worktree for this branch", "tear down this worktree", "set up this worktree", "make this worktree's dev database", "what's the base branch here", "should I rebase or merge", ...Votes: 0GitHub stars: 2
- GrillkitGrill the user relentlessly about any idea, plan, or design, a round of unblocked decisions at a time, each with a recommended answer, until you both share the same picture. Use when the user wants to stress-test or pressure-test an idea, says "grill me", "grill this plan", "poke holes in this", "interrogate my design", or otherwise asks to interrogate a concept before committing to it, whether a rough idea, a plan file, an architecture, or a PR.Votes: 0GitHub stars: 2
- HandoffkitCompact the current conversation into a handoff document another agent or session can pick up cold: goal, state, next steps, key artifacts by reference, and constraints. Use when you deliberately run "/handoffkit" (optionally with a focus argument) to hand off work, write a handoff doc, or summarize the session for the next agent.Votes: 0GitHub stars: 2
- HumankitStrip the tells of AI-generated writing from prose so it reads like a person wrote it. Use when asked to humanize text, remove AI-isms, make writing sound less like ChatGPT, edit out "AI slop," or review a draft for robotic phrasing without rewriting it. Covers em-dash overuse, puffery, filler, and the AI vocabulary words.Votes: 0GitHub stars: 2
- IdeakitThink an idea through across many sessions, with one ideas repo holding a folder per idea, a jotpad for the thoughts that have none, and one idea open at a time. Use when the user says "jot this down", "promote that jot", "capture this idea", "let's think about the <X> idea", "where do my ideas stand", "research <X> for this idea", "is the <X> idea worth building", "I'm dropping the <X> idea", or runs "/ideakit".Votes: 0GitHub stars: 2
- ImplementkitImplement a plan, spec, or issue into working code in straight-through, tests-after, or TDD mode, then run the repo's test and build gate before declaring done. Use when the user says "implement this plan", "implement #42", "do this TDD", "build it, then add tests", "apply these review findings", or "make this failing test pass". It runs attended; the unattended issue-to-PR span is afkkit's.Votes: 0GitHub stars: 2
- IssuekitOwn the GitHub issue lifecycle in five modes: file issues from a plan, start a workable issue in its own worktree, close one once its PR merges, sync PR↔issue links and dependents after merge, and triage the tracker for label and title gaps and for done, duplicate, or obsolete issues. Use when the user says "create issues from this plan", "file an issue", "start issue #42", "close #42", "sync my issues", "triage the backlog", "set the priority on #42", "#42 is grilled, mark it ready", "fix th...Votes: 0GitHub stars: 2
- MergekitTake an open GitHub PR and set it up for review on your machine (worktree, project running, review pack), then merge it once you say so, or service review feedback on a PR you authored. Use when you say "pull PR #34 down so I can test it", "merge PR #34", "address the review comments on my PR", or "my PR is red, fix the CI".Votes: 0GitHub stars: 2
- MotionkitChoose the easing, duration, spring, and properties that make web UI motion feel right, then build it, review it in a change or across a codebase, or find why it drops frames. Use when the user says "animate this dropdown", "this animation feels off", "audit the animations in this app", "this transition is janky", or asks "what's it called when an element slides in and settles".Votes: 0GitHub stars: 2
- NamekitName a project to a naming convention you already use, then prove the name is free on the domain, npm, and GitHub before you commit to it. Use when the user says "name this project", "what should I call this", "give me project name ideas", "come up with a name for X", "is <name> taken", "check if this name is available", or "/namekit".Votes: 0GitHub stars: 2
- OrcakitKeep the Orca desktop app's workspace list honest about the git worktrees your workflow actually creates: link each one to its issue, keep its status current, and clean out the ones whose work already merged. Use when the user says "orcakit", "clean up my orca workspaces", "my Orca sidebar is full of finished work", "which workspaces are stale", "link my worktrees to their issues", "remove the workspaces for merged issues", or "where should Orca put new worktrees".Votes: 0GitHub stars: 2
- PaseokitPush the git worktrees your workflow actually creates into Paseo's workspace registry, because Paseo discovers nothing on its own. Use when the user says "paseokit", "sync my worktrees to paseo", "sync all my projects to paseo", "my paseo sidebar is missing worktrees", "paseo doesn't show my worktree", or "where should paseo put new worktrees". It also reaps the finished work and the dead rows: "clean up the worktrees whose PRs merged", "clean up my paseo workspaces", "my paseo sidebar is ful...Votes: 0GitHub stars: 2
- PlankitTurn a rough feature or change into a structured plan document (docs/plans/NNNN-plan-<slug>-YYYY-MM-DD.md) before any code: brainstorm the approach, settle the big decisions, and write a plan that can be hardened and turned into issues. Use when the user says "plan this feature" or "brainstorm a plan/PRD/spec", the front of the plan → grill → file workflow.Votes: 0GitHub stars: 2
- PrkitDraft and open a GitHub pull request from your branch, with title, summary, and test plan written from the actual commits and diff, then created with the gh CLI, embedding verifykit proof artifacts inline when a bundle is present. Use when the user asks to open a PR, says "create a pull request", "raise a PR", "submit this for review", or "gh pr create", even if they don't spell out the title or body.Votes: 0GitHub stars: 2
- PromptkitSharpen the prompt before you send it, whether the one-shot instruction you're about to hand a coding agent or the system prompt your application ships. Use when the user says "optimize this prompt", "what's wrong with this prompt", "write or rewrite the system prompt my app ships", or "/promptkit".Votes: 0GitHub stars: 2
- PrototypekitBuild throwaway code that answers a question, whether an interactive state model you can drive, a script that measures one thing, or competing live UI variants to switch between in the app, then fold the answer into the decision and delete the code. Use when the user says "prototype this", "spike this", "does this state model hold up", "is this library fast enough", or "try three live versions in the app". Not a demo generator and never production code.Votes: 0GitHub stars: 2
- QakitGenerate a QA plan for a feature just implemented, grounded in the actual code changes: the agent runs every check with an observable result, in a headless browser when one is available, and leaves a short manual list of what needs human judgment, saved to docs/qa. Use when a coding session wraps and you want to hand-test the result, or the user says "write a QA plan", "make a manual test plan", "how do I test this", "generate a testing plan for this feature", "try to break this component", o...Votes: 0GitHub stars: 2
- RefactorkitSurvey an existing codebase for the structural change worth making, then rank the candidates, crown one, and write it up as a reviewable proposal. Use when the user says "where should I refactor", "this code is hard to change", or "audit the module boundaries".Votes: 0GitHub stars: 2
- ReleasekitCut a release from the Conventional Commits a repo already writes: derive the semver bump and a changelog from the commit range, bump the manifest, tag it, and publish a GitHub release, all behind a mandatory preview. Use when the user says "cut a release", "tag a version", "release this", "what's the next version", "generate a changelog", "ship v2", or "/releasekit". It never publishes to a package registry and never moves a published tag.Votes: 0GitHub stars: 2
- RepokitConfigure a GitHub repo through gh in four modes: an inferred About description and topics, the workflow labels (issuekit's lifecycle and priority sets plus `ai-review`), a new-repo setup (house settings, baseline files, About, labels), and a docs/ renumbering into creation order. Use when the user says "set the repo description", "add topics", "provision the workflow labels", "set up this new repo", or "renumber the docs".Votes: 0GitHub stars: 2
- ResearchkitResearch the credible options for a technical decision and recommend one (a tool, library, framework, architecture, or service) grounded in primary sources with cited, dated evidence. Use when the user asks "which should I use, A or B", "compare X and Y", "evaluate options for Z", "what's the best tool/library/service for …", "should we use X or Y", "research X before we build", or runs "/researchkit", the decision research that front-runs a plan.Votes: 0GitHub stars: 2
- ReviewkitReview AI-agent-implemented code specifically, in four ordered passes (convention-fit, agent-slop signatures, requirement-completeness, correctness) against the working tree or the branch diff, findings ranked by severity and backed by quoted evidence. Use when the user says "review this code", "review my changes", or "check the agent's work" before commit or PR.Votes: 0GitHub stars: 2
- SeokitAudit a web page, or crawl a whole site, for SEO and AEO gaps (crawlability, on-page, structured data, Core Web Vitals, AI-crawler access, answer extractability), then write a prioritized fix report and a long-term search and AI-visibility plan. Use when the user says "audit the SEO of <url>" (including a localhost URL), "check SEO before I deploy", "crawl my site for SEO issues", "why isn't this page ranking", "is my site ready for AI search or ChatGPT", "check my robots.txt for AI bots", or...Votes: 0GitHub stars: 2
- SkillkitCreate a new AI agent skill from scratch (kit-convention naming, drafting, trigger cases, live testing, publishing), or re-check an existing one after a change. Use when the user says "help me make a skill for X", runs "/skillkit", or says "I changed this skill, check it".Votes: 0GitHub stars: 2
- StatuskitSurvey a project read-only (working tree, issues and their priority, open PRs, unfiled plans, docs awaiting review) into a one-screen dashboard that crowns one finish-first next move routed to the kit that does it, saved by default as a throwaway snapshot under docs/status/. Use when you sit down at a project and ask "what should I do next" or "check project status"; add "no file" to skip the snapshot. It reads and recommends only; the crowned kit does the work.Votes: 0GitHub stars: 2
- TestkitRetrofit an automated test suite onto a working codebase that has none: rank the untested surface, crown a slice, stand up a runner, and write tests that were each watched to fail before they were kept. Use when the user says "this project has no tests", "add test coverage" to code that already runs, or "what should I test first". Tests for code still being built belong to implementkit.Votes: 0GitHub stars: 2
- TutorkitTeach a topic across many sessions, with one learning repo holding a folder per topic, lessons pitched at what you already know, and spaced retrieval that makes it stick. Use when the user says "explain how X works", "teach me X", "quiz me on what's due", "am I ready on X", "where am I with my learning", or runs "/tutorkit".Votes: 0GitHub stars: 2
- UikitBuild production UI that reads as a deliberate choice for this project rather than an LLM default, audit shipped UI for the tells that give it away, or mock up a screen as an image before the build. Use when the user says "build this page", "make this UI not look AI-generated", "audit our UI", "make the frontend look good", "mock up this screen", "show me a few options for this screen", or "/uikit". Reads a project's DESIGN.md when one exists.Votes: 0GitHub stars: 2
- ValidatekitValidate a SaaS or startup idea before you build it, with a few forcing questions, an optional market and competitor scan, an honest verdict graded on the evidence you can actually produce, the narrowest wedge worth testing, and one real-world assignment. Use when the user says "validate my idea", "should I build this", "will anyone pay for this", or runs "/validatekit".Votes: 0GitHub stars: 2
- VerifykitShow a frontend change in a real browser, or prove it for a PR: drive the feature, capture screenshots (plus a short GIF for proof), and publish proof so a pull request can embed it inline; or set up the browser driver and the publish path on a machine. Use when a frontend change is built and you want to see it or want visual evidence it works before opening the PR: "show me what it looks like", "screenshot this", "verify this feature", "record the flow working", "prove the UI change", "/veri...Votes: 0GitHub stars: 2
- WikikitGenerate and maintain a project's reader-facing documentation in-repo (getting-started, how-to guides, architecture overview, runbooks), every command verified against the code, in four modes: init, update, audit, and an opt-in publish that mirrors the set to the GitHub wiki. Use when the user says "write docs for this project", "update the docs", "our docs are stale", or "sync the docs to the GitHub wiki". Not an agent handoff, and not the glossary or ADRs.Votes: 0GitHub stars: 2
- DbkitModel database schemas, write and check migrations so they run safely on a live database, find why a query is slow from its plan, and audit a schema and its migration history, in four modes: design, migrate, tune, and audit. Use when the user says "design the schema for …", "write a migration to …", "is this migration safe", "check this migration", "why is this query slow", "explain this query plan", "add an index for this query", or "audit our database schema".Votes: 0GitHub stars: 2