Loading...
Loading...
Found 6,226 Skills
Unity 6 UI development guide. Use when building user interfaces, menus, HUD, buttons, or any UI elements. Covers UI Toolkit (recommended for new projects — USS, UXML, UI Builder, data binding), uGUI/Canvas (legacy runtime UI), and IMGUI. Based on Unity 6.3 LTS documentation.
Catlass Operator End-to-End Development Orchestrator. Based on ascend-kernel (csrc/ops), it connects catlass design, catlass-operator-code-gen and ascendc sub-skills to complete the closed loop from project initialization to documentation, precision, and performance. Keywords: Catlass, end-to-end, ascend-kernel, operator development, workflow orchestration.
Phase 2 of the feature workflow — Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and discuss with the user based on the plan, do not proceed forcefully.
Write application code that integrates with third-party tools via the Truto unified API. Covers API calls, webhook handlers, connection flows, and data access patterns for use in the user's codebase.
Truto API conventions — base URL (https://api.truto.one), Bearer auth, unified/proxy/custom URL patterns, cursor pagination, idempotency, admin filter syntax, and skill routing between `truto` (app code) and `truto-cli` (terminal). Load whenever calling, configuring, or reasoning about any api.truto.one endpoint.
Search patent databases and academic literature for prior art relevant to an invention. Use when user says "现有技术检索", "prior art search", "专利检索", "check patents", or wants to find relevant prior art.
Draft or update requirement documents under `codestable/requirements/` for the project — use **user stories + plain language** to describe a capability's "reason for existence, solution approach, and boundaries", so non-technical readers can quickly understand the highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or during the feature-design phase, it is found that there is no corresponding requirement for the capability to be implemented this time.
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Cloutboost platform help — gaming influencer marketing platform with 1.5M+ creator database across YouTube, Twitch, and TikTok, plus managed agency services. Covers Portal (influencer discovery, 20+ search filters, game-genre filtering), campaign management (outreach, scheduling, content review, approval), automated analytics and reporting, retargeting (repurposing influencer content for paid ads), and PR/media relations for game launches. Use when struggling to find the right gaming creators, Cloutboost campaign not getting enough creator applications, Portal search filters not narrowing results well, campaign reports hard to interpret, or unsure whether to retarget with influencer content. Do NOT use for influencer marketing strategy across platforms (use /sales-influencer-marketing), gaming marketing strategy (use /sales-gaming-marketing), general retargeting strategy (use /sales-retargeting), or PR strategy (use /sales-media-relations).
People.ai (now Backstory) platform help — automatic activity capture, deal intelligence, pipeline health, revenue forecasting, MCP integration, Salesforce/Dynamics/Oracle CRM sync. Use when reps aren't logging activities and CRM data is stale, deals are slipping without warning and you need early risk signals, forecast accuracy is poor because it's based on gut not data, evaluating People.ai vs Gong vs Clari vs Revenue.io for revenue intelligence, activity data isn't tying back to pipeline or revenue outcomes, or you want to connect People.ai to AI agents via MCP. Do NOT use for conversation intelligence with call recording and transcription (use /sales-gong or /sales-note-taker), building outbound sequences (use /sales-cadence), or general CRM data cleanup strategy (use /sales-data-hygiene).
NeoReach platform help — enterprise influencer marketing SaaS + managed services, 3M+ creator database with 40+ discovery filters, AI recommendation engine, fraud detection, campaign management (contracts, content tracking, payments), analytics (ROI, CPM, CPE, proprietary IMV metric), REST API (400+ data points, sponsorship pricing, audience matching, competitor spend), and optional managed campaign services. Use when NeoReach discovery isn't surfacing relevant creators, fraud scores look suspicious, campaign ROI or IMV numbers seem off, API integration isn't returning data, unsure whether to use managed services or self-serve, or need to compare NeoReach pricing with alternatives. Do NOT use for influencer marketing strategy across platforms (use /sales-influencer-marketing), TikTok marketing strategy (use /sales-tiktok-marketing), or gaming influencer marketing (use /sales-gaming-marketing).
Retargeting and remarketing strategy — website visitor retargeting, cart abandonment recovery, dynamic product ads, cross-channel retargeting, audience segmentation, frequency capping, attribution, pixel setup, in-app retargeting. Use when website visitors leave without converting, cart abandonment rates are too high, retargeting ads aren't profitable, you're unsure which retargeting platform to use, or past visitors never come back. Do NOT use for AdRoll-specific config (use /sales-adroll), Remerge-specific config (use /sales-remerge), email marketing (use /sales-email-marketing), B2B account-based advertising (use /sales-b2b-advertising), or general paid ads strategy (use /paid-ads).