Claude Skills by ALVIN-YANG

Choose the primary skill from the work you need delivered. A domain or artifact-specific skill should lead; AY Skills supplies an approval or evidence boundary only where it helps.

Design service and transport contracts before implementation. Use when the primary deliverable is a REST, GraphQL, gRPC, event, webhook, SDK, or internal service interface, including 接口设计, API文档, OpenAPI, 错误码, 鉴权, or 幂等方案. Do not use for system architecture, physical database schemas, generic documentation, or requests primarily asking to implement handlers.

Design a system or subsystem before implementation. Use when the primary deliverable is architecture, module boundaries, data ownership, integration, deployment shape, quality attributes, or an architecture.md proposal, including 技术架构, 后端架构, 系统拆分, or 单体还是微服务. Do not use for routine implementation, refactoring an existing codebase without a design deliverable, endpoint details, or physical database schemas.

Build, diagnose, and repair streaming voice audio on Apple platforms with evidence from provider bytes through hardware output. Use when Swift, macOS, or iOS TTS/voice playback is silent, crackles, pops, clips, re-buffers, fails on later turns, or mixes badly with ASR, VAD, AVAudioEngine, AudioQueue, PCM, MP3, or WebSocket streams. Do not use for generic UI sound design or offline media editing.

Select and design a database-specific logical and physical data model before implementation. Use when the primary deliverable is database choice, tables or collections, keys, constraints, indexes, transactions, concurrency, migration, ERD, DDL, or database.md, including 数据库设计, 表结构, 索引设计, or schema review. Do not use for product requirements, system architecture, API contracts, query debugging, or requests primarily asking to run migrations.

Select and apply publicly documented thinking frameworks from real experts to open-ended decisions, ideation, critique, or explanation. Use when the user asks who understands a problem best, requests a named expert's perspective, invokes best minds, 顶级专家, or 谁最懂这个, or wants competing expert lenses. Do not use for ordinary facts, implementation, diagnosis, individualized medical, legal, or financial advice, style imitation, or unsupported claims about what a person would say.

Diagnose and repair bugs, regressions, crashes, hangs, test failures, incorrect behavior, and unexpected slowness through evidence and root cause. Use when something broke or the user asks to diagnose, 修bug, repair, or implement a proven fix; keep diagnosis read-only unless repair is requested. Let a dedicated diagnosis-only workflow lead a diagnosis-only request when available. Do not use for planned improvements without a failure symptom.

Choose and approve a store-icon metaphor and visual direction, then create the assets when needed. Use when the deliverable is an App Store, Play Store, launcher, AppIcon, .icns, adaptive-icon, 换图标, 重做图标, or 图标太丑 request. Let a dedicated Apple icon asset skill lead exact AppIcon generation, export, installation, or debugging when available. Do not use for in-app glyphs or favicons-only work.

Implement and verify an approved product or software change inside a human-approved boundary. Use when the user asks to add a feature, implement an approved design, change product behavior, or make a general code change, including 加功能, 实现, 做一下, 落地, or 改代码, and no more specific implementation skill applies. Do not use for product discovery, UI or architecture design-only work, bugs, optimization, long-form writing, review, store icons, or other specialized artifact work.

Improve an existing codebase's structure, maintainability, performance, or developer experience from a measured baseline without scope drift. Use when refactoring, optimization, simplification, cleanup, renaming, or extraction is the primary task, including 重构, 优化性能, 整理代码, or 简化, and there is no bug symptom. Let a dedicated module-design skill lead when the interface or seam itself is unresolved. Do not use for greenfield architecture or design-only work.

Write concise consumer-specific Markdown handoffs for approved or implemented APIs, events, messages, and release deltas. Use when backend, web, mobile, desktop, or device teams need 接口文档, 消息协议, 联调说明, 客户端升级说明, or 本期接口变更. Do not use to design a new contract, generate an exhaustive public API reference, describe internal implementation, write product release notes, or document unchanged interfaces.

Research and shape rough product ideas into evidence-backed product definitions, strategies, MVP scopes, requirements, or PRDs. Use when product discovery, competitive research, user and problem framing, product goals, prioritization, or behavioral requirements are the primary deliverable and implementation is not requested, including 做产品定义, 写PRD, 调研竞品, or 这个想法值不值得做. Do not use for visual UI direction, system architecture, API or database design, implementation, store icons, long-form article...

Review product, UI, architecture, API, database, implementation, or delivery artifacts for intent, correctness, risk, cross-artifact consistency, and proof. Use when a general audit, review-then-fix, 发布前检查, or check spanning several handoffs is requested. Let a dedicated since-commit or pull-request code-review skill lead branch diffs when installed, and yield to specific security or accessibility review.

Create and validate reproducible Apple App Store screenshot decks from exact shipped UI captures. Use when asked for App Store 宣传图, localized screenshot sets, device framing, marketing copy overlays, exact-size exports, or screenshot truth checks. Do not use for build upload, submission, review status, StoreKit or privacy setup, app icons, product UI design, or application implementation.

Design and approve product interfaces before frontend implementation. Use when the primary deliverable is visual direction, application screens, screen-by-screen mockups, interaction states, a design system, or a design.md handoff, including 定设计风格, 生成设计图, UI方案, or 一张张确认页面. Do not use for product strategy, store icons, a single decorative image, UI compliance review, or requests primarily asking to write frontend code.

Research, structure, draft, rewrite, and illustrate substantial articles or technical explainers. Use when a long-form article, 写技术文章, evidence gathering, visual plan, diagram, English, or bilingual deliverable is central. Let a dedicated natural-Chinese writing skill lead prose-only Chinese articles when available. Do not use for short answers, UI copy, or narrow documentation edits.