Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only frontend state-management skill with no code execution, hidden data access, or persistence behavior.
Install this if you want Chinese-oriented guidance for complex frontend state architecture. Be aware that it declares an opus model preference and may be invoked for broad state-design discussions, but the package itself is documentation-only and does not run code or access data.
The activation guidance is broad enough to trigger on ordinary frontend architecture discussions, not just clear requests for this specialized skill. That can cause unnecessary invocation, irrelevant guidance, or context bleed from adjacent conversations, though it does not by itself enable code execution or privilege escalation.
The description says to use the skill when terms like “状态管理”, “store 设计”, or “state design” appear. These phrases are broad and common in frontend discussions, and the file does not provide explicit boundaries or negative examples clarifying when the skill should not activate.
Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
---
name: state-architecture
description: Designs scalable state management architecture for complex frontend apps. Covers store slicing, server vs client state separation, optimistic updates, cross-tab sync, and state machine patterns. Use when 状态管理, store 设计, Zustand, Redux, 状态架构, 乐观更新, 状态机, or state design.
model: opus
---
# 状态管理架构（State Architecture）
Nearly all instructional content, headings, trigger examples, and output template are written in Chinese, with no statement that the user may choose another language. This can violate language/locale policy when a skill implicitly constrains responses to a specific language without opt-in.
The tagline and description are entirely in Chinese, which imposes a specific language on users without any opt-in or indication that the skill is intentionally limited to a Chinese-speaking audience. Under the policy, language-specific presentation should either offer user choice or clearly justify the locale restriction.
The natural-language instructions and usage guidance are written in Chinese, which implicitly fixes the interaction language without indicating user opt-in or a documented regional requirement. Under the stated policy, language constraints should either be optional for the user or clearly justified.