all publishers

mew-ton

@mew-ton source repo

44 published skills

  1. ▌
    Soloscrum Define Dod · mew-ton
    Reference: soloscrum Definition of Done checklist. AC verified at the appropriate layer (Subtask PR slice + no regression; Issue-without-Subtasks full AC; parent Issue intent-level sign-off when all Subtasks close). Tests exist if applicable, PR body links Issue number with Closes/Fixes (per-Subtask PRs reference only the Subtask, never the parent), lint passes, review approved.
    0 installs
  2. ▌
    Soloscrum Create Issue · mew-ton
    Structures an idea into a GitHub Issue with Background, Goal, AC, and Out of Scope. Checks issue size, suggests splitting if over threshold, and determines priority and story points. Profile-agnostic.
    0 installs
  3. ▌
    Soloscrum Design UI Task · mew-ton
    Designs a Subtask (type design-ui) in Figma with design tokens, components, all component states, and state transition diagrams. Checks DoD and transitions the Subtask to In Review via the active profile's tracker operation skill on completion.
    0 installs
  4. ▌
    Soloscrum Implement Task · mew-ton
    Implements a develop work unit — Subtask or no-Subtask Issue (per soloscrum-define-branch-commit's case-split) — by creating a branch, writing code and tests, committing with Conventional Commits, generating a PR body, creating the PR as draft, and transitioning the target to In Review via the active profile's tracker operation skill.
    0 installs
  5. ▌
    Soloscrum Define Priority · mew-ton
    Reference: priority levels Urgent/High/Medium/Low and decision criteria. Urgent=blocker or outage, High=user impact or dependency, Medium=normal dev, Low=tech debt.
    0 installs
  6. ▌
    Soloscrum Define Worktree · mew-ton bundle
    Reference: where /soloscrum:develop does its work. Each work unit gets its own git worktree under a repo-internal root (default .soloscrum/worktrees), so the main checkout is never switched onto a feature branch. Defines the layout, the worktree_root resolution order, the create/reuse rules, and the merged-branch test /soloscrum:cleanup uses to reclaim them.
    0 installs
  7. ▌
    Soloscrum Define Task Type · mew-ton
    Reference: task type definitions. develop=code changes handled by soloscrum-dev, design-ui=Figma and design tokens handled by soloscrum-ui. UI features always split into design-ui then develop.
    0 installs
  8. ▌
    Soloscrum Split Into Tasks · mew-ton
    Breaks a GitHub Issue into subtasks with type (develop or design-ui) and story point estimates. Registers each subtask via the tracker operation skill matching the active profile.
    0 installs
  9. ▌
    Soloscrum Validate Feature · mew-ton
    Validates a feature's design for scope clarity, dependencies, and technical feasibility. Returns Pass/Conditional Pass/Fail with recommended actions.
    0 installs
  10. ▌
    Soloscrum Define Issue Size · mew-ton
    Reference: Issue and Subtask split criteria. Issues split when they bundle multiple independent intents (SP > 5 or subtask count > 5 are mis-scope smells, not hard work-volume limits). /soloscrum:breakdown fires when delivering one intent as a single PR would be unreviewable. Defines the suggest_split action, including the source Issue's terminal disposition after a split.
    0 installs
  11. ▌
    Soloscrum Define Pr Lifecycle · mew-ton
    Reference: PR phases (draft → review → ready → merge-handoff) and per-transition autonomy rules. Reversible transitions (gh pr create --draft, gh pr ready) run without pre-confirm; irreversible transitions (gh pr merge) are gated to the user. Used by implement-task, review-implementation, and the code-review-process verdict mapping.
    0 installs
  12. ▌
    Soloscrum Define Story Points · mew-ton
    Reference: story point scale and estimation criteria. SP is anchored on scope x uncertainty (size class, not a time unit); SP 5 is the upper bound and Issues estimated above it are mis-scope smells signalling likely intent bundling — return to /soloscrum:refine for Issue split per soloscrum-define-issue-size.
    0 installs
  13. ▌
    Soloscrum Define UI Standards · mew-ton
    Reference: UI design standards including token categories and naming convention, required component states (Default/Hover/Focus/Disabled/Error), and WCAG AA accessibility requirements.
    0 installs
  14. ▌
    Soloscrum Define Branch Commit · mew-ton
    Reference: branch naming ({type}/{issue-id}-{slug}, where issue-id is the Subtask or no-Subtask Issue), Conventional Commits, and parent Issue close convention (per-Subtask PRs close only the Subtask; parent closes via /soloscrum:refine janitor). Repo-specific strategy in .claude/rules/branch.md takes precedence.
    0 installs
  15. ▌
    Soloscrum Review Implementation · mew-ton
    Reviews a PR or Figma file against the DoD checklist with layered AC verification per soloscrum-define-dod (Subtask PR = slice + no regression; Issue-without-Subtasks PR = full AC; parent Issue intent-level sign-off = when all Subtasks close). PRs are expected in draft; on Pass the review agent promotes the PR to ready, transitions the Subtask to Done via the active profile's tracker operation skill, and hands the merge command off to the user. Issue close is not part of this sequence — it happens at merge time via the PR body's Closes
    0 installs
  16. ▌
    Soloscrum Tracker Github Set Sp · mew-ton
    Operation: set the SP value of a Subtask on a GitHub Projects v2 Number field. Used when active tracker profile is github-only.
    0 installs
  17. ▌
    Soloscrum Tracker Linear Set Sp · mew-ton
    Operation: set the SP value of a Linear subtask via the estimate field. Used when active tracker profile is linear+github.
    0 installs
  18. ▌
    Soloscrum Define Design Criteria · mew-ton
    Reference: criteria for validating feature design across scope clarity (Goal and AC alignment), dependency identification, and technical feasibility against the project stack.
    0 installs
  19. ▌
    Soloscrum Define Tracker Profile · mew-ton
    Reference: tracker profile (github-only or linear+github), how to resolve which profile is active, the storage/API mapping for every concept, and the routing rule that maps profile to operation skills.
    0 installs
  20. ▌
    Soloscrum Define Review Perspective · mew-ton bundle
    Reference: the Review Perspective format — a machine-local, self-describing unit of review knowledge stored at ~/.claude/review-perspectives/<name>/PERSPECTIVE.md. Defines the directory contract, the skill-shaped frontmatter, the description rules /soloscrum:review selects on (English, <=2048 chars, when + what + a stated boundary, decidable without the body), and why perspectives are deliberately not stored as skills.
    0 installs
  21. ▌
    Soloscrum Define Code Review Process · mew-ton
    Reference: standard code review pipeline (CodeRabbit + multi-agent review + the user's review perspectives) and the per-finding decision rules. Severity and confidence scores are inputs to a per-item decision, NOT auto-skip filters. Every CodeRabbit finding is surfaced and judged individually; agent-generated findings carry a confidence pre-filter, and perspective findings carry a grounding requirement — both suppress hallucinations without silently dropping signal.
    0 installs
  22. ▌
    Soloscrum Tracker Github Query State · mew-ton
    Operation: list Issues and Sub-issues currently In Progress or In Review on GitHub. Used when active tracker profile is github-only.
    0 installs
  23. ▌
    Soloscrum Tracker Linear Query State · mew-ton
    Operation: list Linear subtasks currently In Progress or In Review with linked PR or Figma URLs. Used when active tracker profile is linear+github.
    0 installs
  24. ▌
    Soloscrum Tracker Github Query Backlog · mew-ton
    Operation: list backlog Issues and Sub-issues from GitHub, ordered by priority. Used when active tracker profile is github-only.
    0 installs
  25. ▌
    Soloscrum Tracker Linear Query Backlog · mew-ton
    Operation: list backlog Linear Tasks and subtasks ordered by priority. Used when active tracker profile is linear+github.
    0 installs
  26. ▌
    Soloscrum Define Agent Responsibilities · mew-ton
    Reference: which agent or command creates, transitions, and verifies each soloscrum concept (Issue, Subtask, SP, type, priority, state, branch, PR, etc.). Tracker-profile-independent — use together with soloscrum-define-tracker-profile.
    0 installs
  27. ▌
    Soloscrum Tracker Github Add Dependency · mew-ton
    Operation: declare that one GitHub Issue depends on another by editing the body with a Depends on line. Used when active tracker profile is github-only.
    0 installs
  28. ▌
    Soloscrum Tracker Github Create Subtask · mew-ton
    Operation: create a subtask of a GitHub Issue using native GH Sub-issue. Used when active tracker profile is github-only.
    0 installs
  29. ▌
    Soloscrum Tracker Linear Add Dependency · mew-ton
    Operation: declare a blocking relation between Linear issues using Blocks/Blocked by. Used when active tracker profile is linear+github.
    0 installs
  30. ▌
    Soloscrum Tracker Linear Create Subtask · mew-ton
    Operation: create a Linear subtask under the Linear Task synced from a GitHub Issue. Used when active tracker profile is linear+github.
    0 installs
  31. ▌
    Soloscrum Tracker Github Transition State · mew-ton
    Operation: transition the state of a GitHub Issue or Sub-issue using state labels and open/close. Used when active tracker profile is github-only.
    0 installs
  32. ▌
    Soloscrum Tracker Linear Transition State · mew-ton
    Operation: transition the state of a Linear subtask via Linear MCP. Used when active tracker profile is linear+github.
    0 installs
  33. ▌
    Soloscrum Tracker Github Wait For Pr Checks · mew-ton bundle
    Operation: poll a GitHub PR's CI status checks until all of them complete (or until a timeout) and return their conclusions. Used by /soloscrum:develop and /soloscrum:review when the next step depends on green CI. Profile-agnostic — PRs live on GitHub regardless of tracker_profile, so both `github-only` and `linear+github` route here.
    0 installs
  34. ▌
    Starlight Skills Bp I18N · mew-ton
    Provides rules for handling multi-language documentation. Use this when configuring agent skill documents using starlight-skills on an i18n-enabled project. Do not use this for standard single-language sites or plugin configuration options.
    2 installs
  35. ▌
    Starlight Skills Started · mew-ton
    Provides core concepts and use cases for the starlight-skills plugin. Use this when you need to understand the philosophy or general purpose of dual-publishing documents and skills. Do not use this for installation steps, frontmatter syntax, or configuration options.
    4 installs
  36. ▌
    Starlight Skills Authoring · mew-ton bundle
    Provides rules and frontmatter schema for writing AI skills. Use this when you need to know how to add `skill: true`, configure skill metadata, or understand the naming constraints. Do not use this for plugin configuration options or deployment instructions.
    2 installs
  37. ▌
    Starlight Skills Deployment · mew-ton
    Provides deployment scenarios and Agent CLI installation methods for generated skills. Use this when you need to know about `well-known-endpoint` vs `collocated` output modes, or how an agent installs external skills. Do not use this for authoring skills or configuring frontmatter options.
    4 installs
  38. ▌
    Starlight Skills Installation · mew-ton
    Provides installation and basic setup instructions for starlight-skills. Use this when you need to add the plugin to a new Astro Starlight project or configure its initial setup. Do not use this if the plugin is already installed, or for frontmatter authoring rules.
    4 installs
  39. ▌
    Starlight Skills Configuration · mew-ton
    Provides all `astro.config.ts` plugin options for starlight-skills. Use this when you need to configure output modes, URL paths, automatic categories, sidebars, or other advanced build settings. Do not use this for frontmatter authoring rules or deployment procedures.
    1 install
  40. ▌
    Starlight Skills Bp Separate UI · mew-ton
    Provides rules for handling interactive frontend components in skill documents. Use this when migrating heavily interactive Astro or React pages into agent skill documents using starlight-skills. Do not use this to format plain text Markdown or configure frontmatter.
    6 installs
  41. ▌
    Starlight Skills Companion Files · mew-ton
    Provides instructions on how to use the `subfiles` frontmatter field. Use this when you need to attach external schemas, scripts, or large datasets to a skill without polluting the main markdown file. Do not use this for main skill body authoring or plugin configuration.
    4 installs
  42. ▌
    Starlight Skills Bp One Instruction · mew-ton
    Provides rules for scoping skill files. Use this when creating or refactoring agent skill documents using starlight-skills. Do not use this for general Markdown formatting or frontmatter configuration.
    2 installs
  43. ▌
    Starlight Skills Bp Semantic Markdown · mew-ton
    Provides rules for writing semantic Markdown to maximize agent comprehension. Use this when formatting the textual body of agent skill documents using starlight-skills. Do not use this for configuring YAML metadata or plugin options.
    2 installs
  44. ▌
    Starlight Skills Bp Descriptive Frontmatter · mew-ton
    Provides rules for writing effective skill descriptions. Use this when setting up frontmatter properties for agent skill documents using starlight-skills. Do not use this for structuring the actual text body or plugin configuration options.
    2 installs