Results for “ar-previews”

Use for Site Building work when Codex should design content types, editorial workflows, previews, localization, permissions, and migration-safe CMS models.

Use this skill for WebXR, AR previews, model-viewer, mobile sensors, permissions, fallback UX. Trigger when the task involves 3d web work related to XR AR Web Experiences, production implementation, audits, debugging, strategy, or validation.

Designing and evaluating AI/ML systems: prompt engineering, RAG design, LLM application patterns, AI safety, evaluation frameworks, MLOps, cost optimization. Use for AI pipelines or eval harnesses.

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

Agent skill for swarm-pr - invoke with $agent-swarm-pr

Runs independent AI CLI reviewers over phase plans and merges their feedback into a REVIEWS.md file.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Agent skill for pr-manager - invoke with $agent-pr-manager

针对 Modular RAG MCP Server 项目的模拟技术面试 Agent。读取用户简历（可选），围绕三个方向进行最多 3 轮深度追问，结束后生成并持久化面试报告（含参考答案、包装识别点评、评分）。Use when user says '模拟面试', '面试练习', '帮我面试', 'mock interview', 'interview practice', '面试', '考我', '开始面试', or wants to practice interviewing about this project.

Designing red team attack scenarios, threat models, MITRE ATT&CK/OWASP application, Purple Team exercises, and AI/LLM red teaming. Use when adversarial security validation is needed.

Two-party working posture — user as director, agent as executor. Every fork, tradeoff, and taste choice is surfaced via batched AskUserQuestion with structural framing, a recommended default, and concrete previews when comparison is visual, so the human steers direction while the agent handles implementation. Eliminates the review-bottleneck (no giant diff to approve at the end — review is distributed across picks) and prevents codebase-understanding debt (the user remembers the architecture because they picked it). Use whenever the user invokes /duet, or says "work with me", "ask before", "check with me", "I want to decide", "don't assume", "human-in-the-loop", "co-author", "pair with me", "duet", or whenever a task clearly involves aesthetic, architectural, or irreversible strategic decisions — even without those exact words. Pair with the Duet output style to minimize cognitive load between picks.