All authors

Claude Skills by xiaohei-info
github.com/xiaohei-info46 skills0 installs94 views
- Creative Apple DesignApple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.Votes: 0GitHub stars: 34
- Creative Claude DesignDesign one-off HTML artifacts (landing, deck, prototype).Votes: 0GitHub stars: 34
- Creative Design MdAuthor/validate/export Google's DESIGN.md token spec files.Votes: 0GitHub stars: 34
- Creative Emil Design EngineeringThis skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.Votes: 0GitHub stars: 34
- Creative HumanizerHumanize text: strip AI-isms, audit AI tells, and add real voice.Votes: 0GitHub stars: 34
- Creative IdeationGenerate project ideas via creative constraints.Votes: 0GitHub stars: 34
- Creative Popular Web Designs54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.Votes: 0GitHub stars: 34
- Diagram ArchitectureDark-themed SVG architecture/cloud/infra diagrams as HTML.Votes: 0GitHub stars: 34
- Diagram Ascii ArtASCII art: pyfiglet, cowsay, boxes, image-to-ascii.Votes: 0GitHub stars: 34
- Diagram ConceptGenerate flat, minimal light/dark-aware SVG diagrams as standalone HTML files, using a unified educational visual language with 9 semantic color ramps, sentence-case typography, and automatic dark mode. Best suited for educational and non-software visuals — physics setups, chemistry mechanisms, math curves, physical objects (aircraft, turbines, smartphones, mechanical watches), anatomy, floor plans, cross-sections, narrative journeys (lifecycle of X, process of Y), hub-spoke system integratio...Votes: 0GitHub stars: 34
- Diagram DrawioUse when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, network topology, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Best suited when the diagram needs custom styling, rich shape vocabulary, swimlanes, or exportable images (PNG/SVG/PDF/JPG). Generates .drawi...Votes: 0GitHub stars: 34
- Diagram ExcalidrawHand-drawn Excalidraw JSON diagrams (arch, flow, seq).Votes: 0GitHub stars: 34
- Diagram InfographicInfographics: 21 layouts x 21 styles (信息图, 可视化).Votes: 0GitHub stars: 34
- Software Design Clean ArchitectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers compo...Votes: 0GitHub stars: 34
- Software Design Ddd Domain ModelingUse when architecture work hinges on DDD-style domain modeling: subdomains, bounded contexts, context relationships, aggregate boundaries, and how those decisions shape overview or detailed design artifacts.Votes: 0GitHub stars: 34
- Software Design Demand Survey MethodologyUse when an architect must start at the demand-research stage, turn a business problem into a researchable architecture problem, and preserve the full lifecycle-stage doctrine for what to ask, what to answer, and what the business-research document must contain.Votes: 0GitHub stars: 34
- Software Design Lifecycle DeliveryUse when an architect must decide which architecture lifecycle stage to enter next, route to the correct stage methodology skill, and apply the merged lifecycle backbone as one coherent delivery chain rather than as separate old and new skill systems.Votes: 0GitHub stars: 34
- Software Design Lifecycle Deploy Ops Deployment Arch DiagrammingUse when an architect in the deploy-and-ops stage must produce or review the 部署架构图 / 物理架构图 so that physical topology, deployment boundaries, and run-stage assumptions are visible during handoff.Votes: 0GitHub stars: 34
- Software Design Lifecycle Deploy Ops MethodologyUse when an architect must run the deployment-and-operations handoff stage, preserve the full lifecycle-stage doctrine for deploy/ops, and turn completed design into physical topology, rollout, operations, monitoring, emergency, and rehearsal deliverables.Votes: 0GitHub stars: 34
- Software Design Lifecycle Solution Design Biz Arch DiagrammingUse when an architect in the solution-design stage must produce or review the 业务解决方案架构图 and needs the fully merged specialist method directly inside the new lifecycle family instead of via a legacy wrapper skill.Votes: 0GitHub stars: 34
- Software Design Lifecycle Solution Design Biz Flow DiagrammingUse when an architect in the solution-design stage must produce or review a 业务流程图 that explains roles, steps, and handoff order without collapsing into system architecture, technical architecture, or detailed-design flow logic.Votes: 0GitHub stars: 34
- Software Design Lifecycle Solution Design MethodologyUse when an architect must run the solution-design stage after demand research, preserve the full lifecycle-stage doctrine for this stage, and turn business research into solution-design outputs such as business flow, domain model, solution architecture, risk controls, and milestone framing.Votes: 0GitHub stars: 34
- Software Design Lifecycle Tech Detailed Core Flow DiagrammingUse when an architect in detailed technical design must produce or review the 关键流程图 or 状态机 and needs the fully merged branch-complete core-flow specialist method directly inside the new lifecycle family.Votes: 0GitHub stars: 34
- Software Design Lifecycle Tech Detailed MethodologyUse when an architect must run the detailed-design portion of technicalVotes: 0GitHub stars: 34
- Software Design Lifecycle Tech Detailed Technical Arch DiagrammingUse when an architect in detailed technical design must produce or review the 技术架构图 and needs the fully merged technical-architecture specialist method directly inside the new lifecycle family.Votes: 0GitHub stars: 34
- References> **定位**:工具无关、系统无关、场景全覆盖的架构图绘制指令集。可加载于任意 AI Agent,指导其在任何技术领域(后端、前端、数据、云原生、安全、DevOps、AI/ML、IoT、区块链等)产出专业、一致、可读的架构图。 > **目标受众**:架构师、研发工程师、技术负责人。 > **回答的核心问题**: > 1. 功能通过什么技术栈实现?如何选型? > 2. 项目/服务的逻辑分层与物理结构是什么? > 3. 服务、进程、任务、调用链路如何协作? > 4. 稳定性、扩展性、安全性、可观测性如何保障? > **推荐工具**:Excalidraw / Draw.io (diagrams.net) / PlantUML / SVG/HTML / Lucidchart。Agent 应根据场景自行选择最合适的工具,或按用户指定工具输出。 ---Votes: 0GitHub stars: 34
- Software Design Lifecycle Tech Overview Functional Arch DiagrammingUse when an architect in overview technical design must produce or review the 系统功能架构图 and needs the fully merged functional-architecture specialist method directly inside the new lifecycle family.Votes: 0GitHub stars: 34
- Software Design Lifecycle Tech Overview MethodologyUse when an architect must run the overview-design portion of technical design, preserve the full lifecycle-stage doctrine for shared technical-design entry and overview design, and define goals, alternatives, functional layering, system structure, risk, and overview-level design boundaries before detailed design begins.Votes: 0GitHub stars: 34
- Software Design Lifecycle Tech Overview System Arch DiagrammingUse when an architect in overview technical design must produce or review the 系统架构图 and needs the fully merged system-architecture specialist method directly inside the new lifecycle family.Votes: 0GitHub stars: 34
- Software Design Mattpocock GrillingGrill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.Votes: 0GitHub stars: 34
- Software Design Patterns And RefactoringUse when architecture or backend work needs pre-code structural guidance from design patterns, or post-code cleanup guidance from refactoring and code-smell-driven improvement.Votes: 0GitHub stars: 34
- Software Design PhilosophyManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", or "pass-through method". Also trigger when reviewing interface designs for simplicity, evaluating whether an abstraction is pulling its weight, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow m...Votes: 0GitHub stars: 34
- Software Design System DesignDesign scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common s...Votes: 0GitHub stars: 34
- Superpowers BrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 34
- Superpowers Dispatching Parallel AgentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesVotes: 0GitHub stars: 34
- Superpowers Finishing A Development BranchUse 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 cleanupVotes: 0GitHub stars: 34
- Superpowers Receiving Code ReviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationVotes: 0GitHub stars: 34
- Superpowers Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current sessionVotes: 0GitHub stars: 34
- Superpowers Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 34
- Superpowers Test Driven DevelopmentUse when implementing any feature or bugfix, before writing implementation codeVotes: 0GitHub stars: 34
- Superpowers Verification Before CompletionUse 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 assertions alwaysVotes: 0GitHub stars: 34
- Software Development Karpathy GuidelinesBehavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.Votes: 0GitHub stars: 34
- Software Development NormsUse when writing, reviewing, or refactoring code in any language to apply industrial-grade development norms abstracted from the Alibaba Java Development Handbook. Covers naming, type safety, exceptions, logging, concurrency, databases, project structure, testing, and security with language-agnostic principles and single-language examples.Votes: 0GitHub stars: 34
- Software Development Pragmatic ProgrammerApply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, do...Votes: 0GitHub stars: 34
- Software Development SketchThrowaway HTML mockups: 2-3 design variants to compare.Votes: 0GitHub stars: 34
- Software DevelopmentTop-level entry point for the software development skill family. Routes to the right sub-skill for design patterns, refactoring, DDD, worktree governance, kanban splitting, container supervision, project governance, runtime ops, and web routing.Votes: 0GitHub stars: 34