Query Google Places API (New) via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.

Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).

当用户主动汇报自己完成的具体动作、求反馈或默认求认可时使用。明说型：'我把 leetcode hot100 刷完了'/'我做完了 XX 项目'/'我读完了《XX》'/'我考了 CET-6/雅思/某证书'/'我这周投了 50 家'/'我简历改了 5 版'/'我今天面了 X 家'/'X 我终于弄完了'/'我跑通了 XXX'/'我做了 X 感觉怎么样'/'这样算不算'。隐蔽型（压低期待的汇报，用户自己在克制但实际在求认可）：'我好像把 X 搞懂了'/'我试了一下 X'/'我昨天随手做了个 X'/'我不知道这算不算什么，但我…'/'可能不算多，但我…'。边界：用户**已经做完具体动作**在汇报（区别于 coach-concern-direct 的'我够不够'担忧、coach-resume-review 的'帮我看简历'请求、coach-request-deliver 的'帮我梳理'请求）。应用本 skill：第 1 句具体认可他做了什么（不是'真棒'），第 2-3 句把动作从'作业视角'翻译到'求职/能力积累视角'给出可立刻自测的具体锚点，第 4 句根据定位结果动态生成 A/B 选择（深挖/横向/修漏洞/暂停诊断 四选二，不是固定二分）。禁止空洞鼓励、禁止直接打击、禁止无脑加码。

Here’s the updated AGENTS.md with a Doc Sync note so contributors know to check all public-facing docs together when changes happen:

Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries. Use when the user asks about GitHub issues, pull requests, workflows, or wants to interact with GitHub repositories from the command line — including tasks like check CI status, create PR, list issues, or query the GitHub API.

Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI. Use when creating or maintaining LSUIElement menubar utilities, defining Tuist targets/manifests, implementing model-client-store-view architecture, adding script-based launch flows, or validating reliable local build/run behavior without Xcode-first workflows.

Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file. Concrete actions include adding Sendable conformance, applying @MainActor annotations, resolving actor isolation warnings, fixing data race diagnostics, and migrating completion handlers to async/await.

Implement, review, or improve accessibility in iOS/macOS apps with SwiftUI and UIKit. Use when adding VoiceOver support with accessibility labels, hints, values, and traits; when grouping or reordering accessibility elements; when managing focus with @AccessibilityFocusState; when supporting Dynamic Type with @ScaledMetric; when building custom rotors or accessibility actions; when auditing a11y compliance; or when adapting UI for assistive technologies and system accessibility preferences.

Implement, review, or improve localization and internationalization in iOS/macOS apps — String Catalogs (.xcstrings), LocalizedStringKey, LocalizedStringResource, pluralization, FormatStyle for numbers/dates/measurements, right-to-left layout, Dynamic Type, and locale-aware formatting. Use when adding multi-language support, setting up String Catalogs, handling plural forms, formatting dates/numbers/currencies for different locales, testing localizations, or making UI work correctly in RTL languages like Arabic and Hebrew.

Use when onboarding developers to an unfamiliar codebase, documenting a complex architectural flow across multiple files, or creating guided walkthroughs for code reviews. Generates VSCode CodeTour JSON files with progressive disclosure — starting from high-level architecture and drilling into implementation details. Domain: Documentation, Onboarding. Level: Intermediate. Tags: code-tour, onboarding, walkthrough, documentation, progressive-disclosure, vscode.

Discover functions that block the main thread, then micro-audit each for internal optimization opportunities

Proactive code review. When the user completes a meaningful coding task or asks for a review, invoke /rrr automatically — but only if this project has opted in.

Run the proofreading protocol on project files. Checks grammar, typos, consistency, and academic writing quality. Produces a report without editing files.

Audit SpawnForge code for changes that block future multiplayer networking. Use when modifying state management, entity systems, or the command pipeline — flags non-deterministic state, client-authoritative patterns, and unsyncable mutations.

'PR creation workflow, title format, description template, and quality gates'

Audit SoulMap AI evals so datasets, assertions, source markers, and golden responses stay source-backed, failure-oriented, and hard to game.

Review an entity store PR

Mandatory core-4 reviewer with P0-P3 severity classification and specialist escalation

