Smart Contracts

Guide developers through property-based testing including property definition, shrinking, and framework-specific implementation

Use @inkcre/web-design styling system with design tokens, SCSS mixins, and theming.

Complete ArgoCD API and CLI skill for GitOps automation. Use when working with ArgoCD for: (1) Managing Applications - create, sync, delete, rollback, get status, (2) ApplicationSets - templated multi-cluster deployments, (3) Projects - RBAC, source/destination restrictions, sync windows, (4) Repositories - add/remove Git repos, Helm charts, OCI registries, (5) Clusters - register, rotate credentials, manage multi-cluster, (6) Accounts - generate tokens, manage users, check permissions, (7) Any ArgoCD REST API calls or argocd CLI commands. Supports both REST API (curl/HTTP) and CLI wrapper approaches with bearer token authentication.

Production-ready authentication framework for TypeScript with Cloudflare D1 support via Drizzle ORM or Kysely. Use this skill when building auth systems as a self-hosted alternative to Clerk or Auth.js, particularly for Cloudflare Workers projects. CRITICAL: better-auth requires Drizzle ORM or Kysely as database adapters - there is NO direct D1 adapter. Supports social providers (Google, GitHub, Microsoft, Apple), email/password, magic links, 2FA, passkeys, organizations, and RBAC. Prevents 12+ common authentication errors including D1 adapter misconfiguration, schema generation issues, session serialization, CORS, OAuth flows, and JWT token handling.Keywords: better-auth, authentication, cloudflare d1 auth, drizzle orm auth, kysely auth, self-hosted auth, typescript auth, clerk alternative, auth.js alternative, social login, oauth providers, session management, jwt tokens, 2fa, two-factor, passkeys, webauthn, multi-tenant auth, organizations, teams, rbac, role-based access, google auth, github auth, micros

Expert-level Vercel AI SDK v5 patterns for production chatbots. Use for: (1) Chat persistence with Drizzle/PostgreSQL, (2) Generative UI with typed tool parts, (3) Human-in-the-loop tool confirmations, (4) Custom data streaming with reconciliation, (5) Anthropic provider with extended thinking/reasoning, (6) Type-safe message metadata with token tracking. Covers advanced patterns only - assumes basic AI SDK knowledge. NOT for AI SDK v6.

提供Foundry智能合约开发的专业指导,包括合约编写、测试、部署和安全最佳实践。当需要开发、测试或部署Solidity智能合约时使用此技能。

Expert on Shelby Protocol smart contracts on Aptos blockchain. Helps with blob metadata, micropayment channels, auditing system, storage commitments, placement group assignments, Move modules, and on-chain state management. Triggers on keywords Shelby smart contract, Shelby Move, blob metadata, micropayment channel, Shelby auditing, placement group assignment, storage commitment, Aptos contract.

Code quality standards, linting rules, and best practices for clean Solidity code. Use when reviewing code quality or establishing project standards.

This skill should be used when setting up organization-level app integrations (Reddit, Notion, LinkedIn, WordPress) with OAuth flows, encrypted token storage, API client wrappers, and usage logging in a Next.js App Router application. Use this skill when implementing external provider connections for a multi-tenant app with secure credential management, token refresh, and admin-controlled integration features.

Defines branch naming conventions for issue work. Use when creating branches for issues, understanding work status from branches, or linking commits to issues.

Flowcharts are composed of **nodes** (geometric shapes) and **edges** (arrows or lines). The Mermaid code defines how nodes and edges are made and accommodates different arrow types, multi-directional arrows, and any linking to and from subgraphs.

Audit and exploit smart contracts and Web3 applications including reentrancy, integer overflow, access control flaws, and DeFi-specific vulnerabilities. Use when testing blockchain applications or performing smart contract audits.

Complete Figma design extraction for pixel-perfect implementation.Extracts design tokens, component specs, layouts, and responsive behavior systematically.Use when user provides Figma design:- Figma URL or file link provided- User mentions "Figma", "design file", "mockup", or "design system"- During /create-plan phase when design needs extraction- User says "extract from Figma" or references Figma linkExtract systematically:- Design tokens: ALL colors (hex + usage), typography (sizes, weights, line heights), spacing scale, border radius, shadows, opacity values- Components: ALL states (default, hover, active, focus, disabled, loading, error), ALL variants (size/style/intent), exact dimensions, spacing, visual properties- Layouts: page structure, grid systems (columns, gutters), component hierarchy- Responsive: mobile/tablet/desktop differences explicitly documented- Assets: icons (names, sizes), images (dimensions, alt text), illustrationsGoal: Extract ONCE completely during planning phase

Guide developers through property-based testing including property definition, shrinking, and framework-specific implementation

Use when building features with unknowns or uncertainties - start from well-understood parts (business logic, UX, pure functions), write code as if ideal collaborators exist, use mocks to define APIs through usage, preventing analysis paralysis from trying to understand everything upfront

Expert in managing GCP Groups (Google Cloud Identity and Azure AD) via the Groups API. **Use this skill whenever the user mentions 'groups', 'group members', 'add to group', or 'remove from group'.** Handles listing members (with file-based approach for large groups), adding/removing members, and checking membership. Uses ADM token authentication. **DO NOT use for ServiceNow groups.**

Framework-agnostic brutalist web design system with Space Grotesk typography, purple/cyan/pink palette, bold offset shadows, and sharp borders. Use when building any web interface (HTML, React, Vue, Svelte, Astro, etc.) that needs neo-brutalist aesthetics with consistent design tokens, typography scale, and component patterns.

Complete guide for Google Gemini API using the CORRECT current SDK (@google/genai v1.27+, NOT thedeprecated @google/generative-ai). Covers text generation, multimodal inputs (text + images + video +audio + PDFs), function calling, thinking mode, streaming, and system instructions with accurate 2025model information (Gemini 2.5 Pro/Flash/Flash-Lite with 1M input tokens, NOT 2M).Use when: integrating Gemini API, implementing multimodal AI applications, using thinking mode forcomplex reasoning, function calling with parallel execution, streaming responses, deploying toCloudflare Workers, building chat applications, or encountering SDK deprecation warnings, context windowerrors, model not found errors, function calling failures, or multimodal format errors.Keywords: gemini api, @google/genai, gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite,multimodal gemini, thinking mode, google ai, genai sdk, function calling gemini, streaming gemini,gemini vision, gemini video, gemini audio, gemini pdf, sys

Expert on Aptos blockchain, Move language, smart contracts, NFTs, DeFi, and Aptos development. Triggers on keywords aptos, move, blockchain, smart contract, nft, defi, web3, mainnet, testnet, devnet

Use Jira scripts instead of Jira MCP for ticket operations. Read operations (jira-get-issue), write operations (jira-create-ticket, jira-comment-ticket, jira-update-ticket, jira-log-work, jira-link-tickets), and list operations (jira-list-tickets, jira-list-sprint). Use when reviewing code, creating tickets, commenting on tickets, updating tickets, logging work, linking tickets, listing tickets, or viewing sprint. Replaces ~30 MCP functions (40k tokens) with lightweight bash scripts.