Loading...
Loading...
Found 491 Skills
bkend.ai platform onboarding and core concepts guide. Covers MCP setup, resource hierarchy (Org->Project->Environment), Tenant vs User model, and first project creation. Use proactively when user is new to bkend or asks about initial setup. Triggers: bkend setup, first project, bkend start, MCP connect, bkend 시작, 처음, 설정, MCP 연결, 프로젝트 생성, bkend始め方, 初期設定, MCP接続, bkend入门, 初始设置, MCP连接, configuracion bkend, primer proyecto, configuration bkend, premier projet, bkend Einrichtung, erstes Projekt, configurazione bkend, primo progetto Do NOT use for: specific database/auth/storage operations (use domain-specific skills), enterprise infrastructure (use infra-architect).
Build a brand context file that all other creator marketing skills read before starting. This skill should be used when setting up brand context, starting a new brand, onboarding a brand, creating brand context, initializing brand profile, running brand setup, building a brand profile, capturing brand information, filling out brand details, or when any other skill cannot find .claude/brand-context.md. For campaign-specific briefs, see campaign-brief-generator. For creator-specific outreach, see outreach-writer. Run this first before using any other creator marketing skill.
SaaS product design methodology for building user-facing application features. Covers: onboarding, empty states, billing UX, feature gating, dashboard design, notification patterns, settings/admin UX, audit trails, loading states, multi-tenancy. Use when: designing new SaaS features, creating dashboards, planning onboarding flows, or reviewing product-level UX decisions.
Generate an ARCHITECTURE.md file for a codebase following matklad's principles. Use when asked to "write an architecture doc", "create ARCHITECTURE.md", "document the architecture", "explain the codebase structure", "write a codemap", or when onboarding contributors to a project. Based on https://matklad.github.io/2021/02/06/ARCHITECTURE.md.html and modeled after rust-analyzer's architecture doc.
Use this skill when designing SDKs, writing onboarding flows, creating changelogs, or authoring migration guides. Triggers on developer experience (DX), API ergonomics, SDK design, getting-started guides, quickstart documentation, breaking change communication, version migration, upgrade paths, developer portals, and developer advocacy. Covers the full DX lifecycle from first impression to long-term retention.
Contextual help and onboarding for the swain skill ecosystem. Use when users ask about swain — what skills exist, how to use them, what artifacts are available, how workflows connect, or when they need a quick reference. Also invoked after swain-init to orient new users. Triggers on: 'how do I...', 'what is...', 'help', 'what can swain do', 'show me the commands', 'I'm confused', 'where do I start', any question about swain skills, artifacts, or workflows, and after project onboarding completes.
First-time Perses setup pipeline: discover or deploy server, configure MCP connection, create initial project, add datasources, and verify connectivity. 4-phase pipeline: DISCOVER, CONNECT, CONFIGURE, VALIDATE. Use when setting up Perses for the first time, connecting Claude Code to an existing Perses instance, or onboarding a new team to Perses. Use for "perses onboard", "setup perses", "connect to perses", "perses getting started". Do NOT use for dashboard creation (use perses-dashboard-create) or server deployment details (use perses-deploy).
Implements onboarding and help systems including product tours, interactive tutorials, tooltips, checklists, help panels, and progressive disclosure patterns. Use when building first-time experiences, feature discovery, guided walkthroughs, contextual help, setup flows, or user activation features. Provides timing strategies, accessibility patterns (keyboard, screen readers, reduced motion), and metrics for measuring onboarding success.
Generate project-level AGENTS.md guides that capture conventions, workflows, and required follow-up tasks. Use when a repository needs clear agent onboarding covering structure, tooling, testing, task flow, README expectations, and conventional commit summaries.
Friendly onboarding when users ask about capabilities
Apply UX psychology effects to UI design. Automatically reference when designing landing pages, pricing tables, onboarding flows, and CTAs.
Add or refresh a fixed 20-line file-header comment that summarizes a source file and indexes key classes/functions with line-number addresses. Use when annotating large codebases for fast navigation, onboarding, refactors, or when you want LLMs/humans to locate relevant symbols quickly without reading entire files.