Loading...
Loading...
Found 5,021 Skills
Amazon Sagemaker integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon Sagemaker data.
1CRM integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1CRM data.
ClickFunnels integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClickFunnels data.
Amazon Cognito integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon Cognito data.
Async Interview integration. Manage data, records, and automate workflows. Use when the user wants to interact with Async Interview data.
Azure AI Vision integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure AI Vision data.
Percy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Percy data.
OnTask integration. Manage data, records, and automate workflows. Use when the user wants to interact with OnTask data.
Phase 1 of the feature workflow — Draft a design document for the new feature, serving as the sole input for subsequent implementation and acceptance. First gather evidence (read architecture docs, review relevant code, grep to prevent term conflicts, check archives), then write a complete first draft in one go (including YAML frontmatter + three-tier structure + test design), submit it to the user for overall review, and iterate until approval. After approval, extract {slug}-checklist.yaml from {slug}-design.md for use in the next two phases. Trigger scenarios: "Start designing the solution", "Write design doc", "Prepare to implement XX", with the prerequisite that you already know what to do, who it's for, and how to define success.
Phase 3 of the feature workflow – Complete the acceptance closed-loop. Four tasks: 1. Check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; fix any deviations on the spot instead of just "noting them" in the report. 2. Incorporate this feature into the project's overall architecture documentation. 3. If this feature changes the user story or boundaries of the corresponding requirement, update the requirement doc accordingly. 4. If this feature originated from a roadmap item, change the status of the corresponding entry in roadmap items.yaml to done and sync it with the main document. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Prerequisite: cs-feat-impl is completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".
Background knowledge for droid-control workflows -- not invoked directly. Recording lifecycle for terminal and browser sessions.
Tomba integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tomba data.