GitHub
prototype-planning
Define what to build at what fidelity to learn what you need without over-investing. Use before starting any prototype.
Skills IA Outils
Découvrez les skills Outils, comparez leurs dépôts et consultez leurs instructions.
Catégories: Outils
Outils Effacer les filtres
Explorer
GitHub
assumption-validation
Test whether assumptions are true before making commitments. Use when assumptions have low certainty and high risk.
GitHub
zettel
제텔카스텐 방식의 원자적 노트를 생성합니다. 공부한 개념을 정리하거나 새로운 지식을 추가할 때 사용하세요.
GitHub
blog
블로그 글 초안을 생성합니다. 개발 블로그나 취미 블로그 글을 쓰기 시작할 때 사용하세요.
GitHub
publish
작성 완료된 블로그 글을 발행 처리합니다. 블로그 글 발행, 아카이브 이동, 글 완료 처리할 때 사용하세요.
GitHub
naki-mcp-proxy
Token-efficient proxy for Naki's 47 MCP tools. Routes user intent to optimal MCP tool via agent isolation, saving 40-70% tokens. Use for any Naki game control, bot status, or UI operation.
GitHub
mcp-tool-writer
Create, modify, and manage MCP tools for the Naki mahjong AI assistant. Use when adding new MCP tools, modifying existing tools, or fixing tool-related issues. This skill understands the Protocol-based MCPTool...
GitHub
release-manager
Build, package, tag, and release Naki app to GitHub. Use when the user asks to "release", "publish", "tag", "build DMG/ZIP", or "upgrade version". Handles the complete release workflow from build to GitHub rele...
GitHub
webui-tester
Test, debug, and modify Majsoul WebUI (Laya engine) within the Naki app. Use when the user asks to adjust "the screen" or "UI" - clarify whether they mean Naki's SwiftUI app or Majsoul's WebUI. This skill handl...
GitHub
buzzllm-gateway
Use buzzllm CLI to perform web searches, execute Python code in Docker, search/analyze local codebases, or generate code change blocks. Trigger when user asks for web search, Python execution, code analysis, or...
GitHub
cc-task
Implement based on an approved plan. Use after cc-plan is finalized.
GitHub
cc-explore
Research codebase and dependencies to support planning. Use when evidence is missing.
GitHub
cc-plan
Create a concrete implementation plan with scope, risks, verification, and rollback. Use before any code changes.
GitHub
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...
GitHub
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
GitHub
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
GitHub
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
GitHub
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
GitHub
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
GitHub
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
GitHub
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
GitHub
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
GitHub
executing-plans
Use when you have a written implementation plan to execute with review checkpoints
GitHub
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.