duc01226/EasyPlatform - Page 2

figma-design

[Frontend] Use when you need to extract design context from Figma URLs via MCP, REST API, or screenshot fallback.

fix

[Implementation] Use when you need to analyze and fix issues [INTELLIGENT ROUTING]. Flag: --target={ci|issue|logs|test|types|ui} scopes the fix; --target=types resolves TypeScript errors inline.

frontend-design

[Frontend] Use when you need to create distinctive, production-grade frontend interfaces with high design quality.

git-conflict-resolve

[Git] Use when you need to resolve git merge/cherry-pick/rebase conflicts with backup, analysis, and reporting.

git-developer-performance

[Git] Use when generating developer KPI, performance, contribution value, story point, man-day, or code-quality reports from local git commit history.

git-merge

[Git] Use when you need ⚠️ Merge code from one branch to another.

graph-blast-radius

[Code Intelligence] Use when you need to analyze the blast radius of current code changes using the structural knowledge graph.

graph-build

[Code Intelligence] Use when you need to build, update, or sync the code review knowledge graph. Flag: --scope={full|update|sync} (default auto-detect); --scope=full forces a full rebuild, --scope=update re-parses uncommitted working-tree changes,…

graph-connect-api

[Code Intelligence] Use when you need to detect frontend-to-backend API connections using the knowledge graph.

graph-export

[Code Intelligence] Use when you need to export the code review knowledge graph. Flag: --format={json|mermaid} (default json); --format=json dumps the full graph to a JSON file, --format=mermaid renders a single file as a Mermaid flowchart diagram.

graph-query

[Code Intelligence] Use when you need to query code relationships and connections using the structural knowledge graph.

graph-trace

[Code Intelligence] Use when investigating what happens when code executes, understanding blast radius, or tracing frontend-to-backend flows.

greenfield

[Planning] Use when you need to start a new project from scratch with full waterfall inception — idea, research, domain modeling, tech stack, and implementation plan.

harness-setup

[Quality] Use when setting up an agent quality harness with feedforward guides and feedback sensors.

idea

[Project Management] Use when capturing new ideas, feature requests, or concepts for future refinement.

integration-test-review

[Code Quality] Use when you need to review integration tests for assertion quality, bug protection, repeatability, and test-spec traceability — AND verify the review target (changed production code) has test coverage (integration-first) with spec↔test↔code…

integration-test

[Testing] Use when you need to generate or review integration tests.

integration-test-verify

[Testing] Use when you need to verify integration tests pass after writing and reviewing them.

interface-design

[Frontend] Use when you need interface design for product UIs — dashboards, admin panels, SaaS apps, tools.

investigate

[Fix & Debug] Use when you need to investigate and explain how existing features or logic work. Flag: --mode=explain produces a one-way developer-narrative explanation (Purpose → How → Why → Impact) tuned by coding level; use /understand for the standalone…

journal

[Utilities] Use when recording an engineering journal entry — capture decisions, blockers, lessons, or progress notes during work.

knowledge-review

[Research] Use when you need to review knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.

knowledge-synthesis

[Research] Use when you need to synthesize research findings into structured report using template.

learn

[Utilities] Use when you need to teach Claude lessons that persist across sessions.

lint

[Code Quality] Use when you need to run linters and fix issues for backend or frontend.

linter-setup

[Quality] Use when you need to research and configure code quality tooling for any tech stack — linters, formatters, static analysis, pre-commit hooks, and CI gates.

llm-council

[Decision Support] Use when pressure-testing irreversible, high-stakes decisions with adversarial AI advisors.

markdown-novel-viewer

[Content] Use when you need background HTTP server rendering markdown files with calm, book-like reading experience.

markdown-to-docx

[Document Processing] Use when you need to convert markdown files to Microsoft Word ( DOCX) format with GFM support and math rendering.

markdown-to-pdf

[Document Processing] Use when you need to convert markdown files to PDF with syntax highlighting and custom CSS support.

market-analysis

[Research] Use when you need to analyze market landscape: competitors, sizing (TAM/SAM/SOM), trends, SWOT, customer segments.

memory-management

[Utilities] Use when saving or recovering task progress across sessions via file checkpoints — especially before context compaction.

package-upgrade

[Code Quality] Use when the user asks to analyze package upgrades, check for outdated dependencies, plan npm/NuGet updates, or assess breaking changes in package updates.

pbi-challenge

[Code Quality] Use when you need an AI-assisted Dev BA PIC review of PBI drafts.

pbi-mockup

[Project Management] Use when you need to generate an HTML mockup report from PBI and story artifacts.

pdf-to-markdown

[Document Processing] Use when you need to convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR).

performance-review

[Debugging] Use when analyzing or optimizing performance bottlenecks: database queries, N+1 fan-out, indexing, API latency, memory, concurrency, algorithmic complexity (O(n²)), frontend rendering, caching, and distributed paths.

plan-analysis

[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.

plan-execute

[Implementation] Use when you need to start coding & testing an existing plan. Flags: --approval=off (auto/trust mode, no approval gate), --tests=off (skip the test step), --parallel (parallel phase execution via subagents).

plan-review

[Planning] Use when you need to auto-review a plan for validity, correctness, and best practices — recursive: review, validate findings with why-review, fix validated findings, full re-review until no findings.