Loading...
Loading...
Found 125 Skills
Set up and manage a Memory Bank system for cross-session context continuity across AI coding agents. Use when the user mentions 'memory bank' with any action intent — setup, install, initialize, init, update, refresh, sync, status, check, read, show, review, display, or equivalents in any language (e.g. Turkish: kur, kurulum, güncelle, durumu, oku; German: einrichten, aktualisieren; Spanish: configurar, actualizar; French: installer, mettre à jour). Supports Claude Code, Cursor, Windsurf, Cline, GitHub Copilot, Roo Code, Aider, Antigravity, and OpenAI Codex.
Manage AI coding agents on a visual Kanban board. Run parallel agents through a To Do→In Progress→Review→Done flow with automatic git worktree isolation and GitHub PR creation.
Install the Chief into the current project. Uses setup.sh as the primary method, then verifies and fixes manually if needed. Use when the user wants to set up the framework (e.g. "/chief-install" or "/chief-install canary").
Harness engineering for AI coding agents — five subsystems, memory persistence, session continuity, verification workflows, scope control, lifecycle management.
Manage durable working-session memory for coding agents. Use when a user asks to preserve or recover agent context across disconnects, VS Code restarts, long-running work, handoffs, or any session where important state should be written periodically under the repo's session directory.
Best Practice Advisor for AGENTS.md / CLAUDE.md. It is used when users ask about the format, structure, and best practices of agents markdown, AGENTS.md, CLAUDE.md, Claude Code memory, and AI coding agent instruction files; it also supports reviewing, diagnosing, rewriting, optimizing, or creating agent instruction files such as AGENTS.md, CLAUDE.md, CLAUDE.local.md, and .claude/rules from scratch. It is not suitable for general README writing unless the goal is to provide project context for AI coding agents.
Suggest agent rules analyzing the session history and the current repository.
Professional prompt engineering, context engineering, and AI agent orchestration for coding agents (Claude Code, Codex, Cursor, Gemini CLI). Use when designing CLAUDE.md/AGENTS.md files, writing skills, planning multi-agent pipelines, optimizing token usage, managing session handoffs, or structuring any prompt for maximum agent performance. Do NOT use for general coding tasks or code review.
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
Composable development workflow system. Phases define reusable steps; paradigms compose them into ordered sequences. Four paradigms cover greenfield, enhancement, bugfix, and addition task types.
Use when working with the `arise` CLI to check readiness, generate review-first plans from strict PRDs or GitHub issues, inspect `.arise/` artifacts, execute reviewed plans, or recover interrupted and integration-blocked runs.
This skill bridges the current host coding agent (Claude Code, Codex, or Gemini CLI) to IM platforms (Telegram, Discord, Feishu/Lark, QQ, or WeChat). Use for: setting up, starting, stopping, or diagnosing the IM bridge daemon; forwarding agent replies to a messaging app. Trigger on: "link-to-im", "start bridge", "stop bridge", "bridge status", "消息推送", "消息转发", "桥接", "连上飞书", "手机上看claude", "启动后台服务", "诊断", "查看日志", "启动桥接", "停止桥接", "配置", or any mention of IM bridge management. Subcommands: setup, start, stop, status, logs, reconfigure, doctor. Do NOT use for: building standalone bots, webhook integrations, or coding with IM platform SDKs — those are regular programming tasks.