Topic: workflow-automation
917 skills in this topic.
-
ring:dependency-mapping
Cross-project dependency mapping and analysis skill for identifying, tracking,
and managing dependencies across portfolio projects.
LerianStudio/ring 169
-
ring:systemplane-migration
Gate-based systemplane migration orchestrator. Migrates Lerian Go services from .env/YAML-based configuration to the systemplane — a database-backed, hot-reloadable runtime configuration and settings management plane with full audit history, optimistic concurrency, change feeds, component-granular bundle rebuilds, and atomic infrastructure replacement. Requires lib-commons v4.3.0+.
LerianStudio/ring 169
-
ring:visual-explainer
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
LerianStudio/ring 169
-
ops-migration-planning
Structured workflow for infrastructure migration planning including cloud migrations,
technology upgrades, and data center transitions.
LerianStudio/ring 169
-
delivery-reporting
Delivery reporting skill for creating visual executive presentations of squad deliveries
(engineering, product, design). Analyzes Git repositories to extract business value from
technical changes and generates HTML slide presentations with customizable visual identity.
LerianStudio/ring 169
-
ring:dev-validation
Development cycle validation gate (Gate 5) - validates all acceptance criteria are met
and requires explicit user approval before completion.
LerianStudio/ring 169
-
ring:using-ring
Mandatory orchestrator protocol - establishes ORCHESTRATOR principle (dispatch agents,
don't operate directly) and skill discovery workflow for every conversation.
LerianStudio/ring 169
-
ops-incident-response
Structured workflow for production incident management following SRE best practices.
Covers incident declaration, triage, coordination, resolution, and post-mortem.
LerianStudio/ring 169
-
ring:using-pm-team
12 pre-dev workflow skills + 4 research agents organized into Small Track (4 gates, <2 days) and
Large Track (9 gates, 2+ days) for systematic feature planning with research-first approach.
LerianStudio/ring 169
-
ux-states-audit
Audit UI code for missing loading states, empty states, and error states. Every async operation and data-driven UI must handle all three. Finds gaps and implements the missing states using the app's existing patterns.
markmdev/meridian 146
-
planning
Interview-driven planning methodology that produces implementation-ready plans. Always use this skill INSTEAD of EnterPlanMode — it provides structured interviewing (20-40 clarifying questions), exhaustive parallel codebase exploration (5-15 Explore agents), verbatim requirements capture, and automated plan validation via plan-reviewer (must score 9+). Use for new features, refactoring, architecture changes, migrations, or any non-trivial implementation work.
markmdev/meridian 146
-
observability-audit
Audit code for observability gaps — debug logs left in, errors caught without being logged, missing context on log entries, untracked slow operations. Uses the app's existing observability tooling exclusively.
markmdev/meridian 146
-
error-audit
Audit code for silent error swallowing, fallbacks to degraded alternatives, backwards compatibility shims, and UI that fails to show errors to the user. Finds and fixes all occurrences in the specified scope.
markmdev/meridian 146
-
create-docs
Create or update .meridian/docs/ knowledge files for a module or directory. Produces reference docs with frontmatter for context routing.
markmdev/meridian 146
-
add-frontmatter
Scan all .md files in the project and add or fix YAML frontmatter (summary + read_when) so they can be discovered by context routers like Reflex.
markmdev/meridian 146
-
writing-skills
Use when creating, editing, or validating Cursor custom skills, especially when deciding where they should live, how they should be named, and how to describe when they apply.
6BNBN/FlowPilot 127
-
systematic-debugging
Use when diagnosing a bug, failing test, build issue, or unexpected behavior in Cursor before proposing a fix. Focus on reproducing the issue, tracing the cause, and validating the repair.
6BNBN/FlowPilot 127
-
subagent-driven-development
Use when executing a larger plan in Cursor with parallel or delegated work, while keeping tasks narrowly scoped and reviewed between steps.
6BNBN/FlowPilot 127
-
playwright
6BNBN/FlowPilot 127
-
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
6BNBN/FlowPilot 127
-
finishing-a-development-branch
Use when implementation work is done and you need to decide how to finish it in Cursor, such as keeping the branch, merging locally, creating a pull request, or cleaning up temporary workspaces.
6BNBN/FlowPilot 127
-
feature-dev
Use when building a new feature or substantial behavior change in Cursor and the user wants a structured workflow from discovery through implementation and review.
6BNBN/FlowPilot 127
-
executing-plans
Use when a written implementation plan already exists in Cursor and the next step is to execute it in small batches with checkpoints and verification.
6BNBN/FlowPilot 127
-
dispatching-parallel-agents
Use when facing two or more independent tasks in Cursor that can be investigated or executed in parallel without conflicting edits or shared state.
6BNBN/FlowPilot 127