xiaohei-info
UserProduction-grade software delivery for coding-agent teams on Multica — dynamic planning, deterministic execution, verifiable delivery.
Categories
Indexed Skills (45)
creative-claude-design
Design one-off HTML artifacts (landing, deck, prototype).
creative-design-md
Author/validate/export Google's DESIGN.md token spec files.
creative-humanizer
Humanize text: strip AI-isms, audit AI tells, and add real voice.
creative-popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
diagram-architecture
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
diagram-ascii-art
ASCII art: pyfiglet, cowsay, boxes, image-to-ascii.
diagram-concept
Generate 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 integrations (smart city, IoT), and exploded layer views. If a more specialized skill exists for the subject (dedicated software/cloud architecture, hand-drawn sketches, animated explainers, etc.), prefer that — otherwise this skill can also serve as a general-purpose SVG diagram fallback with a clean educational look. Ships with 15 example diagrams.
diagram-drawio
Use 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 .drawio XML and exports locally via the native draw.io desktop CLI.
diagram-excalidraw
Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).
software-design-ddd-domain-modeling
Use 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.
software-design-demand-survey-methodology
Use 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.
software-design-lifecycle-delivery
Use 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.
software-design-lifecycle-solution-design-biz-arch-diagramming
Use 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.
software-design-lifecycle-solution-design-methodology
Use 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.
software-design-lifecycle-tech-detailed-core-flow-diagramming
Use 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.
software-design-lifecycle-tech-detailed-methodology
Use when an architect must run the detailed-design portion of technical design, preserve the full lifecycle-stage doctrine for detailed design, and define the concrete runtime, project, flow, data, interface, non-functional, security, recovery, hardware, and implementation-plan surfaces needed for execution.
software-design-lifecycle-tech-detailed-technical-arch-diagrammi
Use 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.
software-design-lifecycle-tech-overview-functional-arch-diagramm
Use 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.
software-design-lifecycle-tech-overview-methodology
Use 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.
software-design-lifecycle-tech-overview-system-arch-diagramming
Use 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.
software-design-patterns-and-refactoring
Use 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.
software-development-norms
Use 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.
software-development-sketch
Throwaway HTML mockups: 2-3 design variants to compare.
creative-ideation
Generate project ideas via creative constraints.
diagram-infographic
Infographics: 21 layouts x 21 styles (信息图, 可视化).
software-design-lifecycle-deploy-ops-deployment-arch-diagramming
Use 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.
software-design-lifecycle-deploy-ops-methodology
Use 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.
software-development
Top-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.
software-design-clean-architecture
Structure 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 component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.
software-design-philosophy
Manage 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 modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For boundaries, see clean-architecture.
software-design-system-design
Design 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 system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
software-development-karpathy-guidelines
Behavioral 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.
software-development-pragmatic-programmer
Apply 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, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.
software-design-lifecycle-solution-design-biz-flow-diagramming
Use 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.
creative-apple-design
Apple'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.
creative-emil-design-engineering
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
superpowers-brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
superpowers-dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
superpowers-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
superpowers-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 or blind implementation
superpowers-subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
superpowers-systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
superpowers-test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
superpowers-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 assertions always
software-design-mattpocock-grilling
Grill 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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.