Loading...
Loading...
Found 6,147 Skills
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.
Npm integration. Manage data, records, and automate workflows. Use when the user wants to interact with Npm data.
Beacon integration. Manage data, records, and automate workflows. Use when the user wants to interact with Beacon data.
Google Cloud Dataflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Cloud Dataflow data.
Affinda integration. Manage data, records, and automate workflows. Use when the user wants to interact with Affinda 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.
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".
Tomba integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tomba data.
Ikas integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ikas data.
Faraday integration. Manage data, records, and automate workflows. Use when the user wants to interact with Faraday data.
Create new skills, modify and improve existing skills. Use when users want to create a skill from scratch, edit or optimize an existing skill, turn a workflow into a reusable skill, or improve a skill's description for better triggering.