layer-09-ux
Expert knowledge for UX Layer modeling in Documentation Robotics
Expert knowledge for UX Layer modeling in Documentation Robotics
Answers questions about Claude Code features, configuration, and usage from local documentation synced from code.claude.com. Use when users ask about hooks, plugins, skills, MCP servers, slash commands, sub-agents, settings, permissions, sandboxing, CLAUDE.md memory files, model selection, costs, IDE integrations (VS Code, JetBrains), CI/CD (GitHub Actions, GitLab), or cloud providers (Bedrock, Vertex, Azure).
Optimizes AI models for edge deployment through quantization, lazy loading, and memory management. Use when deploying models to resource-constrained environments, mobile devices, or edge computing scenarios. Do not use for cloud deployment, model training, or data preprocessing.
Implement Background Sync API to queue and replay mutations when connectivity is restored.
Provides workflow guidelines for problem-solving, git commits, GitHub issues, PRs, build management, and testing. Use when planning tasks, creating issues, submitting PRs, managing builds, or writing tests.
This skill should be used when the user wants to "create to-be-continuous component", "build TBC template", "extend existing component", "create variant", "contribute to to-be-continuous", "component structure", "how to create gitlab ci component", or needs guidance on component architecture, naming conventions, GitLab CI component syntax, input specifications, base job patterns, or to-be-continuous best practices and philosophy.
Create typed relationships with FQN, proper kinds (calls/async/reads/writes), descriptive labels, and no return relationships.
Engineer resilient UI systems with layered error boundaries, retries, and fallback orchestration.
錯誤處理與 Result Pattern 技能,協助開發者實作統一的錯誤處理機制,包含 Result Pattern 應用、Failure 物件建立與分層錯誤處理策略。
Use event sourcing to build auditable, replayable UI state systems compatible with concurrent rendering.
Design deterministic state machines that remain correct under concurrent rendering and re-entrancy.
Multi-repository synchronization coordinator for version alignment, dependency sync, and cross-package integration. Use for package synchronization, version management, documentation alignment, and coordinated releases across multiple repositories.
Railway deployment, CI/CD workflows, GitHub Actions, and smoke tests. Handles Railway configuration, GitHub Actions workflows, deployment automation, and health checks. Use when working with deployment, CI configuration, Railway setup, or infrastructure automation, or when user mentions Railway environments, GitHub Actions, deployment issues, CI failures, "Build failed" errors, smoke test errors, CI/CD pipelines, Docker configuration, or devops workflows.
Model complex UI flows using finite state machines to ensure deterministic behavior.
Repository 設計指導技能,協助開發者根據業務需求選擇最合適的 Repository 設計策略(資料表導向 vs 需求導向 vs 混合模式)。
Enforces JU-DO-KON! architectural boundaries, module responsibilities, and design intent. Use when designing, refactoring, or reviewing core game logic.
Establish scalable architecture using modular boundaries, domain-driven design, and consistent data access patterns.
Decouple business logic from UI using Inversion of Control with Context and Hooks.
SOP for autonomous bug detection, diagnosis, and fixing without human intervention. Use when treating GitHub issues or when assessing repository readiness for autonomous maintenance.
Manage Architecture Decision Records (ADRs) using git-adr, a CLI tool that stores ADRs in git notes instead of files. Execute commands (init, new, edit, list, show, search, sync, supersede, link, attach, stats, export, import), generate ADR content in any format (MADR, Nygard, Y-Statement, Alexandrian, Business Case, Planguage), and teach ADR best practices. Use when users ask about: ADRs, architecture decisions, decision records, git-adr commands, documenting technical decisions, or need help creating/managing ADRs in a git repository.