mew-ton
- 44 skills
- 0 followers
- yesterday last updated
- ▌ Soloscrum Define Dod · mew-tonReference: 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.
- ▌ Soloscrum Create Issue · mew-tonStructures 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.
- ▌ Soloscrum Design UI Task · mew-tonDesigns 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.
- ▌ Soloscrum Implement Task · mew-tonImplements 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.
- ▌ Soloscrum Define Priority · mew-tonReference: priority levels Urgent/High/Medium/Low and decision criteria. Urgent=blocker or outage, High=user impact or dependency, Medium=normal dev, Low=tech debt.
- ▌ Soloscrum Define Worktree · mew-ton bundleReference: 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.
- ▌ Soloscrum Define Task Type · mew-tonReference: 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.
- ▌ Soloscrum Split Into Tasks · mew-tonBreaks 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.
- ▌ Soloscrum Validate Feature · mew-tonValidates a feature's design for scope clarity, dependencies, and technical feasibility. Returns Pass/Conditional Pass/Fail with recommended actions.
- ▌ Soloscrum Define Issue Size · mew-tonReference: 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.
- ▌ Soloscrum Define Pr Lifecycle · mew-tonReference: 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.
- ▌ Soloscrum Define Story Points · mew-tonReference: 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.
- ▌ Soloscrum Define UI Standards · mew-tonReference: UI design standards including token categories and naming convention, required component states (Default/Hover/Focus/Disabled/Error), and WCAG AA accessibility requirements.
- ▌ Soloscrum Define Branch Commit · mew-tonReference: 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.
- ▌ Soloscrum Review Implementation · mew-tonReviews 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
- ▌ Soloscrum Tracker Github Set Sp · mew-tonOperation: set the SP value of a Subtask on a GitHub Projects v2 Number field. Used when active tracker profile is github-only.
- ▌ Soloscrum Tracker Linear Set Sp · mew-tonOperation: set the SP value of a Linear subtask via the estimate field. Used when active tracker profile is linear+github.
- ▌ Soloscrum Define Design Criteria · mew-tonReference: criteria for validating feature design across scope clarity (Goal and AC alignment), dependency identification, and technical feasibility against the project stack.
- ▌ Soloscrum Define Tracker Profile · mew-tonReference: 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.
- ▌ Soloscrum Define Review Perspective · mew-ton bundleReference: 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.
- ▌ Soloscrum Define Code Review Process · mew-tonReference: 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.
- ▌ Soloscrum Tracker Github Query State · mew-tonOperation: list Issues and Sub-issues currently In Progress or In Review on GitHub. Used when active tracker profile is github-only.
- ▌ Soloscrum Tracker Linear Query State · mew-tonOperation: list Linear subtasks currently In Progress or In Review with linked PR or Figma URLs. Used when active tracker profile is linear+github.
- ▌ Soloscrum Tracker Github Query Backlog · mew-tonOperation: list backlog Issues and Sub-issues from GitHub, ordered by priority. Used when active tracker profile is github-only.
- ▌ Soloscrum Tracker Linear Query Backlog · mew-tonOperation: list backlog Linear Tasks and subtasks ordered by priority. Used when active tracker profile is linear+github.
- ▌ Soloscrum Define Agent Responsibilities · mew-tonReference: 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.
- ▌ Soloscrum Tracker Github Add Dependency · mew-tonOperation: 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.
- ▌ Soloscrum Tracker Github Create Subtask · mew-tonOperation: create a subtask of a GitHub Issue using native GH Sub-issue. Used when active tracker profile is github-only.
- ▌ Soloscrum Tracker Linear Add Dependency · mew-tonOperation: declare a blocking relation between Linear issues using Blocks/Blocked by. Used when active tracker profile is linear+github.
- ▌ Soloscrum Tracker Linear Create Subtask · mew-tonOperation: create a Linear subtask under the Linear Task synced from a GitHub Issue. Used when active tracker profile is linear+github.
- ▌ Soloscrum Tracker Github Transition State · mew-tonOperation: transition the state of a GitHub Issue or Sub-issue using state labels and open/close. Used when active tracker profile is github-only.
- ▌ Soloscrum Tracker Linear Transition State · mew-tonOperation: transition the state of a Linear subtask via Linear MCP. Used when active tracker profile is linear+github.
- ▌ Soloscrum Tracker Github Wait For Pr Checks · mew-ton bundleOperation: 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.
- ▌ Starlight Skills Bp I18N · mew-tonProvides 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.
- ▌ Starlight Skills Started · mew-tonProvides 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.
- ▌ Starlight Skills Authoring · mew-ton bundleProvides 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.
- ▌ Starlight Skills Deployment · mew-tonProvides 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.
- ▌ Starlight Skills Installation · mew-tonProvides 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.
- ▌ Starlight Skills Configuration · mew-tonProvides 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.
- ▌ Starlight Skills Bp Separate UI · mew-tonProvides 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.
- ▌ Starlight Skills Companion Files · mew-tonProvides 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.
- ▌ Starlight Skills Bp One Instruction · mew-tonProvides 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.
- ▌ Starlight Skills Bp Semantic Markdown · mew-tonProvides 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.
- ▌ Starlight Skills Bp Descriptive Frontmatter · mew-tonProvides 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.