Explorar skills

AWT é uma skill de teste web E2E com IA, atuando como 'olhos e mãos' para ferramentas de codificação de IA. Ela suporta cenários YAML declarativos, execução Playwright, correspondência visual e detecção automática de plataforma.

Esta skill oferece um fluxo de trabalho para desenvolvimento de plugins WordPress, abrangendo arquitetura de plugins, hooks, interfaces de administração, REST API, melhores práticas de segurança e recursos do WordPress 7.0 como Colaboração em Tempo Real, Conectores de IA, Abilities API, DataViews e blocos somente PHP.

百度文库智能PPT个人版 — 一句话自动生成高质量 PPT，支持多种风格、场景和配色。 TRIGGER: 用户提及"生成PPT/做PPT/制作PPT/AI PPT/aippt/幻灯片/演示文稿"时触发。 DO NOT TRIGGER: 非 PPT 相关操作，文件管理操作，网盘上传下载等操作。

百度网盘(Baidu Drive)文件管理 — 上传、下载、转存、分享、搜索、移动、复制、重命名、创建文件夹。 同时支持 Agent 记忆备份/恢复（kimiclaw/maxclaw/qclaw/openclaw）。 TRIGGER: 用户提及"百度网盘/bdpan/网盘/云盘/baidu drive/Baidu Drive"并涉及文件操作； 或用户提及"备份记忆"、"恢复记忆"、"查看记忆备份"等记忆相关操作。 DO NOT TRIGGER: 非文件存储操作，或使用其他云盘服务时；本地记忆整理/清理操作；PPT 生成操作（已独立为 baidu-wenku-aippt skill）。

Use when an existing task in an active Piyaz project carries scope larger than 13 points worth of work (composer's research brief raised the `oversize-task` flag, or the user explicitly says "split this task", "decompose RZE-42", "this task is too big", "break <taskRef> into smaller pieces"). Composer dispatches this from its oversize handler. Splits the parent into 2 to N child tasks, rewires eve

Use when the user has a net-new software project idea that needs shaping into a brief before tasks can be created. Triggers: "I want to build...", "I'm thinking about an app for...", "let's plan a project", vague or exploratory phrasing, ambiguous scope. Do not use when an existing repo is present (route to onboarding), a Piyaz project already exists with a description, or the user has a complete

Use when the current repo has existing code but no Piyaz project that matches it, and the user wants to adopt Piyaz on day N. Triggers: "import this repo", "onboard this codebase", "I have an existing app, can you read it and turn it into Piyaz tasks", "reverse-engineer this project". Do not use when no code exists yet (route to brainstorm), a Piyaz project for this repo already exists (route to m

Use when an existing task in an active Piyaz project carries scope larger than 13 points worth of work (composer's research brief raised the `oversize-task` flag, or the user explicitly says "split this task", "decompose RZE-42", "this task is too big", "break <taskRef> into smaller pieces"). Composer dispatches this from its oversize handler. Splits the parent into 2 to N child tasks, rewires eve

Treinamento de prompts ciente do estágio, melhoria de prompts, análise retrospectiva, feedback sobre hábitos de prompting e relatórios locais sobre a qualidade dos prompts para agentes de codificação de IA como Claude Code ou Codex.

Explicit doorway to the Piyaz decompose-feature subagent. Use only when the user types /piyaz:decompose-feature directly. For natural-language requests to add a new feature or capability cluster to an active project, the /piyaz skill or the assistant dispatches the decompose-feature agent via the Task tool. Do not invoke this skill for that path.

Use when the user explicitly wants a deep CTO-mode review of a Piyaz project. Triggers: "strategic review", "audit the project", "rebalance the graph", "what's the health of this project", "deep dive on the dependency graph", "I want a thorough navigation session", "prune orphans", "connect missing edges", "audit blockers", "consolidate categories or tags", "graph health check". Do not use for rou

Use when the user explicitly wants a deep CTO-mode review of a Piyaz project. Triggers: "strategic review", "audit the project", "rebalance the graph", "what's the health of this project", "deep dive on the dependency graph", "I want a thorough navigation session", "prune orphans", "connect missing edges", "audit blockers", "consolidate categories or tags", "graph health check". Do not use for rou