All Skills

Use HasData APIs for web scraping and structured web data extraction.

Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with mermaid user journey and kill criteria.

Presentation creation, format conversion (ODP/PPTX/PDF), slide automation with LibreOffice Impress.

Algorithm-first discipline: state Big-O, data structure, and algorithm family BEFORE writing loops, queries, or recursion. Catches O(n^2), N+1, and brute-force defaults.

LLM Operations -- RAG, embeddings, vector databases, fine-tuning, prompt engineering avancado, custos de LLM, evals de qualidade e arquiteturas de IA para producao.

Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".

CRITICAL: Use for MolyKit AI chat toolkit. Triggers on: BotClient, OpenAI, SSE streaming, AI chat, molykit, PlatformSend, spawn(), ThreadToken, cross-platform async, Chat widget, Messages, PromptInput, Avatar, LLM

Onboard

Write idiomatic PHP code with generators, iterators, SPL data structures, and modern OOP features. Use PROACTIVELY for high-performance PHP applications.

Reads a public API using a declared token.

Demonstrates pinned dependency metadata.

Looks harmless but omits important runtime requirements.

Review governed memory proposals, policy tags, tombstones, and effective memory.

Inspect a project and propose safe cleanup of generated or cache files.

Prepare release readiness notes, version checks, test checklist, and local issue drafts.

Review dependency manifests, lockfiles, and risky install surfaces.

Inspect local project structure, git state, docs, and relevant governed memory.

Perform read-only web research with governed browser proposals for manual review.

Create a daily business brief from local docs, memory, tasks, and safe web context.

Plan cafe marketing work across daily posts, promotions, feedback, and local competition.

Review protected asset policy and risky local data surfaces.

Higher-precedence research helper with risky setup.

Use when delivery work needs structuring into epics — defining a new epic, refining or superseding an existing one, or decomposing a PRD's requirements into durable delivery structures that feed issue decomposition. Writes docs/product/epics/NN-<slug>.md (durable, id-stable, superseded-never-deleted), each epic tracing to the JTBD ids it serves and the PRD requirement IDs it bundles. In the A-Team pipeline this is a definition-phase output ("the Epics"). Do not use for full roadmap/portfolio planning across quarters (deliberately not ported), for delivery tickets or acceptance criteria (ticket-writer), or to create or revise jobs (jobs-to-be-done).

Use when driving a feature prompt to a production-ready PR through discovery, definition, design, spec, issues, and dev phases, or when the user runs /feature or /feature resume — orchestrates the A-Team agentic pipeline over a target repo.

Use when a feature's screens and flows are drafted and the design phase needs a navigable wireframe — a multi-screen greyscale Astro prototype where buttons and links actually work, suitable for the design gate and moderated user testing. In the A-Team pipeline it is conducted by ateam-design and consumes design.md's

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc

prd-writer

ticket-writer

discovery-plan

product-report

Use when a project's durable context needs to be seeded or refreshed — creating or updating docs/product/context.md (overview + digest + source index + glossary + Know/Don't-Know ledger + design context + technical context) in the target repo; when a project has no context layer yet (Stage-0 setup); when domain terminology is still forming or has drifted; after a meeting, new evidence batch, or scope change that outdates the current context. Also use to ingest new docs/product/input/ batches into the digest. Do not use for repo scaffolding or CI setup, for writing the discovery plan, PRD, or epics (use discovery-plan, prd-writer, epics), or for creating or revising Jobs to be Done — this skill records finished JTBDs by id and marks missing ones TBD; jobs-to-be-done owns minting them.

ateam-definition

research-synthesis

Load this skill when the user says "close issue", "close-issue", or "/close-issue". Verifies IT and UC acceptance criteria for a story issue, ticks off passing checkboxes, and closes the issue only if all criteria pass and the linked PR has been merged.

Load this skill when the user says "prepare base", "prepare-base", or "/prepare-base". Prunes remote tracking references, checks out a base branch, pulls latest, and cleans up local-only feature branches after confirmation.

Load this skill when the user says "review issue", "review-issue", or "/review-issue". Reviews an implemented GitHub issue against its requirements and the project coding standards, acting as a critical tech-lead review pass before merging.