with one click
universal-mcp-sync
universal-mcp-sync contains 12 collected skills from nawodyaishan, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use when adding a new MCP server provider to usync. Triggers: "add a new provider", "add provider X", "scaffold provider", "support <NAME> MCP", "register an MCP server". Walks through official doc lookup, scaffolding, registration, header dispatch, QA scenarios, and documentation updates.
PROJECT-SPECIFIC to usync (mcp-config-tui). Use when iterating on TUI UI/UX bugs via the Docker-first bug-hunt harness. Triggers: "UX bug hunt", "iterate on UI bugs", "fix UX issues", "expand the matrix", "ux-fake-prod", "matrix scenario", "TUI regression", "DM-P<n>". Drives the 4-stage loop (expand → run → triage → fix+lock) and the lens framework for catching UX defect classes beyond functional bugs.
Review an SDD implementation plan before code generation and decide whether it is approved, needs changes, or is rejected.
Initialize or upgrade a repository for production spec-driven development with constitution, templates, review checklists, and tool memory pointers.
Detect spec drift, prepare release notes, and write retrospectives after SDD implementation or review.
Implement one approved SDD task inside strict file, safety, and verification boundaries.
Produce a technical implementation plan from an approved SDD spec without editing product code.
Create or improve spec-driven development artifacts using local source docs plus current Exa research. Use for SDD planning, gap analysis, documentation upgrades, architecture specs, task breakdowns, and docs-only preparation before implementation.
Route spec-driven development work to the correct phase skill. Use when the user asks for SDD, spec-driven development, Spec Kit style workflow, feature planning, implementation from specs, verification, or spec drift review.
Create or refine SDD feature, bug-fix, refactor, or migration specifications with clarification handling before technical planning.
Break an approved SDD plan into small, bounded, independently verifiable implementation tasks.
Verify implementation and review code against the approved SDD spec, plan, tasks, contracts, and constitution.