Configure and maintain Deno development commands (check, test, dev, prod). Use when the user wants to set up or update the standard command interface in deno.json and scripts/ directory.

Commit current changes as atomic, conventional commits with targeted documentation sync — groups the diff into logical commits and updates the docs each change affects.

Adapt project-local flowai primitives (skills, agents, AGENTS.md artifacts, hooks) to project specifics. Standalone adaptation — independent of update.

Use when the user asks to add TypeScript strict-mode code-style rules to AGENTS.md for a TypeScript project using strict mode. Do NOT trigger for Deno projects (use setup-agent-code-style-deno) or non-strict TS configurations.

Use when the user asks to add Deno/TypeScript code-style rules to AGENTS.md, or during initial Deno project setup when code-style guidelines need to be established. Do NOT trigger for non-Deno TypeScript projects (use setup-agent-code-style-strict), or for runtime-agnostic style advice.

Test a client against a Prism mock server built from an OpenAPI spec. Use when the user wants to test against a mock API, drive a client or harness through an OpenAPI spec, verify request payloads or 422 behavior against a spec, or when a task needs a local fake of a REST API for fast, deterministic testing.

Use when the user provides a source (URL, file path, or free text) to save into the project's memex — a long-term knowledge bank for AI agents. Stores the raw source, extracts entities into cross-linked pages, runs a backlink audit, and updates the index and activity log. Do NOT trigger on casual reads; only when the intent is to persist a source into the memex.

Use when the user asks to audit a memex (long-term knowledge bank for AI agents) for orphans, dead SALP REFs, missing sections, contradictions, or index drift. Runs a deterministic structural check, layers LLM-judgement findings, optionally auto-fixes trivial issues with `--fix`. Do NOT trigger on general code linting.

Use when the user asks a question to be answered from the project's memex (long-term knowledge bank for AI agents) rather than training data or the live web. Reads the index, opens relevant pages, follows one SALP-REF hop, synthesises a cited answer, files it back. Do NOT trigger on source-code or live-session questions.

Produce a comprehensive Product Requirements Document (PRD). Use when the user asks to write a PRD or formalize a feature's scope, goals, and success metrics.

Rewrite text in a dense, factual informational style with no fluff or marketing. Use when the user asks to write or rewrite docs or notes concisely or to apply a neutral informational tone.

Author task files in the GODS framework (Goal, Overview, Definition of Done, Solution). Use when the user asks to write, structure, or break down a task or plan in GODS format.

Write a Development Enhancement Proposal (DEP) for a technical improvement. Use when the user wants to propose, document, or formalize a technical change for review.

Create and manage GitHub issues using the GODS framework. Use when creating, updating, or triaging GitHub issues.

Creates interactive HTML teaching materials with clickable state diagrams. Use when the user asks to produce an explorable tutorial artifact, not to answer a question.

Fix failing or broken tests by finding the root cause and correcting the source code (not the test). Use when tests fail, a suite is red, or the user asks to fix or repair tests or a CI test failure.

Guide to writing prompts for reasoning models (Gemini Pro, GPT-4o, Claude Sonnet), focused on structure and context. Use when the user is writing or tuning prompts for a reasoning or smart model.

Guide to writing stable prompts for instant/fast models (Gemini Flash, GPT-4o Mini, Haiku). Use when the user is writing or tuning prompts for a fast or cheap model.

Build AI-IDE plugin MCP elements - stdio JSON-RPC servers, tool schemas, host wiring for Claude Code/Codex, event-name mapping, and validation. Use when adding an MCP server to a plugin.

Design AI-IDE plugin marketplaces - requirements, host-specific payloads, local dogfood, release sync, and validation. Use when the user wants to create or publish a plugin marketplace.