Skill Creator
binee108
21 published skills · 0 GitHub stars across the catalog. View on GitHub ↗
moai-domain-uiux
Domain UI/UX Expert - Enterprise design systems, component architecture, accessibility, icons, and theming integration
moai-foundation-context
Enterprise context and session management with token budget optimization and state persistence
moai-foundation-core
MoAI-ADK's foundational principles - TRUST 5, SPEC-First TDD, delegation patterns, token optimization, progressive disclosure, modular architecture, agent catalog, command reference, and execution rules for building AI-powered development workflows
moai-library-shadcn
Moai Lib Shadcn Ui - Professional implementation guide
moai-workflow-templates
Enterprise template management with code boilerplates, feedback templates, and project optimization workflows
agent-model-selection
Guidelines for selecting appropriate AI model (Sonnet vs Haiku) based on task complexity, ensuring cost efficiency while maintaining quality. Use when assigning work.
architecture-principles
Core architecture principles (SSOT, DRY, Anti-Spaghetti) for maintainable code design. Use when planning features, implementing code, or reviewing architecture to prevent duplication and technical debt.
code-minimization
Write minimum necessary code following YAGNI principle to prevent bloat and over-engineering. Use when implementing features to keep the codebase lean and avoid premature optimization or speculative features.
git-workflow-policy
Git workflow policies including commit rules and worktree cleanup sequence. Use when managing git operations, commits, or merges.
interactive-questions
Ask clarifying questions using AskUserQuestion tool when requirements are unclear to prevent assumptions and misunderstandings. Use when facing ambiguous requirements, missing information, or trade-off decisions before implementation.
language-conventions
Defines language usage conventions separating user communication from technical artifacts. Use when writing code, documentation, commits, or communicating with users in multilingual projects.
nine-step-workflow
Comprehensive 9-step development workflow ensuring quality through planning, implementation, review, testing, and documentation with worktree isolation. Includes agent assignments, quality gates, and AskUserQuestion usage. Use when orchestrating feature development or understanding the development process.
phase-decomposition
Breaks features into 3-8 manageable phases with clear deliverables and success criteria. Use when planning feature implementation to create testable, independently committable work units.
plan-document-lifecycle
Lifecycle management of plan documents from creation to automatic cleanup after merge. Use when creating, referencing, or cleaning up plans.
plugin-setup
Interactive plugin setup wizard for first-time configuration. Use when user requests plugin setup, initial configuration, or asks for help setting up the nine-step workflow plugin.
risk-assessment
Identifies technical, timeline, and dependency risks with mitigation strategies. Use when reviewing plans or implementations to catch potential issues early before they become problems.
security-checklist
Prevents RCE, SQL injection, and common vulnerabilities through validation and safe coding practices. Use when implementing or reviewing security-sensitive code involving user input, database queries, or command execution.
tag-based-search
Code tagging system using @FEAT, @COMP, @TYPE tags for easy discovery and navigation. Use when adding documentation tags or searching for related code across the codebase.
test-file-management
Permanent vs temporary test organization and immutable contract philosophy. Use when creating, modifying, or reviewing tests.
trust-principles
TRUST quality principles (Test-first, Readable, Unified, Secured, Trackable) ensuring production-ready code. Use when implementing, reviewing, testing, or evaluating code quality across all development phases.
worktree-path-policy
Ensures all file operations occur in the correct worktree directory to prevent accidental changes to the wrong codebase. Use when implementing, reviewing, testing, or documenting code in worktree-based development workflows.