nextclaw

当设计、修改或评估前端交互体验、操作按钮、hover/focus/active/disabled 状态、tooltip、popover、菜单、键盘可达性、紧凑模式下的操作可理解性，或用户指出“这个操作不知道是什么”“体验不统一”“交互规范”时使用。

当用户要求目录结构治理概况、整体问题概况、结构热点、目录问题量化、下一步治理优先级、长期结构债务地图，或用“概况”“热点”“整体情况”指代当前 module-structure/app-l1/app-l2/app-l3 治理状态时使用。用于输出可复现的量化概览，而不是直接开始重构。

Use when editing AGENTS.md, commands/commands.md, Rulebook or Project Rulebook content, project AI instructions, or deciding whether a rule belongs in AGENTS.md, a skill, or ordinary docs. Also use when the user says to remember a rule/principle/norm, or for /config-meta, /check-meta, /new-rule, and AGENTS token optimization.

用作 NextClaw 标准开发流程/交付流程的总 owner；当用户要求规范开发流程、实现、修复、重构、方案到实现、验证、提交、收尾、完成工作，或需要阶段化节奏与主动汇报时使用。

当用户要求技术方案、方案设计、设计文档、架构方案、实现前设计、交互/前端/后端方案，或开发流程进入“先设计再实现”的阶段时使用。用于产出可执行的方案设计合同，覆盖现状证据、owner、数据流、目录组织、可维护性、非目标、风险与验证标准；本 skill 是开发流程中的方案设计专项，不是完整开发 workflow owner。

用于定义或重构基于 feature 的代码组织架构，尤其适用于判断当前作用域应保持单 feature root、何时引入 features/ 聚合层、何时拆稳定子 feature、何时严格限制 shared 目录、如何处理可被其他 workspace 源码依赖的 package/SDK/shared library 的导入 alias，以及如何分别处理包内部结构与仓库级组织边界。

Use when running /validate, choosing validation commands after changes, closing code work, checking TypeScript/build/lint requirements, doing bugfix resolution verification, smoke testing, runtime startup/status log verification, maintainability guard/review, governance ratchets, or release validation.

Use when implementing, refactoring, or designing source-level contracts in this repository, especially if a task touches frontend i18n/user-facing copy, frontend base/display components, tool schemas, API/protocol parameters, shared contracts, compatibility paths, fallback-heavy logic, duplicate branches, weak abstractions, unclear file placement, ad-hoc helpers, or patch-style fixes that would turn into garbage code.

Create or update complete NextClaw lightweight apps, deciding whether the user needs a Panel App, a Service App, or a combined Panel + Service App. Use for NextClaw applets, small tools, dashboards, local file tools, AI-assisted UI tools, apps that may combine right-side UI with backend actions, or questions about what NextClaw/Panel apps can do and which app APIs/capabilities they can use.

Create or update the Panel App UI part of a NextClaw lightweight app. Use after nextclaw-app-creator selects Panel-only or Panel + Service, or when the user explicitly asks for a right-side Panel App UI, folder-based static panel, Service Actions UI, Agent-powered Panel App, React/Vite/Tailwind Panel App, or asks what a Panel App can do and which injected APIs/capabilities it can use.

当用户要发布已经提交的 NPM 包，但当前工作区还有未完成、半吊子、staged/unstaged WIP，或用户明确要求“不要把未完成改动发上去”“隔离发布”“全部发布”“发布产物再合回 master”时使用。覆盖 git worktree 隔离发布、NPM stable/beta 全量或窄发布、保护当前 WIP、registry 验证、release commit/tag 回流本地目标分支。

Use when publishing NextClaw NPM packages or NPM runtime update channels, including beta/stable dist-tags, nextclaw@beta validation, runtime bundle manifests, packaged update public keys, and npm registry closure checks.

当用户希望把 Codex 或 Codex CLI/SDK 作为 NextClaw 正式会话类型接入，尤其是通过 narp-stdio 配置、安装、修复、doctor 或真实冒烟时使用。

