Loading...
Loading...
Found 183 Skills
Provides general guidelines for using Intlayer in any project. Use when the user asks to "get started with Intlayer", "declare content files", or understand the "project structure" for internationalization.
Documents the opencode-kanban CLI contract and provides correct command patterns for task/category operations.
Trade decision audit trail and statistics
Saves, retrieves, and searches structured context (reasoning, decisions, trade-offs) behind AI-generated code, linked to git commits. Use when the developer says "save this session with GitWhy", asks about past context or decisions, or wants to push context to a PR. Also use after significant implementation work, debugging sessions, or architecture decisions.
List and run Glean platform tools. Use when discovering available platform tools or executing them programmatically.
Internal command support for dynamic Rust crate skill management. Use only when explicitly invoked by /sync-crate-skills, /clean-crate-skills, or /update-crate-skill.
contract-cli 开放平台共享约定技能：在 `contract` 和 `mdm` 模块间做选择，并遵守 `contract/v1/mcp` user-only 限制、`--input-file` 请求体输入、输出格式和 profile 选择规则。当用户要操作开放平台 CLI 但尚未明确命令模块时触发。
Core Catalyst project setup — directory structure, environments, CLI commands, and all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, Org ID). Trigger on 'start a Catalyst project', 'what is .catalystrc', 'where do I find my Table ID', 'difference between Development and Production', or any Catalyst ID or CLI question.
プロジェクトをHarness仕様に初期化。開発の準備体操はこちらで。Use when user mentions '/harness-init', new project setup, launch a project, or introduce harness to existing project. Do NOT load for: implementation, reviews, or planning.
Ground responses in paper excerpts with citations. Use when user wants cited claims, quotes, or needs to avoid hallucination about paper content.
Manage Linear issues, projects, and teams
Provide Ludus CLI command guidance, flags, and workflows for range lifecycle, template management, testing mode, snapshots, users/groups, and diagnostics. Use when users ask how to run, interpret, or troubleshoot any `ludus` command.