Loading...
Loading...
Found 1,645 Skills
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos). Use when the user wants to save, organize, sync, deduplicate, or search across their knowledge systems.
Initialize a RootSpec project — create the rootspec/ directory, copy framework files, detect or create prerequisites. Use this when a user wants to start using RootSpec in a project, whether it's greenfield or has existing code.
Document codebase as-is with research directory for historical context
Alibaba Cloud APIG Migration Skill. Migrate Kubernetes nginx Ingress resources to Alibaba Cloud API Gateway (APIG, ingressClass: apig). Users provide Ingress YAML (paste, file, or directory) — no cluster access required for analysis. Covers annotation compatibility classification, Higress native mapping, built-in plugin selection, custom WasmPlugin development, migrated Ingress YAML generation, and migration report with deployment guide. Triggers: "nginx ingress migration", "APIG compatibility", "gateway migration", "ingress-nginx to APIG", "nginx迁移", "网关迁移", "Ingress兼容性分析", "APIG迁移", "迁移评估", "annotation兼容性", "WasmPlugin开发".
Sistema de planificación basado en archivos estilo Manus para organizar y rastrear el progreso de tareas complejas. Crea task_plan.md, findings.md y progress.md. Cuando el usuario solicita planificación, desglose u organización de proyectos multipaso, tareas de investigación o trabajos que requieren más de 5 llamadas a herramientas. Soporta recuperación automática de sesión tras /clear. Palabras clave: planificación de tareas, planificación de proyecto, crear plan de trabajo, analizar tareas, organizar proyecto, seguimiento de progreso, planificación multipaso, ayúdame a planificar, desglosar proyecto
Sync user-level AI configs (~/.claude/, ~/.codex/) with the dotfiles/ directory. Use when dotfiles drift, after sessions that change permissions/hooks, on new machines, or when the user says "sync", "pull dotfiles", "push configs".
Use the open-source free `coverlet` toolchain for .NET code coverage. Use when a repo needs line and branch coverage, collector versus MSBuild driver selection, or CI-safe coverage commands.
Scan C# source files for hard-to-test static dependencies — DateTime.Now/UtcNow, File.*, Directory.*, Environment.*, HttpClient, Console.*, Process.*, and other untestable statics. Produces a ranked report of static call sites by frequency. USE FOR: find untestable statics, scan for static dependencies, testability audit, identify hard-to-mock code, find DateTime.Now usage, detect static coupling, testability report, static analysis for testability. DO NOT USE FOR: generating wrappers (use generate-testability-wrappers), migrating code (use migrate-static-to-wrapper), general code review, or finding statics that are already behind abstractions.
Apply governance theory to analyze multi-level, network, and collaborative governance arrangements beyond traditional government. Use this skill when the user needs to evaluate public-private partnerships, analyze multi-stakeholder governance structures, compare governance models across sectors, or assess institutional arrangements for collective decision-making — even if they say 'who governs this', 'public-private collaboration', or 'how are decisions made across organizations'.
Draft or update architecture documents under `easysdd/architecture/` — describe what a subsystem/module looks like currently, how it is divided, and how external interfaces operate, to provide pre-positioning input for subsequent feature-design. Information sources include code + user materials (oral accounts, scattered documents, compound deposits, existing decisions), and the output can be reverse-validated by anchoring to specific `file:line`. Two modes: new (draft a new architecture document from scratch), update (refresh an existing document based on the latest code status and new user materials). Single-target rule — only modify one document at a time. Trigger scenarios: user says "fill in an architecture doc", "draft an architecture document", "update the architecture directory", "write down the structure of this module", or when it is found that "something that should be in the architecture is missing" during the feature-design / feature-acceptance phase.
Phase 2 of the issue process — Read the issue report + read the code, identify the true root cause and assess the repair risk, and finally provide the user with 2-3 repair plan options for them to decide. This phase is **not about starting to modify code** — after analysis, show the conclusion to the user first, and only proceed to Phase 3 after the user confirms the plan. The prerequisite dependency easysdd-issue-report has been completed. Trigger scenarios: The user says "analyze this bug", "find the root cause", "locate the issue", and the {slug}-report.md already exists in the issue directory.
Phase 2 of the issue process — Read the issue report + read the code, identify the true root cause and assess repair risks, and finally provide users with 2-3 repair solution options for them to decide. **Do NOT start modifying code in this phase** — present the conclusions to the user after analysis, and only proceed to Phase 3 after the user confirms the solution. Prerequisite: cs-issue-report has been completed. Trigger scenarios: The user says "Analyze this bug", "Find the root cause", "Locate the issue", and {slug}-report.md already exists in the issue directory.