当用户要求前端代码优化、前端可维护性治理、组件拆分、逻辑拆分、视图逻辑解耦、MVP / presenter-manager-store 落地、prop 透传改造、页面/组件代码爆炸 review、React 组件职责收敛、前端重构优先级排序，或指出某个前端 Page/Component 可维护性爆炸时使用。用于把前端优化任务先诊断、排序，再按非新增功能净减约束实施。

在本仓库完成代码、脚本、测试或影响运行链路的配置改动后使用，用于自检可维护性漂移，重点发现超长文件和持续膨胀的文件。

当设计或重构主干/分支架构、kernel、desktop main、runtime host、presenter-manager-store、manager/store/presenter、生命周期装配、owner 依赖、贡献点 contribution，或用户指出最小传参、上层代读、factory/create/registry 过度抽象、稳定业务依赖被过度解耦、prop 透传或链路过长时使用。

当写代码前、给技术方案前，或讨论、审查、重构代码审美、代码是否干净、是否丑、是否优雅、是否简单优先、是否简单第一、代码/组件/函数/文件/模块该不该拆分、拆分价值与损失、是否过度防卫、是否过度抽象、是否像补丁堆叠，或用户明确要求提升代码审美、写出美丽代码时使用。

当把 Codex、Claude Code、Hermes 或其他外部 agent runtime 通过 NARP stdio 接入 NextClaw，或讨论 narp-stdio runtime entries、stdio launcher、agent-side wrapper、迁移旧 agent-runtime 插件时使用。

当设计或重构前端 MVP / presenter-manager-store 架构、Zustand store / persist、前端状态归属、view-logic 解耦、页面刷新状态恢复、localStorage/sessionStorage 替代、减少 prop drilling、业务组件内聚、自包含业务容器、业务编排层、多组件状态/动作协调、复杂 React hook/component 状态机、streaming/data-flow 协调或 RxJS 评估时使用。

当用户要求先研究代码、排查代码、看清楚现状、判断某个组件/函数/manager/文件是什么性质、该不该改、该怎么改，或用户指出“不要我说一下你才注意一下”“主动发现所有问题”“顺着代码查完整”时使用。该 skill 只规定代码调查方法，不承载具体架构、拆分、命名、MVP、UI 或 owner 规范；具体判断必须转交对应专项 skill。

当讨论或修改架构、模块职责、owner、生命周期、对象边界、状态归属、helper/service/class 拆分、抽象力度、重构方案、复杂性能瓶颈、方案对比、决策过程，或用户要求“简单优先”“简单第一”“编程原则”“最佳实践”“底层思想”“不要张口就来”“深入分析”时使用。用于先深挖用户真实意图与约束，再用 GRASP、SOLID、Tell Don't Ask、Law of Demeter、封装、高内聚低耦合等经典原则校准设计，避免空心 owner、假注入、乱兼容、重复职责和过度抽象。

Self-manage NextClaw runtime via CLI guide. For install/start/status/doctor/service/channels/config/agents/cron/remote/update operations, and for discovering local HTTP/API/webhook addresses.

Create or update the Service App backend action part of a NextClaw lightweight app. Use after nextclaw-app-creator selects Service-only or Panel + Service, or when the user explicitly asks for workspace service-apps, MCP-compatible backend helpers, file access, external API calls, local commands, or privileged actions.

当用户要在本地验证当前源码构建出的 NextClaw 产品实例、restart/start/stop、避免跑到全局安装版 nextclaw、需要可复用本地安装态/构建态验证命令或 smoke harness 时使用。

自动检测和改善代码库的文件组织结构，确保代码具有清晰的模块化和分层架构。使用模块化分割（按功能领域）和分层抽象（按职责分层）的双重策略，在每次代码修改后自动运行检测，或在目录文件数超过阈值时触发。

