c3-component-design
Use when documenting component implementation patterns, internal structure, or hand-off points - enforces NO CODE rule and diagram-first approach for leaf-level C3 documentation
setup-statusline
Setup Claude Code statusline configuration automatically (global)
css-design-tokens
Zentrale CSS-Variablen und Design-Tokens fรผr konsistente Styles im gesamten CONSYS-Projekt. Farben, Schriften, Abstรคnde, Schatten.
dotnet-repo-discovery
Discover the primary .sln, list projects, and emit a solution map with target frameworks and test flags.
godot-coding-standards
Godot 4.x ๆ ธๅฟๆถๆๅๅใๅฝ่ฎพ่ฎกใๅฎกๆฅ Godot ็ปไปถๅ็ณป็ปๆถไฝฟ็จใๅ ณๆณจ๏ผ็ปไปถๆจกๅผใไฟกๅท้ไฟกใResource่ฎพ่ฎกใ็ณป็ปๆถๆใ่งฆๅ่ฏ๏ผgodot, ็ปไปถ, ไฟกๅท, ๆถๆ, ่ฎพ่ฎกใ
invalidate-local-plugin
Stop the lingo server and delete the local plugin cache directory so Claude Code downloads the current version again on restart. Use this for testing plugin updates during development.
mql5-x-compile
Compile MQL5 indicators via CLI using X: drive mapping to bypass 'Program Files' path spaces issue. Use PROACTIVELY after editing ANY .mq5 or .mqh file. Triggers - after editing MQL5 code, compile, build, MetaEditor, .mq5, .mqh, indicator, script, EA, expert advisor, "test it", "try it", "run it", path space errors. (project)
agents-ide-usage
Use agents-ide MCP tools for faster code exploration and manipulation
migrating-ast-node
Migrate an ast node definition from java to go
east
East programming language - a statically typed, expression-based language embedded in TypeScript. Use when writing East programs with @elaraai/east. Triggers for: (1) Writing East functions with East.function() or East.asyncFunction(), (2) Defining types (IntegerType, StringType, ArrayType, StructType, VariantType, etc.), (3) Using platform functions with East.platform() or East.asyncPlatform(), (4) Compiling East programs with East.compile(), (5) Working with East expressions (arithmetic, collections, control flow), (6) Serializing East IR with .toIR() and EastIR.fromJSON(), (7) Standard library operations (formatting, rounding, generation).
figma-screenshot-extractor
Extract and save Figma screenshots from Codex session logs when user needs to recover images captured by the Figma MCP server
plantuml-stdlib
Find PlantUML Standard Library (stdlib) modules and suggest `!include <...>` paths (C4-PlantUML, icons, macros, etc.).
context-injector
ไธไธๆๆณจๅ ฅๅทฅๅ ทใๅฝ็จๆทๅๆขๆจกๅใ่ฟๅ ฅๆฐๅ่ฝไธไธๆๆถ่ชๅจ่งฆๅใๆณจๅ ฅ็ธๅ ณ้ขๅ็ฅ่ฏใๆๆฏ็บฆๆใไปฃ็ ไฝ็ฝฎไฟกๆฏใ
astrolabe-common
Base .NET utilities library providing exceptions (NotFoundException, ForbiddenException), LINQ extensions, list editing with change tracking, and reflection utilities. Use when working with Astrolabe.Common or needing common .NET utilities.
csharp-project-expert
ALWAYS use for ANY C# operation: renaming (files/classes/methods/properties/namespaces), finding references/usages ("where is X used"), finding definitions ("where is X defined"), understanding code structure (hierarchies/dependencies/relationships). Roslyn-powered semantic analysis ensures all references are updated correctly across the entire solution.
mcp-structure-skill
Guidance and snippets for creating/updating Codex skills tailored to the mcp-coding-agent project (AST/dependency tooling). Use when asked to build a new skill or refine one for this repoโs workflows and structure.
typescript
TypeScript coding conventions and best practices. Use when working with TypeScript files, defining types, or setting up TypeScript projects.
skill-creator
Use when creating or editing skills for ai-coding-config repo
fstar
F* proof-oriented programming language for verified software development. Use when: (1) writing or verifying F* code (.fst/.fsti files), (2) understanding verification errors from Z3/SMT, (3) learning dependent types, refinement types, or theorem proving, (4) extracting verified code to C via Karamel or to OCaml, (5) working with Low*, Steel, or Pulse DSLs, (6) setting up F* projects with mise. Triggers: F* code, fstar.exe, refinement types, SMT solver errors, z3rlimit, fuel/ifuel, verification conditions, dependent types, Karamel/krml extraction.
typescript-best-practices
TypeScript development best practices, patterns, and conventions. Use when writing TypeScript code, reviewing .ts/.tsx files, discussing type safety, generics, utility types, or TypeScript project configuration. Triggers on mentions of TypeScript, tsconfig, type inference, generics, discriminated unions, React TypeScript.
