duc01226/EasyPlatform - Page 4

story

[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.

strategy-builder

[Content] Use when you need to build marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.

sync-codex

[Codex] Use when you need to run the full Codex mirror sync + verify pipeline (migrate → hooks → context → verify) standalone, no npm/package JSON needed.

sync-skills-shared-protocols

[Skill Management] Use when shared protocol checklists change and need propagation across skills.

tech-stack-research

[Architecture] Use when you need to research, analyze, and compare tech stack options as a solution architect.

template-skill

[Category] Use when defining the standard skill description pattern.

test

[Testing] Use when you need to run tests locally and analyze the summary report.

test-ui

[Testing] Use when you need full-site QA audit (accessibility, performance, security, SEO) with visual reports.

threejs

[General] Use when building 3D web apps with ThreeJS and related WebGL or WebGPU examples.

ui-ux-pro-max

[Frontend] Use when designing beautiful or aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.

understand

[Process] Use when the developer wants something explained — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS…

watzup

[Utilities] Use when you need to review recent changes and wrap up the work.

web-design-guidelines

[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.

web-research

[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.

webapp-testing

[Testing] Use when you need individual page/component testing with Python Playwright scripts.

why-review

[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.

workflow-big-feature

[Workflow] Use when activating the Big Feature workflow for large or ambiguous research-driven feature work.

workflow-bugfix

[Workflow] Use when activating the Bug Fix workflow for systematic debugging with root cause investigation, fix, and verification.

workflow-code-to-spec

[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.

workflow-e2e

[Workflow] Use when activating the E2E testing workflow to generate, update, or maintain Playwright/E2E tests. Pick mode with --source={changes|recording|update-ui}.

workflow-end

[Process] Use when you need to end the active workflow and clear state.

workflow-feature

[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs…

workflow-feature-spec

[Workflow] Use when activating the Business Feature Documentation workflow for 8-section tech-free feature docs.

workflow-greenfield-init

[Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing.

workflow-idea-to-pbi

[Workflow] Use when activating the Idea to PBI workflow for turning an idea — or a raw product vision/problem — into prioritized PBIs and stories (single-PBI deep mode, or multi-opportunity discovery mode).

workflow-idea-to-spec

[Workflow] Use when activating the Idea-to-Spec workflow — turn a raw idea/vision/problem into ONE canonical (provisional) Feature Spec. STOPS at the reviewed spec; chain workflow-spec-to-pbi for a backlog. For code→spec use workflow-code-to-spec.

workflow-refactor

[Workflow] Use when activating the Code Refactoring workflow for restructure and improve existing code without changing behavior.

workflow-research

[Workflow] Use when activating the Research & Synthesis workflow — research a topic via web sources, then synthesize per --output={synthesis|business-eval|marketing|course} (knowledge report, business evaluation, marketing strategy, or course material).

workflow-review-changes

[Workflow] Use when activating the Review Current Changes workflow for review, fix, and re-review recursively until all issues resolved.

workflow-seed-test-data

[Workflow] Use when activating the Seed Test Data workflow for idempotent QC happy-path seeders.

workflow-spec-sync

[Workflow] Use when activating the Test Spec Update (Post-Change) workflow for update test specs and feature docs after code changes, bug fixes, or pr reviews.

workflow-spec-to-pbi

[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.

workflow-visualize

[Workflow] Use when activating the Visual Diagram workflow for create visual excalidraw diagrams from codebase investigation or web research.

workflow-write-integration-test

[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).

worktree

[Git] Use when you need to create isolated git worktree for parallel development.

architecture-design

[Architecture] Use when designing solution architecture across backend, frontend, deployment, monitoring, testing, and code quality.

ask

[Utilities] Use when you need to answer technical and architectural questions.

brainstorm

[Content] Use when you need to brainstorm as a PO/BA — structured ideation for problem-solving, new product creation, or feature enhancement.

branch-comparison

[Git] Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed.

business-analyst

[Project Management] Use when creating user stories, writing acceptance criteria, analyzing requirements, or mapping business processes.