Loading...
Loading...
Found 39 Skills
Universal Assistant — Automatically analyzes scenarios, takes inventory of ECC resources, intelligently routes to the optimal agent pipeline, and completes complex workflows with one click.
Shows the Wasp plugin's available features, commands, and skills.
Cloudflare Workers local development with Wrangler, Miniflare, hot reload, debugging. Use for project setup, wrangler.jsonc configuration, or encountering local dev, HMR, binding simulation errors.
Prompt for generating an AGENTS.md file for a repository
Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)
Orchestrates end-to-end software development using the addyosmani/agent-skills framework. Guides the user through define → plan → build → verify → review → ship phases, spawns subagents for each step, tracks state persistently, and never loses focus on workflow completion. Use when the user says "let's build X", "help me implement X", "walk me through X", or wants structured multi-phase dev guidance. Also triggers when a task is clearly non-trivial and would benefit from phased execution.
The root entry of the CodeStable workflow family — introduces the overall system to users and routes users' specific requests to the correct cs-* sub-skills. Trigger scenarios: users only input `cs` / `/cs`, say "introduce codestable", "do something with codestable", "I want to do X, which skill should I use", "don't know which one to use", or users' described requests are open-ended (e.g., "start working") and haven't converged to a specific sub-skill. This skill itself **does not perform actual tasks** — it doesn't write specs, write code, or read/write content products in the codestable/ directory — it only performs scanning, routing, prompting, and then transfers control to the target sub-skill.
Use when the user wants to manage the dev server — setup, start, stop, restart, or check status.
Set up complete GitHub Copilot configuration for a new project based on technology stack
Use when the user asks to "plan this feature", "plan refactor", "research & plan", "plan auth/API/work", or needs multi-step work with evidence-based planning before coding. Understands → Researches (via Local Search/Research) → Plans → Implement. No guessing; validates with code.
Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.
Execute a single task from a Jira task plan using a structured pipeline of specialist subagents: planning, testing, refactoring, implementation, documentation, code-quality review, architecture review, security audit, and requirements verification. The user must specify which task number to execute. Use when the user says "execute task 3", "work on task 2", "implement task 1", "start task 5 for PROJECT-1234", or "run task N". Also triggered by the orchestrating-jira-workflow skill as Phase 5 of the end-to-end pipeline (called once per task). Requires that the task plan exists at docs/<TICKET_KEY>-tasks.md. Executes ONLY the specified task — never continues to the next one without explicit user approval.