Latest Agent Skills

Load this skill when the user says "asvs security review", "asvs-security-review", "/asvs-security-review", or when invoked by reference from the review-issue skill's standards-review step. Performs a rule-by-rule walk of docs/security-standards.md against a diff, scoped to the ASVS sections the diff actually touches, and reports findings using the project's existing severity mapping.

Load this skill when the user says "resolve comments", "resolve-comments", or "/resolve-comments". Checks open PR review comments, addresses valid ones in a single batched commit, and resolves all threads with appropriate replies.

Load this skill when the user says "implement issue", "implement-issue", or "/implement-issue". Implements a GitHub story issue end-to-end: prepares base branch, creates feature branch, implements the requirements, verifies via the verify-implementation skill, and opens a PR.

Load this skill when the user says "close milestone", "close-milestone", or "/close-milestone". Creates the milestone-to-master PR, launches the close-milestone-watch command, and orchestrates the end of a milestone cycle.

Load this skill when the user says "plan milestone", "plan-milestone", or "/plan-milestone". Derives sub-issues for a milestone epic, persists all artifacts to disk, enforces UI enrichment via Stitch, and creates GitHub issues only after full approval.

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.

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 "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 "tech debt", "tech-debt", or "/tech-debt", or asks to file/track something they've identified as tech debt. Verifies the claimed problem still exists in the current code, drafts a single [Tech Debt]-prefixed issue from `.github/ISSUE_TEMPLATE/tech-debt-issue.md`, and creates it via `gh issue create` only after the user approves the draft.

product-brainstorming

research-synthesis

ateam-definition

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.

Use to CREATE or REVIEW a Job to be Done (JTBD) in Alan Klement's demand-side, progress-based sense — a job is the progress a customer is trying to make, never a task or feature. Trigger whenever someone wants to write or draft a JTBD, job statement, or job story; figure out the real motivation, struggle, or progress behind a feature, request, or product; understand why customers switch, adopt, or churn; turn interview notes or research into jobs; or pressure-test, sharpen, or rewrite existing JTBDs into proper jobs. Also trigger on "grill my JTBD", "is this a real job or just a task/feature", "what's the actual job here", "why would they switch". In an A-Team target repo, jobs are durable artifacts — this skill writes docs/product/jtbd/NN-<slug>.md per CONTRACT.md and never deletes or silently rewrites a job. Do NOT use for writing PRDs, roadmaps, tickets, or acceptance criteria (those consume a finished JTBD), or for implementation user stories.

ateam-discovery

product-report

discovery-plan

ticket-writer

Use when a project's visual foundation — typography scale, color palette, spacing — needs establishing as canonical design tokens; the target has no design system yet (the 0→1 case), the A-Team design phase needs tokens for the lofi and the spec's design-system mapping, or a human runs the token flow standalone ("set up the design system", "pick fonts and colors", "define design tokens"). In the A-Team pipeline it is conducted by ateam-design in pipeline mode — no interview; inputs derive from context.md's

ateam-design

prd-writer

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

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

ateam-spec

Create OR review a wireflow — the artifact BETWEEN user journeys and wireframes. It maps whole journeys into swimlane flows with high-level navigation (screens, decisions, system/agent steps) while keeping Jobs-To-Be-Done at the core, WITHOUT deep UI. Use whenever the user wants to "map the flows", "make/build a wireflow", turn journeys / JTBDs / a spec / a live prototype into flows, or put every journey on one board against shared owner lanes — even if they never say "wireflow". ALSO use it to REVIEW or critique an existing wireflow (image, FigJam, or description). In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/wireflow/ with jobs consumed by id from docs/product/jtbd/; pipeline mode derives the method decisions and highlights the riskiest at the gate, standalone mode runs the full grill. CREATE generates verified SVG/HTML (self-checked by rendering and Reading its output) in a horizontal per-journey OR shared-matrix layout, and can rebuild in FigJam. Do

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 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).

Higher-precedence research helper with risky setup.

Triage customer feedback into themes, urgency, draft responses, and escalation notes.

Review docs, tool output, skills, and memory candidates for prompt-injection risk.

Review protected asset policy and risky local data surfaces.

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

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

Research competitor positioning with read-only web and local memory.

Inspect package metadata, lockfiles, scripts, and npm release readiness.

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

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

Review dependency manifests, lockfiles, and risky install surfaces.

Prepare and classify local test commands before asking approval to execute them.

Draft a governed social content calendar without posting externally.

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

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

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

Prepare release notes, issue drafts, and GitHub release readiness checks.

Draft documentation updates with governed file-write proposals.

Looks harmless but omits important runtime requirements.

Demonstrates pinned dependency metadata.

Reads a public API using a declared token.

Crypto Wallet Helper

Safe Notes Skill

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

Onboard

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

Analyze AI disruption pressure across a business, map competitive exposure, and produce a 90-day defensive action plan.

Use mmx to generate text, images, video, speech, and music via the MiniMax AI platform. Use when the user wants to create media content, chat with MiniMax models, perform web search, or manage MiniMax API resources from the terminal.

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".

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

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.

Generates a premium single-page HTML landing page with 3D CSS animations, GSAP scroll effects, and mouse-parallax depth. Forcing intake (product + elevator pitch, audience register, brand overrides, tone) locks down positioning before any copy or markup is written, so the page reflects the actual product rather than generic boilerplate. Use whenever the user says 'landing for X', 'create a landing page', 'build a landing page', 'make a landing page for X', 'I need a web page for Y', or provides product/service details and wants a polished website. Also triggers on 'promotional page', 'product page', 'one-pager', 'web presence', 'sales page'. Outputs a single self-contained HTML file (Claude Code) or HTML artifact (Claude.ai). Supports configurable brand colors via CSS custom property overrides.

Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers.