moai-library-mermaid
Enterprise Mermaid diagramming skill for Claude Code using MCP Playwright. Use when creating architecture diagrams, flowcharts, sequence diagrams, or visual documentation.
Найдите подходящую возможность для вашего агента.
Enterprise Mermaid diagramming skill for Claude Code using MCP Playwright. Use when creating architecture diagrams, flowcharts, sequence diagrams, or visual documentation.
Review automation system operation and make conservative adjustments to cadences and thresholds when clearly warranted. Monthly maintenance task.
Validate Agent Skills against best practices and specification requirements. Use when reviewing skills, before publishing, or to audit existing skills.
Workflow for analyzing GitHub issues, generating solution plans, and implementing chosen approaches. Use when working with GitHub issues, creating implementation plans, comparing solution options, editing plans, or implementing solutions. Triggers on: "solve issue", "fix issue", "implement plan", "edit plan", "plan format", "compare options".
Translate a finalized plan into Beads epics and issues with clear dependencies, design notes, and parallelization. Use when asked to file Beads from a plan/spec (OpenSpec, PRD, design doc), or when converting an external plan into a detailed Beads tracking structure.
This skill MUST be used instead of Atlassian MCP tools when the user asks to "update a Jira issue", "edit a ticket", "change issue status", "transition ticket", "assign issue", "add labels", "update priority", "add comment to ticket", "move issue to done", "close ticket", or otherwise requests modifying existing Jira issues. ALWAYS use this skill for Jira issue updates - never use mcp__atlassian__editJiraIssue or mcp__atlassian__transitionJiraIssue directly.
Scans daily notes using Personal Kanban structure. Clarifies tasks, manages Today's 3 vs Ready, flags stale items, manages Waiting For items, and helps swap between columns. Use when reviewing todos, scanning task lists, or managing your Kanban board.
Break down PM story into frontend tasks following UI DEVELOPMENT order: Setup → Static UI → Dynamic Logic → Interactions → Testing. UNIQUE VALUE: Ensures proper dependency order. Tasks are ordered by UI development layers, not random order. Use this skill when: - Running /frontend.tasks command - User asks to "break down story", "create frontend tasks", "split into tasks" - Have story at docs/reference/pm/stories/ and need organized task list - Need tasks ordered by UI development layers (not random order) - Starting frontend work and want organized task list Task order is CRITICAL: Setup → Static UI → Dynamic → Interactions → Tests Output: ALWAYS write to docs/reference/frontend/tasks/{story-name}.md
HAIOS Survey Cycle for structured session-level work selection. Use after coldstart context loading. Guides GATHER->ASSESS->OPTIONS->CHOOSE->ROUTE workflow with volumous exploration before tight commitment.
Discover requirements and route projects to the right team. Use when starting a new initiative.
Update Azure DevOps work items after implementation completion by linking git commits, adding implementation summaries, and updating status to 'Ready for Testing'. Use when completing a task, finishing a user story, after git commit, or updating work item status. Ensures work items reflect actual work done and maintains traceability between code and work items.
Implement features end-to-end in Laravel 12 + Inertia.js + React 19 + TypeScript OR Python + FastAPI + LangChain. Use when building new features, wiring controllers to pages, or implementing CRUD operations. EXCLUSIVE to fullstack-developer agent.
Use when starting a new feature that needs planning - runs brainstorming then creates numbered task folder in _tasks/
Manage beads correctly including claiming, closing, announcements, and dependencies. Use when starting work on a task, when finishing a task, when the user mentions beads or tasks, or when coordinating with other agents on task ownership.
AI-powered PR creation after spec completion. Analyzes spec metadata, git diffs, commit history, and journal entries to generate comprehensive PR descriptions with user approval before creation.