Loading...
Loading...
Found 720 Skills
Execute a lightweight ad-hoc task (debugging, documentation, small adjustments) without the full change lifecycle. Assesses spec impact afterward.
Use this skill to turn a raw user request into a structured, model-agnostic task brief before execution, and — when the brief survives confirmation — to be the sole entry point that creates a task directory at `.agents/tasks/<task-id>/`. Invoke whenever the request is complex, multi-step, cross-domain, ambiguous, or will be handed off to another model or agent. Also trigger when the user says things like 'help me figure out what I need', 'I'm not sure how to ask this', 'I want to do X but I don't know where to start', 'take this and make it clearer', or when the task mixes multiple goals or domains. Do NOT trigger for simple one-line requests with clear intent (e.g., 'fix the typo on line 42', 'rename this variable').
Validate cross-artifact consistency across spec.md, plan.md, and tasks.md (read-only)
Electric neon glow effects with high-contrast color pairings for bold, attention-grabbing interfaces.
Official Glue IDL guide for agents. Use when writing, explaining, validating, configuring, or generating code from Glue files into TypeScript, Python, Rust, Go, OpenAPI, JSON Schema, or Protobuf.
Nature figure preparation: resolution (300+ DPI), formats (AI/EPS/TIFF), RGB color, Helvetica/Arial fonts, lowercase panel labels, image integrity requirements.
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.
Documentation standards for changelogs, feature specs, and module documentation
Research, discuss, and write specs. Use this when creating or refining specs.
Use when you need to generate "page list → function points → business processes → business rules" with evidence from frontend code, and the project has non-unique routing entries, complex dynamic routes/permissions/backend menus, and the team is prone to making assumptions or missing evidence chains.
Эксперт по OpenAPI документации. Используй для создания Swagger спецификаций, API schemas и автогенерации документации.
Proxy2.0 数据库设计与操作规范：表设计命名、字段类型、索引规则、DO 对象、Mapper 接口、 SQL 安全、性能优化、MyBatis Plus 使用。Use when: (1) Creating database tables or SQL, (2) Writing DO classes, (3) Creating Mapper interfaces, (4) Reviewing database code, (5) Optimizing queries, (6) Working with MyBatis Plus.