Total 34,549 skills
Showing 12 of 34549 skills
ACI PAY.ON integration. Manage data, records, and automate workflows. Use when the user wants to interact with ACI PAY.ON data.
Toolset integration. Manage data, records, and automate workflows. Use when the user wants to interact with Toolset data.
Everee integration. Manage Companies. Use when the user wants to interact with Everee data.
Read and summarize an existing codebase before any design or implementation work begins. Use as a prerequisite when the project is not greenfield.
Manage Dokploy infrastructure: projects, applications, databases, domains, compose services, deployments, and servers via the Dokploy REST API. Use whenever the user mentions dokploy, deploying apps, managing servers, creating databases, adding domains, docker compose deployments, checking deployment status/logs, or any PaaS infrastructure management. Even if 'dokploy' isn't mentioned explicitly, trigger when the context involves their self-hosted deployment platform.
Write the minimal production code needed to make all existing failing tests pass. No extra features, no test modifications, no refactoring. Use after tests are written and confirmed failing.
Automatically injects the project's extracted design soul into any frontend task. Use this skill on EVERY request that involves building, editing, or reviewing UI — including components, pages, layouts, styles, animations, and design decisions. Triggers on: any prompt containing words like "build", "create", "make", "design", "component", "page", "layout", "button", "form", "card", "nav", "header", "modal", "style", "css", "tailwind", "animate", "responsive", "ui", "frontend", "screen", "dashboard", "landing", "section", or any request to write JSX, TSX, HTML, or CSS. Do NOT trigger on backend-only tasks, database queries, API routes with no UI, or pure logic/utility functions with no visual output. This skill has no slash command — it runs silently in the background on every frontend task. The user never needs to invoke it manually.
Create detailed phase plan (PLAN.md) with verification loop
Write test files driven by acceptance criteria in strict TDD mode. No production code is generated. Use after the low-level design is approved.
Produce a detailed low-level design with API contracts, data models, error handling, test strategy, and dependency version policy. Use after the high-level design is approved.
Spatial organization of knowledge in navigable directories
Navigate the SLDD (Spec Loops Driven Development) process and choose the correct skill for the current stage. Use when starting a new feature or when unsure which step comes next.