Canonical quality engineering: test strategy, case generation, coverage gates, exploratory checks, and security-tinged QA (incl. Shannon-style pentest track when requested).
Canonical playbook for AI coding assistants and CLI pair-programmers (Claude Code, Kilo, Goose, OpenCode, multi-CLI toolkits). Use when choosing or operating an assistant workflow inside the project.
Generative algorithmic art. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized algorithmic-art work when listed in TEAM.yaml or explicitly requested.
Expert API design and delivery: resource modeling, versioning, consistent error envelopes, pagination/filtering, idempotency, OpenAPI/contracts, and boundary validation. Use when defining or changing REST (or HTTP) APIs, DTO/request-response shapes, client integration contracts, or when reviewing endpoint consistency…
Expert backend application engineering: layered architecture, domain services, validation, transactions, caching boundaries, background jobs, and framework idioms (e.g. Laravel/Node) without leaking business rules into controllers. Use when implementing or refactoring server-side features, services, form…
Prefer this for any 3D modeling, mesh, scene, render, or Blender request (e.g. "buat model 3D ikan", character, prop). Drive Blender via BlenderMCP (addon :9876 + blender-mcp). Do not offer script-only / trimesh menus first when Blender MCP can be used. Wire mcp/blender if missing.
Design system framework. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized canvas-design work when listed in TEAM.yaml or explicitly requested.
Canonical spec and requirements skill: 5-phase clarity workflow plus Spec-Kit / markdown-agent spec patterns. Use for PRD, SRS, AC, and implementable specifications before coding.
Video clipper and repurposing ops for creator-approved promotion: consent intake, highlight selection, short-form cuts, captions/branding, attribution, and platform-safe publish handoff. Use when a creator wants clippers to promote their content via clips, Shorts, Reels, or compilations.
AWS, Azure, GCP CLIs. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized cloud-tools work when listed in TEAM.yaml or explicitly requested.
Expert code review against architecture and coding standards: readability, maintainability, security, performance, layering, Sonar-equivalent cleanliness, comment and formatting discipline, modal safety, and a strict ban on raw SQL or database queries outside the persistence layer. Author/date file headers are…
ComfyUI image generation MCP server (GPU required). Use when the project needs this capability or the user / team manifest asks for it. Use for specialized comfyui work when listed in TEAM.yaml or explicitly requested.
Persistent memory layer for Claude Code's /compact command. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized compahook work when listed in TEAM.yaml or explicitly requested.
.NET development environment. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized dotnet work when listed in TEAM.yaml or explicitly requested.
Instance agent for mimir fleet management. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized draupnir work when listed in TEAM.yaml or explicitly requested.
End-to-end software house delivery. Use whenever the user asks to build a feature, fix a non-trivial bug, start a project, or run the full workflow. Orchestrates all roles and executes through Release unless blocked. Skip when WORKMODE is manual unless user/command forces E2E.
General engineering technical interviews: backend, frontend, fullstack, mobile, DevOps tracks — live coding, debugging, system design light, take-home briefs, rubrics, and candidate practice. Not HR-specific; use for technical interview, technical test, mock interview, live coding, system design interview, persiapan…
FFmpeg media processing. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized ffmpeg-processing work when listed in TEAM.yaml or explicitly requested.
Expert frontend application engineering: accessible UI structure, state and data-fetching discipline, form/validation UX, responsive layouts, performance budgets, and integration with API contracts. Use when building or refining SPA/web screens, design-system consumption, client-side routing, or fixing UI reliability…
★not rated 2 yesterdayA67 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: