speedwave

Use Atlassian integration to query and manage Jira Cloud and Confluence Cloud, Jira issues, comments, worklogs and time tracking, transitions, assignments, agile boards/sprints, and Confluence pages, spaces, labels, attachments. Use whenever the user asks about Jira tickets/issues/sprints, logging work or time on a Jira issue, or Confluence pages/spaces, searching with JQL/CQL, getting or creating issues, transitioning workflows, finding or updating pages, etc. Use even when you think you know the answer, issue and page state are dynamic, only the live API reflects current assignments, transitions, comments, or page revisions. Do not use for self-hosted Jira/Confluence Server or Data Center (Cloud only), generic project management theory, or anything outside the configured Atlassian site.

Use the OS calendar integration to query and manage native macOS Calendar.app, listing calendars, fetching events by date range, creating/updating/deleting events, scheduling or rescheduling meetings, and checking availability. Use whenever the user asks about their calendar or schedule, for example "what have I got tomorrow", "am I free Thursday afternoon", "schedule a meeting with Anna at 3pm", or "cancel my 2pm". Use even when you think you know the answer, calendar state is dynamic, only the live API reflects current events, RSVP status, and shared-calendar updates. Do not use for non-macOS systems, third-party calendar services (Google Calendar API directly, Outlook web, etc.), those go through their own integrations if configured.

Use Context7 to fetch current library/framework/API/SDK/CLI/cloud-service documentation whenever the user asks about a named technology, including setup, configuration, code examples, version migration, library-specific debugging, best practices, and "is X the right way to do Y" questions. Covers popular technologies such as React, Next.js, Angular, Vue, Svelte, Prisma, Drizzle, Express, NestJS, FastAPI, Django, Flask, Spring Boot, Tailwind, shadcn/ui, and any other named library, SDK, API, CLI tool, or cloud service. This is documentation for the tool or library itself, not the user's own repo configuration or CI pipeline (use github or gitlab for that). Use even when you think you know the answer, your training data may not reflect recent changes. Prefer this over web search for library docs. Do not use for refactoring, writing scripts from scratch, debugging business logic, code review, or general programming concepts.

Use GitHub integration to query and manage GitHub.com repositories, pull requests, issues, branches, commits, Actions workflow runs, labels, tags, and releases. Use whenever the user asks about GitHub, opening or reviewing PRs, getting PR diffs, listing or commenting on issues, comparing branches, reading workflow logs, creating releases, searching code, checking "my open PRs" or "my assigned issues", etc. Use even when you think you know the answer, repository state is dynamic, only the live API reflects current PR status, workflow runs, or issue assignments. Do not use for plain git operations on the local checkout, GitLab or self-hosted GitHub Enterprise (out of scope), general code review questions, or any repo not on GitHub.com.

Use GitLab integration to query and manage projects, merge requests, issues, pipelines, branches, commits, files, and releases on the configured GitLab instance. Use whenever the user asks about GitLab, listing MRs, reviewing diffs, opening or merging MRs, creating/closing issues, comparing branches, reading pipeline status, fetching files, searching code, checking "my open MRs" or "my assigned issues", etc. Use even when you think you know the answer, repository state is dynamic and only the live API reflects current MR status, pipeline runs, or issue assignments. Do not use for plain git operations on the local checkout, GitHub.com (use github), general code review questions, or anything outside the configured GitLab instance.

Use the OS mail integration to query the user's native macOS Mail.app, listing mailboxes and accounts, searching messages, reading message bodies and attachments, and sending new mail through the configured accounts. Use whenever the user asks about email, for example "any new mail from Anna", "find that invoice email from last week", or "reply to Marek's message". Use even when you think you know the answer, inbox state is dynamic, only the live API reflects current messages, unread counts, and folder organization. Do not use for web-based mail (Gmail/Outlook web), non-macOS systems, email protocol questions (IMAP/SMTP), or generic email-marketing/composition advice.

Use the OS notes integration to query and manage native macOS Notes.app, listing folders and accounts, searching notes by title or body, reading note content, creating new notes, updating existing notes, and deleting notes. Use whenever the user asks about their notes, for example "save this as a note", "find my note about the vendor contract", or "what did I write about the Q3 plan". Use even when you think you know the answer, Notes state is dynamic, only the live API reflects current content, folder structure, and iCloud-sync updates. Do not use for non-macOS systems, other note apps (Obsidian, Bear, Logseq, Notion, etc.), or generic note-taking-methodology advice.

Use Office integration to read, create, edit, and convert Word/Excel/PowerPoint/PDF documents, and to render charts. Use whenever the user asks about working with .docx, .xlsx, .pptx, or .pdf files, for example "turn this into a report", "make me an invoice", "convert this to PDF", or "merge these PDFs", reading content, creating reports or invoices, editing existing documents, converting between formats, merging or splitting PDFs, or rendering charts. Use even when you think you know the answer, document libraries change between framework versions, only the live tool reflects current Office/PDF format support and chart rendering capabilities. Do not use for plain text files (read them directly), generic Markdown conversion that does not need PDF output (use built-in tools), or installing document-processing libraries, they are already behind office.* tools.

Use Playwright integration to browse the web, take screenshots, and interact with web pages in a headless Chromium browser. Use whenever the user asks to screenshot a page, navigate to a URL, check what is on a website, fill a form, click through a flow, or extract content from a rendered page. Use even when you think you know the page content, websites change constantly, only the live browser reflects current rendering, JS-injected content, and dynamic state. Do not use for fetching plain HTML or JSON that does not need JavaScript rendering (use WebFetch), scraping that violates the site's terms of service, anything requiring credentials the user has not provided, or local file access (the Playwright container has no /workspace mount).

Use Redmine integration to query and manage Redmine projects, issues, time entries, journals, comments, relations, and user mappings. Use whenever the user asks about Redmine, for example finding or creating issues, listing assigned tickets, logging time, commenting, transitioning status, linking issues, or looking up project members. Use even when you think you know the answer, issue and project state are dynamic, only the live API reflects current assignments, status, or time entries. Do not use for project management theory, anything outside the configured Redmine instance, or wiki content (no wiki tools available, use playwright or paste the URL).

Use the OS reminders integration to query and manage native macOS Reminders.app, listing reminder lists, fetching reminders by list or due date, creating new reminders, updating, completing, or deleting them. Use whenever the user asks about reminders or to-dos, for example "remind me to call the client tomorrow", "what's on my errands list", or "mark that reminder done". Use even when you think you know the answer, Reminders state is dynamic, only the live API reflects current items, due dates, and completion status. Do not use for non-macOS systems, other reminder/task apps (Todoist, TickTick, etc.), or anything outside the user's local Reminders.app.

Use SharePoint integration to read, write, and manage files, document libraries, lists, list items, columns, and pages on the configured Microsoft 365 site. Use whenever the user asks about SharePoint, listing or searching files in a document library, uploading or downloading, creating or updating lists and items, adding columns, creating or publishing pages, or adding web parts. Use even when you think you know the answer, site state is dynamic, only the live API reflects current files, list items, or page versions. Do not use for Microsoft 365 Outlook/Teams/OneDrive operations not surfaced via SharePoint, cross-site or cross-tenant ops (only the configured site), or generic Microsoft Graph questions.

Use Slack integration to read and send Slack messages as the signed-in user, listing the channels they belong to, reading or exporting channel history and threads (with pagination), reading and sending direct messages (1:1 DMs and group DMs), reading text files shared in channels (markdown, code, logs), posting messages, and finding workspace users by name or e-mail. Use whenever the user asks about Slack, for example "what's new on

Review code for adherence to project guidelines, style guides, and best practices.

Assess the blast radius of a change — breaking API/contract changes, data-migration safety, and the risk of new or changed dependencies.

Analyze code comments for accuracy, completeness, and long-term maintainability.

Verify if code changes require documentation updates. Use during code review to ensure documentation stays synchronized with code — prevents documentation drift.

Detect code duplication and identify refactoring opportunities to ensure DRY compliance.

Detect KISS violations — over-engineering, unnecessary complexity, convoluted solutions — and suggest concrete simplifications that preserve behavior.

Detect performance and concurrency defects — algorithmic complexity on hot paths, N+1 patterns, unbounded growth, blocking calls, data races, deadlocks, atomicity violations.

Detect security vulnerabilities in code changes — injection attacks, auth bypass, data exposure, crypto weaknesses. Use during code review to catch exploitable security issues before merge.

Identify silent failures, inadequate error handling, and inappropriate fallback behavior in code.

Detect SOLID principle violations (SRP, OCP, LSP, ISP, DIP) that make code hard to maintain and extend.

Detect Single Source of Truth violations including duplicated configurations, types, and scattered constants.

Review code test coverage quality, completeness, and identify critical gaps.

Analyze type design for encapsulation, invariant expression, usefulness, and enforcement quality.

Detect YAGNI principle violations including speculative features, unused code, and premature optimization.

Comprehensive multi-dimensional code review — runs every specialized code-review skill in parallel and aggregates verified results

Build a self-contained, dependency-free animated "live product" demo for a landing page — a step carousel that faithfully recreates the real app UI (chat, settings, integrations, logs…) using only HTML + scoped CSS + one inline rAF script. Use when asked to add an animated product walkthrough / hero demo / "show the app in motion" to a marketing site.

Audit a website against a bundled checklist of best-practice rules (Foundations, SEO, Accessibility, Security, Performance, Privacy, Resilience, i18n, Well-Known URIs, Agent Readiness) and report which pass, fail, or are skipped — with evidence. Use when the user asks to "audit a site", "check if a website is built correctly", "review accessibility / SEO / security of a page", or "run the website checklist". Works on one URL or every URL from the sitemap (pairs with speedwave-sitemap). Always runs a final verifier pass. Do not use for: producing a sitemap (use speedwave-sitemap), or fixing the issues — this skill only reports.

Provide the URL inventory of a website as structured JSON for other skills to consume. First tries to extract an existing sitemap (robots.txt + common sitemap.xml paths, expanding sitemap indexes); if none is found, crawls the site via the Playwright integration (same-domain, bounded). Use whenever another skill or the user needs "the list of pages", "the sitemap", "all URLs of a site", or a page inventory to audit. Returns JSON only — no SEO analysis, no reports, no recommendations. Do not use for: auditing the pages, generating a sitemap from templates, or anything beyond producing the URL list.