creating-skills
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
Use this when you have finished making code changes and you are ready to update the documentation based on those changes.
Specialized skill for creating and editing high-quality Kener documentation. MUST be used whenever creating or editing documentation files in the src/routes/(docs)/docs/content/ directory or updating docs.json navigation.
ๆๅฏผ็ๆ็ง็ ๆฅๅใ่กไธ่ฐ็ ใๆๆฏๅๆ็ญ้่ฆๆทฑๅบฆ็ ็ฉถ็้ฟ็ฏๆฅๅใๅฝไปปๅก็ฎๆ ๆฏๅฝขๆ็ปๆๅใๅฏๅผ็จใๅ ทๆๅๆๆทฑๅบฆ็ๆญฃๅผๆฅๅๆถไฝฟ็จๆญคๆ่ฝใ
C# and .NET coding standards for generating new code files. Use when creating new classes, methods, controls, tests, or any new C# / VB source files in this repository. Covers C# 14 / .NET 10 patterns, naming, formatting, XML docs, WinForms conventions, and performance idioms.
Instructions for adding new public APIs (properties, methods, events, delegates) to existing WinForms controls or components. Covers API issue tracking, PublicAPI file maintenance, property/event conventions, CodeDOM serialization, design-time attributes, and XML documentation.
Instructions for using GDI, GDI+ for drawing primitives, shapes and processing/rendering bitmaps and rendering Fonts. Also, tenets for adding new APIs to System.Drawing for modernization and improving drawing, imaging, and font features.
Investigate a plain-language problem description by deeply exploring the codebase, then create a structured GitHub issue with technical findings. Prequel to build-from-issue โ maps vague ideas to concrete, buildable issues. Trigger keywords - spike, investigate, explore, research issue, technical investigation, create spike, new spike, feasibility, codebase exploration.
้่ฟๅๆไปฃ็ ็ปๆไธไพ่ต๏ผ่ชๅจๆๅ็ณป็ปๆปไฝๆถๆใๆ ธๅฟ็นๆๅ่ฝๆจกๅ็ๅฎ็ฐ็ป่๏ผๅนถ็ๆไบ็ธๅ ณ่็ๅค้กต้ข Wiki ็ปๆๆๆกฃ้ใไฝไธบ้กน็ฎ็ๆถๆ็ฅ่ฏๅบๅฎๆค่ ๏ผ่ฟ่ด่ดฃๅจๆฅๅธธๅผๅไธญ่งฃ็ญ็้ฎ๏ผๅนถๅจๆถๆๅๆดๆถ่ชๅจ็ปดๆคๆๆกฃใ
Create a release PR from main to production branch. Use when the user says "ใชใชใผในPR", "productionใซPR", "ใชใชใผในๆบๅ", or wants to trigger a release.
Reviews documentation PRs and provides GitHub PR suggestions. Load when asked to review, suggest changes, or provide feedback on docs content. Covers MDX, frontmatter, style guide, components, and content accuracy.
Research a documentation topic โ locate affected files, understand the problem, identify what to change. Use when investigating an issue, a question, or a topic before writing a fix. Triggers on: "research issue 1234", "investigate what needs changing for #500", "what files are affected by #200", "where is X documented", "is our docs page about Y accurate", "look into how we document Z".
Create a guide page for a Labspace. This includes writing the markdown content for the guide, structuring it according to Docker docs conventions, and ensuring it provides clear instructions and information about the Labspace. Includes learning about the lab itself, extracting out its learning objectives, and combining all of that into a well-structured guide markdown file.
Migrate a Testcontainers guide from testcontainers.com into the Docker docs site (docs.docker.com). Converts AsciiDoc to Hugo Markdown, updates code to the latest Testcontainers API, splits into chapters with stepper navigation, verifies code compiles and tests pass, and validates against Docker docs style rules. Use when asked to migrate a testcontainers guide, add a TC guide, or port content from testcontainers.com to Docker docs.
Assemble a complete hunt blueprint by consolidating outputs from prior hunt planning skills into a single, structured plan for execution. Use this skill after system and tradecraft research, hunt focus definition, data source identification, and analytics generation have been completed. This skill is synthesis and packaging only and must not introduce new research, assumptions, or analytics.
Prepare weekly triage meeting summary for WinAppSDK Needs-Triage issues. Use when preparing for triage meetings, reviewing Needs-Triage issues, generating diff reports since last triage, summarizing new or updated issues, or creating action item recommendations. Triggers on requests involving triage preparation, Needs-Triage review, meeting summary, triage diff, or weekly issue analysis.
Meta-skill that analyzes the Trail of Bits Testing Handbook (appsec.guide) and generates Claude Code skills for security testing tools and techniques. Use when creating new skills based on handbook content.
Techniques for patching code to overcome fuzzing obstacles. Use when checksums, global state, or other barriers block fuzzer progress.
Techniques for writing effective fuzzing harnesses across languages. Use when creating new fuzz targets or improving existing harness code.
Fuzzing dictionaries guide fuzzers with domain-specific tokens. Use when fuzzing parsers, protocols, or format-specific code.
Guide for troubleshooting and configuring Maven Central publishing via Sonatype Central Portal. Use when the user encounters publishing failures, 402/401/404 errors from Sonatype, or needs to migrate from legacy OSSRH to the new Central Portal.
This skill should be used when the user asks questions like "can you summarize", "what happened", "what did we do", "what's the situation", "where are we at", "explain what's going on", "give me an overview", "what's been done", "tell me about this", "walk me through what happened", or any question asking to understand the current state of work or changes. Provides conversational, PR-style summaries with visual diagrams.