Loading...
Loading...
Found 318 Skills
Generate structured product and technical documents through guided discovery. 8 document types: PRD, Brief, Issue, Task, User Story, RFC, ADR, TDD. Use when: defining products, reporting bugs, planning sprints, writing stories, proposing changes, recording decisions, designing systems. Triggers on "create PRD", "create issue", "report bug", "feature request", "create task", "create user story", "create RFC", "create ADR", "create TDD", "create document", "write doc".
Creates professional investment banking strip profiles (company profiles) for pitch books, deal materials, and client presentations. Generates 1-4 information-dense slides with quadrant layouts, charts, and tables.
Guides management consulting-style work—engagement framing, hypothesis-driven problem structuring, issue trees, business cases, operating model and capability design, strategic options analysis, workshop facilitation, and executive recommendations (not legal advice). Use when diagnosing a business problem, structuring a strategy or transformation initiative, building a business case for leadership, designing target operating models, preparing steerCo or board recommendations, or advising on build-vs-buy and portfolio priorities—not for detailed requirements/BRDs (business-analyst), multi-team delivery tracking (technical-program-manager), contract negotiation (commercial-counsel), revenue accounting (senior-revenue-accountant), applied AI architecture (applied-ai-architect-commercial-enterprise), or system ADRs (senior-system-architecture). Canvas/TAM: business-model-researcher. Comms: communication-lead. M&A closing: transaction-manager. M&A principal/IC: transaction-principal.
This skill should be used when content teaches patterns (skills, subagents, ADRs, PHRs, specifications) that have canonical sources elsewhere. Prevents format drift by ensuring content references and follows the authoritative format from canonical sources. Use before implementing lessons that teach platform patterns, or when reviewing content for format consistency.
Detects orphaned code (files/functions that exist but are never imported or called in production), preventing "created but not integrated" failures. Use before marking features complete, before moving ADRs to completed, during code reviews, or as part of quality gates. Triggers on "detect orphaned code", "find dead code", "check for unused modules", "verify integration", or proactively before completion. Works with Python modules, functions, classes, and LangGraph nodes. Catches the ADR-013 failure pattern where code exists and tests pass but is never integrated.
Bootstrap AGENTS.md as a short table-of-contents plus a structured docs/ directory (architecture, product specs, acceptance tests, ADRs, exec plans, quality grades). Use when AGENTS.md is missing, when asked to "create AGENTS.md", "bootstrap project for agents", or "set up agent context".
ASP.NET Core WebApi 整合測試完整指南。當需要對 WebApi 端點進行整合測試或驗證 ProblemDetails 錯誤格式時使用。涵蓋 WebApplicationFactory、IExceptionHandler、Testcontainers 多容器編排、Flurl URL 建構與 AwesomeAssertions HTTP 驗證。 Keywords: webapi integration testing, WebApplicationFactory, asp.net core integration test, webapi 整合測試, IExceptionHandler, ProblemDetails, ValidationProblemDetails, AwesomeAssertions, Flurl, Respawn, Be201Created, Be400BadRequest, 多容器測試, Collection Fixture, 全域例外處理
Expert guide for the payload-reserve plugin — a Payload CMS 3.x reservation/booking system. Use when working with: reservation systems, booking systems, appointment scheduling, calendar views, availability checks, conflict detection, double-booking prevention, status workflows (pending/confirmed/completed/cancelled/no-show), buffer times, cancellation policies, schedule management, service/resource configuration, customer management, walk-in bookings, or integrating payments (Stripe) and notifications with a Payload CMS reservation plugin. Triggers on: "payload-reserve", "payloadReserve", "reservation plugin", "booking plugin", "appointment plugin", "schedule plugin", "availability overview", "calendar view", "reservation conflict", "double booking", "booking status", "cancellation policy".
Create, validate, and transition documentation artifacts (Vision, Journey, Epic, Story, Agent Spec, Spike, ADR, Persona, Runbook, Bug, Design) and their supporting docs (architecture overviews, journey maps, competitive analyses) through their lifecycle phases. Use when the user wants to write a spec, plan a feature, create an epic, add a user story, draft an ADR, start a research spike, define a persona, create a user persona, create a runbook, define a validation procedure, file a bug, report a defect, create a design, capture a wireframe, document a UI flow, sketch interaction states, update the architecture overview, document the system architecture, move an artifact to a new phase, seed an implementation plan, implement a spec, fix a bug, work on a story, or validate cross-references between artifacts. When a SPEC, STORY, or BUG comes up for implementation, always chain into the swain-do skill to create a tracked plan before any code is written. When swain-do is requested on an EPIC, VISION, or JOURNEY, decompose into implementable children first — swain-do runs on the children, not the container. Covers any request to create, update, review, or transition spec artifacts and supporting docs.
Generate a SYSTEM_OVERVIEW.md that orients a senior engineer new to an unfamiliar codebase, with a Mermaid architecture diagram, a sequence diagram for data flow, and a legacy-pattern assessment. Use when user says 'give me a system overview', 'onboard me on this repo', 'walk me into this legacy codebase', 'document the high-level architecture', or 'create a SYSTEM_OVERVIEW.md'. Do NOT use for code walkthroughs (use explain), persistent architecture chapters (use arc42), or ADRs (use document-decision).
Use when working on Laminar demands via the remote Laminar MCP and you see wrong or empty client/product scope, plans from source-context lists without per-id loads, needless raw transcripts, same-step or same-release story-map peers, anchored ADR conflicts, MCP transitions/assignments, broken or silent MCP, or mentions of Laminar MCP, demands, TAL-* ids, story map, anchored or source context, or Laminar handoff.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.