Loading...
Loading...
Found 192 Skills
Fullstory integration. Manage Users, Sessions. Use when the user wants to interact with Fullstory data.
Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
Route to the next skill. Tell it your situation; it names the skill.
Designs the pricing and packaging architecture of a developer tool - the value metric (seats, consumption, capacity, outcome, or a hybrid), free-tier limits, the tier ladder up to enterprise gating, price points bounded by a margin floor and the self-host and build-it ceilings, and a plan to change prices without a backlash. Use whenever someone asks what to charge for a developer tool, how to package tiers, where free ends and paid begins, whether to bill per seat or per usage, how to price against their own open-source edition, or how to raise prices safely - even if they only say the pricing page feels wrong. Not which business model to run - use samber/developer-relations-skills@devtools-business-model. Not pricing-page copy.
Expert in building developer tools, CLI utilities, IDE extensions, and optimizing local development environments.
API document search for WeCom, Feishu, Lark, DingTalk, Taobao, Xiaohongshu, Douyin E-commerce, WeChat Mini Program, WeChat Shop, Pinduoduo, Youzan, WeChat Pay, Alipay, JD, SHEIN, Dewu. WeCom Feishu Lark DingTalk Taobao Xiaohongshu Douyin WeChat Pinduoduo Youzan Alipay JD SHEIN Dewu API docs search. 26,000+ API docs across 15 Chinese open platforms with full-text search. Search API development documents of 15 open platforms, supporting Chinese full-text retrieval. wecom feishu lark dingtalk taobao xiaohongshu xhs douyin jinritemai wechat miniprogram wechat-shop wechat-pay pinduoduo youzanyun alipay jd shein dewu poizon openapi webhook access_token Douyin Shop, Mini Program, Shop, PDD, JD Open Platform, Dewu Open Platform, E-commerce Open Platform, Interface Document, Open Platform
Comprehensive skill for project planning and prompt engineering. Covers hierarchical plans (briefs, roadmaps, phases), Claude-to-Claude meta-prompts, and multi-stage workflows. Use when: planning, prompt creation, agentic pipeline work, project roadmap, meta-prompts, research to implement workflow.
Use when exploring or modifying a codebase and you need a cheap structural map of files, directories, imports, exports, or direct members before reading full source.
Search issues, merged pull requests, READMEs, and documentation. Use when the question is how a library or API behaves, what an error means, or whether a bug was fixed; prefer this over a general web page.
Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.
Guide wanderers to the right animal for their journey. Perch, tilt your head, chatter about the forest, present the options, and warble the recommendation. Use when helping users choose which skill to use, discovering capabilities, or navigating the ecosystem.
Disaster recovery drill exercises and security checklists for web application projects (SPA, SSR, full-stack web apps). Focused on solo/indie developers using free-tier infrastructure (Vercel, Supabase, Cloudflare, Netlify, Railway, etc.). Bridges big-tech best practices (NIST, Google SRE DiRT, ISO 22301) to indie scale. Use when the user mentions drills, disaster recovery, security audit, incident simulation, project health check, resilience testing, backup strategies, secret rotation, or incident response for web projects. Not for mobile apps, desktop software, CLI tools, or games.