build-game
Build the Asciicker game executable using the Mac makefile. Use when building the game, recompiling after changes, or when the user asks to build or compile the game.
Discover Databases skills, compare source repositories and read the instructions for each workflow.
Build the Asciicker game executable using the Mac makefile. Use when building the game, recompiling after changes, or when the user asks to build or compile the game.
Manage session memory - load context, summarize sessions, compress old sessions, search memory
Build the Asciicker game for web using Emscripten, diagnose web build failures, and test WebAssembly output. Leverages specialized MCP agents (Serena, Context7, Chrome DevTools) for deep analysis and debugging.
Validate Blender AKM (Asciicker Mesh) export files, check mesh format, and verify compatibility with the Asciicker engine. Use when exporting from Blender, checking mesh files, or troubleshooting mesh loading.
Test the grass terrain implementation in the editor and game. Use when verifying grass/water terrain, testing material changes, or checking terrain visibility. Includes verification steps from TESTING_GUIDE.md.
Build the Asciicker map editor (asciiid) using the Mac makefile. Use when building the editor, recompiling after changes, or when the user asks to build or compile the editor.
Add a new terrain material definition (dirt, stone, sand, etc.) to the Asciicker material system. Use when adding new materials, defining terrain types, or expanding the material palette.
Obsidian vault notes (AILSS): search/summarize/edit (frontmatter, tags/keywords, typed links/backlinks, broken links; retrieval-first MCP; gated writes)
핵심 행동 규칙 및 안전성 원칙 (항상 적용)
장비 전체 라이프사이클 관리 워크플로우
NSO 장비 관리 및 설정 변경 도구 사용법
Batfish 네트워크 분석 도구 사용법
PNETLab 토폴로지 관리 도구 사용법
동적 텔레메트리 데이터 조회 도구 사용법
Design views with proper includes/excludes and basic layout. Use for include patterns, tag filtering, and simple rank hints. For advanced styling/navigation, use customize-view.
Create Architecture Decision Records (ADRs) documenting WHY decisions were made. Uses standard ADR format (Status/Context/Decision/Consequences).
Quick reference for available element kinds and relationship types from shared specifications.
Load project context before making changes. Use when starting work to check available element kinds, relationship types, and tags.
Create sequence views showing temporal flows and user interactions. Uses plain arrows with descriptive labels (no relationship kinds).
Validate model correctness using MCP tools. Checks element references, relationships, view definitions, and syntax.
Create typed relationships with FQN, proper kinds (calls/async/reads/writes), descriptive labels, and no return relationships.
Structure multi-project workspaces with shared specifications. Use template project for new projects, organize by domain/team/layer.
Create elements with proper naming (PascalCase kinds, camelCase vars), required metadata (technology, description), and correct hierarchy.
Model deployment infrastructure (environments, zones, VMs, apps) with proper hierarchy and instanceOf links. Organize zones into tiers (DMZ, App, Data, Processing) with rich descriptions including VLAN/network...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.