ezpowers

Plugin ezpowers from marketplace ezpowers-dev in dlwlgus9125/EZPowers. Commands read from the repo's manifest — 26 days ago.

Skills (14)

• codebase-design

  Design or improve a module interface, choose a seam, reduce shallow abstractions, and make product code more testable and AI-navigable using deep-module vocabulary. Use for focused module or refactor design, interface alternatives, dependency placement, and test-surface decisions; not for a whole-co

• deep-interview

  Use when a user's request is vague, underspecified, solution-shaped, or explicitly asks for deep-interview, requirement clarification, "grill me", or "그릴미". Resolve stated ambiguity and consequential blind spots into a confirmed, decision-ready request, then offer to proceed, correct, or finish with

• design-architecture

  Use when a project needs durable architecture, boundary, data-flow, deployment, or verification-design decisions before a feature spec is written. Not for implementing code or for general request clarification.

• diagnose

  Reproduce the user's exact symptom with a command observed red before hypothesizing or changing product behavior, then root-cause, fix, and verify bugs, failing tests or builds, integration failures, flaky behavior, performance regressions, and unexpected results. Use when the user invokes diagnose

• execute

  Use when a validated EZPowers plan should be implemented with host-native editing and orchestration, then verified and certified by the project-local runtime.

• explain-with-evidence

  Structure user-facing explanations and work-result reports in the user's active conversational language, grounded in observed evidence and honest limits. Use when explaining completed work, technical decisions, knowledge, concepts, numbers, or rationale beyond a one-line confirmation or status updat

• frontend-design

  Use when frontend, UI, UX, design system, screen structure, component taxonomy, design tokens, responsive behavior, accessibility, or visual QA decisions must be settled before implementation. Not for directly coding UI.

• harness-chain

  Use only when the user explicitly asks to configure or run the project-local EZPowers harness chain for unattended, evidence-gated software or planning-deliverable work. Not for ordinary execute runs, generic planning, or silently adding orchestration to a project.

• hud

  Use when the user asks to enable, configure, inspect, repair, or remove a global Codex model and usage HUD or statusline without installing a project harness.

• improve-codebase-architecture

  Explicitly scan existing product code for evidence-backed deep-module opportunities, render a safe offline report, and explore one user-selected refactor without implementing it. Use for broad maintenance discovery of shallow modules, scattered policy, leaky seams, repeated orchestration, and hard-t

• prepare-execute

  Use when a valid EZPowers feature spec must be mapped into a dependency-valid implementation plan with exact project-local checks and complete criterion coverage. Not for implementing the plan.

• setup

  Use when the user explicitly asks to initialize, install, repair, refresh, or bootstrap repository documentation with EZPowers project-local workflow tooling.

• spec

  Use when settled decisions must be written as a project-local feature acceptance contract with traceable, machine-verifiable criteria. Not for interviewing an ambiguous request or implementing code.

• wiki

  Use when the user asks to capture, search, inspect, promote, refresh, lint, or prune EZPowers project-local session knowledge.

Similar plugins