amo-tech-ai/mdeapp

linear-claude-skill

DEPRECATED — use the `linear` skill instead. "Manage Linear issues, projects, and teams"

linear-create

DEPRECATED — use the `linear` skill instead. Create Linear issues. Use when creating bugs, tasks, or feature requests.

linear-documents

DEPRECATED — use the `linear` skill instead. Manage Linear documents. Use for creating and viewing documentation.

linear-labels

DEPRECATED — use the `linear` skill instead. Manage Linear labels. Use when creating, listing, or deleting labels.

linear-metrics

DEPRECATED — use the `linear` skill instead. View Linear metrics. Use for velocity, burndown, and progress tracking.

linear-milestones

DEPRECATED — use the `linear` skill instead. Manage project milestones - create, update, track target dates. Use when planning project deliverables.

linear-pm

DEPRECATED — use the `linear` skill instead. Linear project management - issues, projects, cycles, and roadmaps. Use for Linear-related tasks like managing issues, tracking sprints, and organizing projects.

linear-pr

DEPRECATED — use the `linear` skill instead. Create GitHub PRs linked to Linear issues. Use when creating pull requests, pushing code for review, or linking PRs to Linear issues.

linear-projects

DEPRECATED — use the `linear` skill instead. Manage Linear projects - full CRUD with labels, members, archive. Use when managing projects.

linear-relations

DEPRECATED — use the `linear` skill instead. Manage Linear issue relationships. Use for blocking, parent/child, duplicates.

linear-roadmaps

DEPRECATED — use the `linear` skill instead. View Linear roadmaps. Use when viewing roadmap planning.

linear-search

DEPRECATED — use the `linear` skill instead. Search Linear issues and projects. Use when finding issues, looking up bugs, or searching the backlog.

linear-sprint

DEPRECATED — use the `linear` skill instead. Sprint planning and analytics - status, progress, burndown, velocity, carry-over. Use when managing sprints.

linear-statuses

DEPRECATED — use the `linear` skill instead. View and manage workflow states. Use when checking or configuring issue statuses for a team.

linear-tools

DEPRECATED — use the `linear` skill instead. "Linear project management expert for issues, cycles, projects, and workflow automation"

linear-triage

DEPRECATED — use the `linear` skill instead. Manage Linear triage inbox. Use for unassigned issues needing attention.

linear-update

DEPRECATED — use the `linear` skill instead. Update Linear issues. Use when changing status, priority, assignee, or labels.

linear-views

DEPRECATED — use the `linear` skill instead. Manage custom views - create, list, apply saved views. Use when working with saved issue filters.

linear-workflow

DEPRECATED — use the `linear` skill instead. Start/stop work on Linear issues. Use when beginning work, creating branches, or getting current issue context.

mde-linear

DEPRECATED — use the `linear` skill instead. mdeai Linear operations — create/update issues, cycles, milestones, and status updates for the sanjiovani workspace. Use whenever the user mentions Linear, SAN-###, Linear issues, cycles, milestones, initiative…

task-verifier

Forensic verifier for mdeai task specs (tasks/core/F*.md) and audit reports (tasks/audit/*.md). Use whenever the user asks to "verify a task", "is this task 100% correct", "audit the audit", "is this safe to execute", "did this task really ship", "check if X…

testing

mdeai testing: Vitest, Playwright, browser MCP, smoke, CI, evals. Use routing table. NOT for: TDD-only workflow (test-driven-development), MCP server failures (troubleshooting), dedicated load-test design.

mde-worktree-pr-flow

Use for worktrees, PRs, shipping, and cleanup. Enforces "small branch → focused PR → tested → merged → deployed → verified → next branch" — one worktree, one goal, one PR, merge gate (lint/build/test/floor/Vercel/prod), PR size limits, and forensic cleanup…

lean-dev-flow

Lean implementation loop for mdeapp (SAN-NNN) tasks. Use this skill whenever starting implementation of any Linear issue, choosing which tests to run, setting up or cleaning up a worktree, or when mde-task-lifecycle phases 3–4 feel heavy for the change at…

mastra

Mastra framework: docs lookup (links.md, mastraDocs MCP, embedded docs), agents, workflows, streaming, browser, tools, memory, RAG, processors, CopilotKit guide. Verify from installed docs — never trust training-data APIs. NOT for: product intent routing…

mde-maps

mdeai Google Maps: Places (New), ChatMap, Gemini grounding, MCP tools, keys, Mastra maps. Quick routing; legacy `google-maps` name archived (see `_archive/2026-05-14`). NOT for: Mapbox-only, pure GIS math, non-Google stacks, generic off-repo tutorials.

mde-real-estate

Orchestrator for real-estate work on mdeai.co — V1 marketplace product, V2 MLS technical playbook, industry context, plus 3 specialized sub-agents (lead qualifier, neighborhood guide, property description). Use when building real-estate features, writing…

mde-supabase

mdeai Supabase: DB, RLS, Auth, Edge Functions, Realtime, Storage, vectors, migrations, pgvector. Use for ANY Supabase work on this repo — schema changes, RLS policies, edge function deploy/debug, auth.uid(), service role, supabase-js, Realtime channels,…

mde-task-lifecycle

Five-phase orchestrator for mdeai.co tasks — plan, research, implement, test, ship. Routes each phase to specialist skills (mde-writing-plans, testing for Vitest/Playwright, `/deploy-check` for pre-ship gates, mdeai-executor) and owns boundaries between them.…

mde-vercel

Orchestrator for Vercel platform work — deploy operations (`vercel deploy`, preview/production, rolling releases, environment variables, domain config, deployment troubleshooting) and React/Next.js performance best practices from Vercel Engineering (Server…

mde-example

TEMPLATE — not a real skill. Copy this folder to `.claude/skills/mde-<domain>/` and remove `disable-model-invocation`. One-line WHAT + WHEN + at least 6 trigger phrases users would actually say. Trigger when the user says "phrase A", "phrase B", "phrase C",…

dashboard-form-ui

Create or modify forms in admin or vendor dashboards in the Mercur basic starter using stable form structure, validation, submission guards, and dashboard UI conventions.

dashboard-page-ui

Create or modify pages in admin or vendor dashboards in the Mercur basic starter using correct routing, page composition, i18n, and dashboard UI conventions.

dashboard-tab-ui

Create or modify tabbed workflows in admin or vendor dashboards in the Mercur basic starter using stable tab structure, validation scope, and i18n-aware wizard conventions.

medusa-ui-conformance

Keep custom admin and vendor UI in the Mercur basic starter aligned with local wrappers and @medusajs/ui. Use when adding reusable UI, interactive primitives, overlays, menus, selectors, or custom dashboard components.

mercur-blocks

Discover, evaluate, install, and verify Mercur blocks in the basic starter using `blocks.json` aliases and CLI workflows.

mercur-cli

Use Mercur CLI commands correctly inside a project created from the Mercur basic starter. Use when choosing between `create`, `init`, `add`, `search`, `view`, and `diff`.

migration-guide

Analyze a Mercur 1.x project and guide migration to 2.0. Self-contained — works without access to the mercur monorepo.