mia-cx
- 33 skills
- 0 followers
- 9 hours ago last updated
- ▌ Refine · mia-cxUse when the user asks to create, edit, change, refine, slim, or audit an agent-consumed document, like a skill, a memory/rules file, or a plan.
- ▌ Babysit · mia-cx bundleUse when the user asks to babysit a pull request: watch it for review comments from bots and human reviewers, fix what is real, resolve the threads, and keep watching until it is green and mergeable. A request for a fresh review pass or a review loop is review-relay, not babysitting.
- ▌ Pr File · mia-cxUse when the user asks to file a pull request or put the current branch up for review.
- ▌ UI A11Y · mia-cxUse when the user asks to make an interface accessible, add keyboard navigation, fix focus handling, label controls for screen readers, meet contrast or touch-target rules, or support reduced motion, and when building any custom control. Stage 4 of ui-design.
- ▌ UI Copy · mia-cxUse when the user asks to write or fix text the interface shows, such as labels, button names, headings, error messages, empty states, confirmations, placeholders, tooltips, or marketing page copy. Stage 3 of ui-design.
- ▌ Momentum · mia-cxShape output for ADHD readers: lower the cost of starting and keep work visibly moving with a small first action, numbered steps, visible wins. Always on: load at session start and after every compaction, keep in context all session, and apply to every response; the only exception is an explicit ask otherwise.
- ▌ Pr Merge · mia-cxUse when the user asks to merge or land a pull request, or says "ship it" for an already-reviewed PR.
- ▌ Say Less · mia-cx bundleSay what you mean exactly once; stop when the request is satisfied. Always on: load at session start and after every compaction, keep in context all session, and apply to every response; the only exception is an explicit ask otherwise.
- ▌ Say More · mia-cx bundleWithhold reasoning by default; expand only when the user says "say more" or asks for an explanation. Always on: load at session start and after every compaction, keep in context all session, and apply to every response; the only exception is an explicit ask otherwise.
- ▌ UI Style · mia-cx bundleUse when the user asks to choose or change typography, color, palette, shape, spacing, depth, icons, or design tokens; add or fix dark mode, themes, or contrast; extract a design system from a site; or write DESIGN.md. Stage 2 of ui-design.
- ▌ UI Design · mia-cx bundleUse when the user asks to design, build, review, or refine product UI or marketing pages, or to fix generic interfaces and poor usability. Routes through the ui-layout, ui-style, ui-copy, ui-a11y, expressive-web, and ui-review stages.
- ▌ UI Layout · mia-cxUse when the user asks to lay out a screen or page, place navigation, arrange or group content, choose density, set breakpoints or make a page responsive, or fix content that shifts or jumps between states. Stage 1 of ui-design.
- ▌ UI Review · mia-cx bundleUse when the user asks to review, audit, or QA a screen or page, check how it looks at desktop or phone width, verify a UI flow works end to end, or says the interface looks generic, off, or unprofessional. Stage 6 of ui-design.
- ▌
- ▌ Create Prd · mia-cxUse when the user wants to write a PRD or plan anything bigger than a single feature or slice — multi-feature efforts, new systems, epics, large refactors.
- ▌ Gh Comment · mia-cxUse when posting, editing, or replying to a comment on a GitHub pull request (a conversation comment, an inline comment on a diff line, or a reply in a review thread), including when another skill needs to publish results to a PR.
- ▌ Next Slice · mia-cxAdvance to the next PRD slice after a merge: clean up the finished worktree and branch, fast-forward main, pick the next unblocked sub-issue of the PRD, set up a fresh worktree, and hand off to address-issue. Use when the user says "next slice", "move on", "advance", or wants to start the next issue after a merge.
- ▌
- ▌
- ▌ Talk Normal · mia-cx bundleShape every piece of output: chat responses, PR descriptions, docs, commit messages, GitHub comments, prose, copy. Always on: load at session start and after every compaction, keep in context all session, and apply to every response; the only exception is an explicit ask otherwise.
- ▌ Upload File · mia-cx bundleUpload a local file, screenshot, or piped output to the i.mia.cx R2 bucket and get back a public URL. Use when the user asks to upload, host, or share a file, wants a link to an image, screenshot, log, diff, or report, or when a result is easier to hand over as a URL than as inline text. Also covers listing and deleting previously uploaded objects, and configuring ShareX or ishare clients.
- ▌ Codex Review · mia-cxGet an independent code review from the Codex CLI (gpt-5.6-sol) — uncommitted changes, a branch diff, a commit, or a specific implementation.
- ▌
- ▌ Review Relay · mia-cx bundleUse when the user asks for a review relay or review loop, for repeated or multi-provider review passes on a pull request, for a PR to be reviewed until it is clean or merge-ready, or to address review comments and resolve review discussions on a PR. A request for one review pass over a diff is not a relay.
- ▌
- ▌ Prd To Issues · mia-cxUse when the user asks to break down a PRD into issues or create implementation tickets. Also use when writing a plan or roadmap based on a PRD to keep things traceable.
- ▌ Expressive Web · mia-cxUse when the user asks for a scroll-driven, spatial, animated, procedural, or WebGPU experience, a hero or landing page that feels alive, or asks to make a marketing page use the web as a medium. Micro-interactions belong to transitions-dev. Stage 5 of ui-design.
- ▌ Codex Subagents · mia-cxUse when dispatching subagent work to GPT models (gpt-5.6-sol, gpt-5.5) via the Codex CLI, including inside Workflows.
- ▌ Doc Coauthoring · mia-cxUse when the user wants to write or co-author a doc — a proposal, technical spec, decision doc, or RFC.
- ▌ Transitions Dev · mia-cx bundleProduction-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, error state shakes, search/input clear, skeleton loaders, shimmer text, sliding tabs, tooltips, staggered text reveals, card hover tilt, plus-to-menu morph, accordions, toasts, like buttons, learn-more hovers, checkbox checks, spinning counters, or toggles. Triggers on "add a transition", "animate the dropdown", "make the modal open smoothly", "swap icon", "page slide", "stagger animation", "open / close transition", "make it animate", "fade between", "success animation", "form error", "shake on invalid", "hover lift", "avatar stack hover", "clear the search", "skeleton loader", "loading shimmer", "shimmer text", "sliding tabs", "segmented control", "tooltip", "reveal text", "tilt card", "3D hover tilt", "cursor glare", "plus to menu", "FAB morph", "accordion", "collapsible", "exp
- ▌ Audit Dependencies · mia-cxUse when the user asks to audit, check, or upgrade dependencies, or mentions vulnerabilities, outdated packages, or dependency bloat.
- ▌ Codex Computer Use · mia-cxUse when the user asks to test a flow, verify UI behavior, inspect a running app, or capture screenshots.
- ▌ Git Commit And Push · mia-cxSplits uncommitted changes into a small set of logical, single-concern git commits, then executes the commits and pushes to remote. Use when the user wants to commit and push, organize changes into logical commits, split a large change into multiple commits, or create a series of conventional commits from the current working tree.