langgenius

Implement internationalization with Lingui in React and JavaScript applications. Use when adding i18n, translating UI, working with Trans/useLingui/Plural, extracting messages, compiling catalogs, or when the user mentions Lingui, internationalization, i18n,…

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads,…

Fold new dev-log entries back into docs/dev-file volumes (the current-truth architecture docs), then bump each volume's 最后核对 stamp. Use when the user asks to distill/reconcile dev-file, run the weekly docs pass, or close out a workstream. Processes only the…

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and…

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Closes the audit→edit→verify loop. Runs an accessibility audit, applies fixes to source code, and re-audits to confirm. Prefers live-DOM auditing via a browser MCP when available; falls back to static HTML audit when not.

Build compact, distinctive landing pages and product skeletons without repeating one visual template. Use for package demos, developer tools, documentation intros, focused product pages, and micro-SaaS sites that should feel small, polished, tactile,…

Harden an interface against real-world inputs: extreme text lengths, emoji/RTL, huge lists, empty states, network failures, API errors, i18n expansion, and concurrent operations. Use when making UI production-ready or reviewing edge-case coverage.

Rule pack for Dify user-guide pages — en/{cloud,self-host}/use-dify/, en/develop-plugin/, and en/self-host/deploy/. Carries the reader personas (master copy), audience-voice rules, dual-copy discipline, and env-var presentation patterns. Loaded by…

Post-writing verification from the reader's perspective. Invoke after completing any documentation task to simulate a real user reading the document for the first time.

The entry point for writing or revising ANY documentation in this repo — user guides, deployment pages, plugin-dev pages, API specs, the env-var reference, CLI pages. Resolves the work type and doc type, then runs the eight-stage pipeline (intake → research →…

Check formatting compliance in changed documentation against writing-guides/formatting-guide.md and tools/translate/formatting-{zh,ja}.md. Routes by path: en/ files get the English linter and rules; zh/ and ja/ files get the CJK linter and rules. Use after…

Audit terminology consistency across documentation against the codebase UI labels and the glossary — in prose and in the UI strings shown in screenshots. Covers full files, not just diffs; excludes env var docs. Use after finalizing a draft, or when the user…

Rule pack for the environment variable reference — en/self-host/deploy/configuration/environments.mdx. Carries the tracing procedure, description rules, verifier, and document structure. Loaded by dify-docs-write; not an entry point. Its release-sync diff is…

Rule pack for the Service API specs ({en,zh,ja}/api-reference/openapi_service.json): spec conventions, app-type scoping, code-verification rules, and the audit machinery. Writing and editing run under dify-docs-write; the standalone audit of an existing spec…

Use when preparing documentation updates for a Dify release — either comparing two version references (e.g., v1.13.2 and v1.13.3) or prepping ahead of an unreleased version in multiple passes. Covers API reference, help documentation, environment variable…

Review mosoo changes for project-rule, architecture, type-safety, data-scope, generated-source, observability, dependency, and verification violations. Use before committing, after completing a feature, or when reviewing another agent's diff, especially for…

Avoid unnecessary React effects in mosoo while using React useEffect directly for real external synchronization. Use when writing or reviewing React components, refactoring effect-driven derived state or event relays, handling subscriptions and browser APIs,…

Build or review Cloudflare Sandbox SDK integrations using repository evidence and current official documentation. Use for secure code execution, agent runtimes, container-backed tools, Wrangler bindings, Dockerfiles, preview services, or Sandbox lifecycle…

Better Auth server/client setup: `auth.ts`, generated schema, DB adapters, sessions, cookies, env vars, and plugins. Use when mentioning Better Auth, betterauth, auth handlers, OAuth, email/password, or session configuration.

Scaffold Better Auth in TypeScript apps: framework handlers, DB adapters, OAuth, email/password, and auth UI. Use when adding login, sign-up, session handling, or Better Auth plugins.

Better Auth email/password setup: verification emails, password reset, policies, hashing, and credential sign-in. Use when adding or hardening email/password login, sign-up, reset, or verification flows.

Better Auth security hardening: rate limits, secrets, CSRF, trusted origins, cookies, sessions, OAuth tokens, and audit logging. Use when reviewing auth security, brute-force protection, token handling, or deployment safety.

Readability-first TypeScript and TSX style guardrails for strict codebases. Use when reviewing or editing TypeScript, defining shared contracts, creating lintable style rules, or deciding between type vs interface, null vs undefined, and…

Act as the WTA green-impl. Use when the user is claiming a contract-sealed task, pulling its worktree, implementing the task, running checks, and submitting for review. Green-impl is the only role that edits product source code; it must stay inside the task…

Act as the WTA green-lead. Use when the user is decomposing a sealed feature intent into tasks, creating a task draft, or signing a task interface contract. Green-lead owns decomposition and the implementation surface; it does not write acceptance contracts…

Install the WTA Rust CLI from source. Clone the public repository, build with cargo, and place the wta binary on PATH. Use when the user wants to start using WTA but does not yet have the wta binary installed, or wants to upgrade to the latest commit on main.

Act as the WTA orchestrator. Use when the user is bootstrapping a WTA project, publishing or sealing a feature intent, registering team members or release targets, closing an intent, or running a release push. The orchestrator owns intent and release; it does…

Operate WTA, the role-gated workflow controller for teams collaborating with humans and AI coding agents. Use when the user wants to set up a new WTA project, configure the SSH/VPS pair, register an identity, or follow the Blue-Green role lifecycle from…

Act as the WTA blue-harness reviewer. Use when the user is reviewing a Delivered task by pulling a reviewer worktree, running the acceptance contract's Required Checks, and recording a verdict. Blue-harness is independent of green-impl; the same person should…

Act as the WTA blue-lead. Use when the user is signing a task acceptance contract, sealing a green-lead decomposition, or merging a Green-reviewed task into product main. Blue-lead is the gate that protects product main; it does not implement code and does…

Use only when the user explicitly requests a review or audit of frontend code under `web/` or `packages/dify-ui/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, or…

Use when writing or changing Vitest or React Testing Library tests under `web/` or `packages/dify-ui/`, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy. Do not use for frontend code-review-only…

Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data flow, effects, or interaction ownership. Do not use for review-only requests, test-only work, copy-only…

Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, frontend code, or backend…

Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags, locators, and assertions. Do not use for Vitest, React Testing Library, backend tests, or generic…

Summarize user input for Agent Builder E2E coverage.

Layer 3 raw HTTP: any endpoint not yet covered by a flow or resource verb.

Manage Droploft documents (drops): upload, list, get, content, share, publish, delete.

Lofts: types, switching, listing, member operations.

Droploft v2 CLI: authentication, configuration, profiles, and patterns shared across all domains.

Background task runs — list, inspect, retry. Use this to debug async failures from doc +upload, publish, etc.

Workspaces: switching, listing, members, navigation tree.

Use when operating the tokener generated CLI. Discover commands, inspect parameters, check auth state, and execute API operations safely.

Use when operating the tokener generated CLI. Discover commands, inspect parameters, check auth state, and execute API operations safely.

Validate a local Dify .difypkg file with bundled Marketplace package validators. Use when a user wants to check a downloaded or locally built plugin package before submitting a PR, including package contents, secrets, binaries, manifest/privacy, README,…

Use when a coding agent needs to work with mosoo setup, local or cloud runtime state, mosoo CLI operations, or app integration with a published mosoo Agent.