Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

mxrsv

@mxrsv source repo

16 published skills

  1. ▌
    Review · mxrsv bundle
    Review a spec or a plan before implementation starts — completeness, ambiguity, feasibility, executable steps, missing dependencies. For reviewing the project itself (code, UX, architecture, deps, docs) use the /review-change, /review-experience, /review-health and /review-release commands instead.
    0 installs
  2. ▌
    Explain · mxrsv
    Explain concepts, bugs, or design decisions in a deliberately chosen teaching style. Use when the user invokes the skill by name, says "explain", or wants to understand *why* (not just a fix). Honors flags `--story` (Journey + Analogy for bugs), `--why` (First principles + Counterfactual for design decisions), and `--diff` (Compare + Layered onion for X vs Y). Auto-picks style if no flag. Output in Vietnamese.
    0 installs
  3. ▌
    Hand Off · mxrsv
    Compact the current conversation into a handoff document for another agent to pick up.
    0 installs
  4. ▌
    Log Wiki · mxrsv
    Capture knowledge vào Tolaria wiki từ mốc lastLoggedAt — cook gợi nhớ (Claude/Codex/Cursor + git), hỏi người kể, soạn entry, xin duyệt rồi ghi qua record-capture.js. Dùng khi người dùng nói "log-wiki", "ghi wiki", "capture wiki", "tổng kết knowledge wiki", hoặc gọi /log-wiki.
    0 installs
  5. ▌
    Planning · mxrsv
    Turn an approved spec (the Linear issue's description) into an implementation plan — a `## Plan` checklist in the issue for small work, sub-issues for work that spans several commits or sessions. Use after "what to build" is clear. Trigger phrases - "plan this", "break into tasks". Not for vague requests - go back to `brainstorm` first.
    0 installs
  6. ▌
    Brainstorm · mxrsv
    Brainstorm
    0 installs
  7. ▌
    Docs Drift · mxrsv
    Đối chiếu tài liệu sống với code thật để tìm chỗ tài liệu mô tả hành vi code không có. Mặc định là scan READ-ONLY, không ghi file nào. Chỉ ghi khi chạy với --apply và sau khi người dùng duyệt diff. Fires ONLY when the user types /docs-drift.
    0 installs
  8. ▌
    Interview Me · mxrsv
    Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
    0 installs
  9. ▌
    Review Change · mxrsv bundle
    Review a change you just implemented — correctness against its callers, test quality, and code-level security — over a git range or the working tree. Run right after finishing a unit of implementation and before committing it. Not for reviewing a spec or a plan (use /review), not for whole-repo architecture, dependencies or docs drift (use /review-health), not for user flow in a browser (use /review-experience).
    0 installs
  10. ▌
    Review Health · mxrsv bundle
    Structural health review of a repo — architecture and coupling, dependency risk, and drift between living docs/schema/config and the code. Use at a milestone, after a big refactor or merge, or as the first review on a never-reviewed repo; needs only the repo, no running app and no diff. Not for a specific change or diff (use /review-change), not for UX or runtime behavior (use /review-experience), not for a ship decision (use /review-release).
    0 installs
  11. ▌
    Context Budget · mxrsv
    Use to audit token consumption across always-loaded guidance — agents, skills, MCP servers, CLAUDE.md / AGENTS.md, rules, hooks and config — in Claude Code or Codex. Identifies bloat, redundancy and duplicate skill roots, and produces optimization recommendations. Meta-maintenance skill.
    0 installs
  12. ▌
    Review Release · mxrsv bundle
    Decide whether to ship, fix, refactor, keep building, or rethink — by synthesizing the review reports that /review-change, /review-experience and /review-health already posted as comments on the Linear issue. Use at a milestone, before cutting a release, or when stuck and unsure whether the work is ready to ship or needs more work first. Reads existing report comments on the issue plus your product direction; it never re-scans the codebase.
    0 installs
  13. ▌
    Security Review · mxrsv bundle
    Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
    0 installs
  14. ▌
    Review Experience · mxrsv bundle
    Review the real user experience of a running app in a real browser — walk the affected flows, force loading/error/empty states, check 375/768/1440, capture console and network evidence. Use after UI, navigation or flow changes when a dev or staging URL is reachable, or when the app is reported confusing or broken in actual use. Not for code-level bugs (use /review-change), not for architecture or docs health (use /review-health).
    0 installs
  15. ▌
    Codebase Onboarding · mxrsv
    Use when entering a new codebase, needing a fast architecture map, or generating onboarding notes from an unfamiliar project. Focuses on reconnaissance first, then targeted reads.
    0 installs
  16. ▌
    Frontend Design Bar · mxrsv bundle
    Use when building, reshaping, or reviewing any web UI (landing page, hero, dashboard, component, marketing site) and it must look designed, not generated. Triggers — a UI that reads flat, generic, templated, or static; calling UI "done" from code/build/TypeScript without looking at a screenshot; deciding whether a design is good enough to ship; prototyping a new template or hero.
    0 installs