ms2sato
- 11 skills
- 0 followers
- 1 week ago last updated
- ▌ Coderabbit Ops · ms2sato bundleCodeRabbit code review operations playbook + troubleshooting / FAQ. Use when creating a PR, before merge, when handling CodeRabbit issues (rate-limit fallback, GitHub-side bot unresponsive, both layers simultaneously rate-limited), or when interpreting the CodeRabbit verdict surfaces (pre-merge checks / reviewDecision / inline comments / commit-status description / formal review bodies). Covers local CLI invocation, GitHub-side bot interpretation, and case-by-case dispositions.
- ▌ Backend Standards · ms2sato bundleDetailed backend patterns and code examples for server implementation. Use when you need step-by-step guidance or concrete code patterns beyond what the auto-loaded backend rules provide.
- ▌ Frontend Standards · ms2sato bundleDetailed React patterns and code examples for frontend implementation. Use when you need step-by-step guidance or concrete code patterns beyond what the auto-loaded frontend rules provide.
- ▌ UX Design Standards · ms2sato bundleUX design principles for agent-console. Use when designing features, evaluating acceptance criteria, or reviewing user-facing interactions in a multi-agent management UI.
- ▌ Code Quality Standards · ms2sato bundleCode quality evaluation criteria for reviews. Use when reviewing code design, architecture, maintainability, or identifying potential issues.
- ▌ Dev Environment Quirks · ms2satoNon-obvious operational details of the local dev environments (single-user `dev.sh`, multi-user `dev-multiuser.sh`, Docker dev stack `docker/docker-compose.yml`) — port layout, source-code propagation, sudo boundaries, multi-repo coexistence. Read when a delegated agent or the Orchestrator first needs to interact with the running dev instance, especially for Browser QA, log inspection, or restart workflows.
- ▌ Architectural Invariants · ms2satoCatalog of cross-cutting architectural invariants that code must respect. Use when designing, implementing, or reviewing features that involve shared resources, persistence, or I/O symmetry. Ask each catalog question against the change.
- ▌ Brewing · ms2satoEvaluate a merged PR against the architectural-invariants catalog and propose a new invariant entry when warranted. Use when the Orchestrator (or a delegated sub-agent) is surveying a recent PR for cross-cutting patterns that the existing catalog does not cover.
- ▌ Architect · ms2satoArchitect role owning implementation artifact quality — Acceptance Criteria authoring and code appropriateness review — plus design review, spec drafting, multi-round audit, and cross-domain design consultation. One Architect per repository, auto-provisioned by the Orchestrator. Owner never invokes this skill directly — the Orchestrator relays consultation requests; delegate workers may push directly for implementation uncertainty.
- ▌ Browser QA · ms2sato bundleManual browser QA via Chrome DevTools MCP. Use when acceptance criteria include manual verification or UI changes need visual confirmation.
- ▌ Orchestrator · ms2sato bundleOwner-facing single-role interface. Coordinates delegate workers (implementation) and the Architect (AC authoring, code appropriateness review, design / spec). Owns prioritization, dispatch, behavior verification (tests / CI / dogfood), merge authority, retro, and rule maintenance. Auto-provisions the Architect session on startup. Use when managing development agents, making prioritization decisions, or running the sprint lifecycle.