Serve MarkdownViewer-web-pro locally for testing. Use when the user says /localdeploy, asks to test locally, run a local server, or preview before pushing.

'Use when staging and committing code changes with conventional commit messages'

Security and compliance for MCPAtlas: threat model, RBAC, audit, supply chain, input validation, plugin sandbox. Use when implementing auth, hardening, or reviewing security-sensitive code.

Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.

Pipeline orchestrator that works Ada-labelled Planka cards through the full dev pipeline (story → plan → code → review). Use for autonomous development sessions.

Documentation creation and modification rules (docs/en/developer/ design documents, abstraction principles, structure, docs-first workflow). Use when creating documentation, updating design documents, writing architecture docs, checking which docs must change for a code change, asking about documentation structure/design principles, or working with files in docs/en/developer/ (fallback: docs/ja/).

Reviews code for quality, security, and maintainability. Use after implementing features, completing significant work, or when user asks for code review.

Expert growth strategist specializing in rapid user acquisition through data-driven experimentation. Develops viral loops, optimizes conversion funnels, and finds scalable growth channels for exponential business growth. Use when Codex needs this specialist perspective, workflow, or review style for related tasks in the current project.

Review and rate code implementations against issue cards and ExecPlans using git diffs, AGENTS.md, and PLANS.md. Use when a user asks for an implementation review, compliance check, regression risk assessment, or to validate changes against one or more issue cards or ExecPlans.

Generate a safe, step-by-step refactor plan minimizing risk and preserving functionality.

Generate a concise hotspot briefing from the wy-hotspot-monitoring workspace state. Use this skill whenever the user asks for a hotspot digest, trend summary, recent signal review, shift report, or operator-ready briefing, especially when they want a quick readout instead of raw JSON or the full dashboard.

>

Code reviews of git changes without creating actual PR.

Unified codebase quality review: merge readiness verdict + maintainability (Clean Code) + docs-vs-code consistency. Use for code review, quality check, refactor check, outdated docs check, or merge/production readiness.

Generate pull request summaries and open GitHub PRs from the current branch’s git changes.

Focused on 7 high-impact review dimensions based on "Clean Code" principles.

Use when you need concrete UI/UX inputs (palette, typography, landing patterns, UX/a11y constraints) to drive design or review. Searchable UI/UX design intelligence (styles, palettes, typography, landing patterns, charts, UX/a11y guidelines + stack best practices) backed by CSV + a Python search script. Triggers: UIUX/uiux, UI/UX, UX design, UI design, design system, design spec, color palette, typography, layout, animation, accessibility/a11y, component styling. Actions: search, recommend, review, improve UI.

Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness.

'Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.'

Review or refactor React / Next.js code for performance and reliability using a prioritized rule library (waterfalls, bundle size, server/client data fetching, re-renders, rendering). Use when writing React components, Next.js pages (App Router), optimizing bundle size, improving performance, or doing a React/Next.js performance review.

Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan.

Creates non-technical changelogs from git commits.

You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.

>

Monitor and report on Ralph Wiggum loop progress. Provides real-time status, iteration summaries, and progress tracking via Archon state. Use to check on running or completed loops, view iteration history, and diagnose issues.

Trigger a xylem drain cycle and report what moved through the queue. Use when the user asks to run pending work, kick the daemon manually, process queued vessels, or monitor a fresh drain.

Plans the next sprint with PM analysis, multi-agent technical table, and roadmap generation. Use to plan sprints, prioritize features, convene technical tables.

배포 스크립트의 보안·안전성 리뷰를 수행한다. 롤백 절차, 장애 대응, 권한 설정을 점검한다.

Meta-level analysis of plan vs execution to identify process improvements. Analyzes divergence patterns and suggests updates to CLAUDE.md, agents, and skills.

Load this skill when writing tests, reviewing test coverage, setting up testing strategies, or ensuring code quality. Covers the testing pyramid, unit/integration/e2e test standards, naming conventions, and mandatory 90% coverage requirements.

Creates production-ready pull requests with automatically updated AGENTS.md and project docs. Use when the user asks to create a PR, make a PR, is ready to merge, has finished a feature and wants a PR, or says they're done for the day with changes to commit.