Loading...
Loading...
Found 23 Skills
Alipay Merchant Onboarding Process Orchestration. Trigger conditions: User says "I want to become an Alipay merchant", "I want to onboard", "I want to sign a contract", "Apply to become a merchant", "Alipay merchant onboarding", "Alipay merchant contract signing", "Payment merchant activation", "Go live", "Merchant application", "Merchant onboarding", "I want to create an app", "Create an app", "Publish an app", "App creation", "App publication". Supports individual developer onboarding, covering the full process of product recommendation, category selection, information collection, product contract signing, and app creation. Uses the real alipay-cli CLI tool.
Review and explain verified deployed EVM smart contracts from a contract address and chain. Use when a user asks to break down what a Solidity contract does, map its architecture and source files, identify user/admin flows, proxy or implementation roles, asset movement, privileged controls, events, state variables, or unresolved uncertainty for developer onboarding, integration triage, or preliminary technical review. This is a developer-oriented contract review, not a security audit or safety certification.
Design the partner-developer onboarding journey on a B2B SaaS platform - from partner signup through dev-account and sandbox provisioning, docs, education and certification posture, and support channels, to the first submitted app. Use whenever the user mentions partner developer onboarding, developer program entry, self-service vs application-gated registration, sandbox tenancy for partners, certification gating submission, partner support channels, or time-to-first-submitted-app - even if they never say "onboarding". Journey design only. Do NOT use for review-gate mechanics (samber/developer-platform-skills@app-marketplace-review) or sandbox isolation architecture (samber/developer-platform-skills@api-test-mode-design).
Technical documentation and knowledge management expert. Use when creating comprehensive documentation systems, improving developer knowledge sharing, or building documentation-driven development workflows.
Get a new developer from clone to a running local app.
Use when bootstrapping team knowledge from a brownfield codebase — reverse-engineers CDRs for contribution to team-ai-directives adlc branch.
Explain large or complex pull requests as a navigable HTML guide, tracing user journeys from entrypoints through changed code. Use when asked to understand a PR or build a guided walkthrough of its changes.
Quickly understand a new codebase's architecture, tech stack, and patterns. Use when user asks "what is this project", "project overview", "how is this codebase structured", "what tech stack", or when onboarding to a new codebase.
Expert guide for setting up development environments including IDE configuration, tooling, dependencies, and developer onboarding. Use when bootstrapping new projects or standardizing team environments.
Turn a curious developer into an activated one: the docs, the quickstart, and the first-run experience that gets them to their first real win fast, and back again. Use when people sign up or star the repo but never get it working, come once and never return, or you're about to pour traffic into a first-run that leaks.
Use when you need to understand or explain a pull request, merge request, branch, or diff rather than judge it — especially when taking over unfamiliar code, locating a change in the project's architecture, or getting oriented before reviewing a large change.