Use when deciding, creating, or updating docs/logs iteration records; when the user asks to commit/提交/收尾 after changes; when changes touch code, scripts, tests, runtime config, large non-code governance/docs rewrites, NPM release records, root-cause fix notes, red-zone touch records, work notes, or goal-progress anchors.

当用户要求沉淀、整理、归档、维护或分流项目想法、产品思考、讨论记录、PRD、设计、计划、路线图、TODO、docs/thoughts、docs/designs、docs/plans 或 docs/logs 迭代记录时使用。用于判断内容应进入 docs/TODO.md、docs/thoughts、docs/designs、docs/plans、docs/prd、docs/ROADMAP.md 还是 docs/logs，并维护它们之间的升级关系。

Enforce Angular/NestJS-style file naming (kebab-case plus role suffixes like controller/manager/store/service). Use when users ask for naming conventions, file renames, modular refactors, or naming governance in TypeScript/JavaScript repositories.

当修改前端样式、基础组件、展示组件、响应式布局、紧凑模式、Tailwind/CSS/container query、组件视觉状态，或用户质疑样式是否内聚、可移植、自洽时使用；尤其适用于 reusable UI package、shared component、跨宿主复用组件的样式 owner 判断。

当用户要求提交、收尾、统一 NPM 发布、GitHub release、changelog、release notes、变更汇总，或担心并行会话导致发布内容靠记忆整理时使用。适用于需要进入用户可见发布说明的 NextClaw workspace 包变更和 Changesets 聚合。

Use the local browser-connector CLI to inspect and operate the user's current Chrome tabs through the Browser Connector extension and Native Host. Use when the user asks to list open browser pages, read a current page, capture a screenshot, or perform controlled browser interactions from NextClaw.

在本仓库将本地 skill 发布或更新到 NextClaw marketplace 时使用。适用于新增 marketplace skill、从 SkillHub 继承 skill 到本项目 marketplace、补齐 marketplace.json 双语元数据、执行发布后远端校验与安装冒烟。

Use when code changes are finished and a second-pass maintainability review is needed beyond lint or guard output, especially to judge deletion opportunities, simplification chances, abstraction fit, or whether non-feature changes added unjustified code

Create or update an engineering-style NextClaw Panel App using pnpm, Vite, React, TypeScript, and Tailwind CSS, then build it into a static .panel directory. Use when the user asks for a modern frontend stack, React Panel App, Vite app, Tailwind UI, or reusable/buildable Panel App project, and when the requested Panel App has complex UI/state, AI chat or Agent Run workflows, charts, filters, forms, or needs TypeScript access to App Client types.

Use the local aigen CLI to generate images through configured providers such as OpenRouter or OpenAI. Use when the user asks to create, generate, or render images and wants files produced locally through an external CLI.

当用户要求“发布 beta”“统一 beta 发版”“发一个新的 NPM beta 版本”“一键 beta release”或希望直接复用 NextClaw 的 beta 发布闭环时使用。适用于 nextclaw 及其相关 workspace 包的 beta 发布，也适用于需要同时闭合 npm registry 与 NPM runtime update channel 的场景。

当用户要为 NextClaw 写产品博客、短文、官网文章、宣传叙事、功能优势阐述、发布故事、配图建议，或要求把某个产品点讲清楚、写得更有传播力时使用。用于把产品愿景、真实证据、用户痛点、差异化判断和可发布文案收敛成可复用写作流程。

Use when building, verifying, or releasing NextClaw desktop installers, DMGs, update bundles, update manifests, or one-command desktop beta/stable release automation. Enforces the packaged update public key contract, the required verification commands, and the rule that raw electron-builder output is not enough.

Use when a task involves fallbacks, backward compatibility, graceful degradation, environment-specific rescue paths, legacy retention, or "just in case" compatibility logic. Prefer explicit, clear, predictable behavior over hidden rescue paths, and require strict necessity plus exit conditions for any compatibility path.

Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.