Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

tdd-generator

Sterne1

Forks0

Aktualisiert1. April 2026 um 08:03

Test-driven workflow for unit, component, and E2E testing. Enforces Red-Green-Refactor and generates the right test type for changed code.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

materialofair

materialofair/claudecode-omc

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	tdd-generator
description	Test-driven workflow for unit, component, and E2E testing. Enforces Red-Green-Refactor and generates the right test type for changed code.

TDD Generator

Use this skill to drive implementation through tests first.

Workflow

Detect target type:
- Pure logic -> unit tests
- UI behavior -> component/integration tests
- User journeys -> E2E tests
RED:
- Write failing test first
GREEN:
- Implement minimal code to pass
REFACTOR:
- Improve structure while keeping tests green
Add regression cases for discovered bugs and edges.

Recommended Stack

Unit/component: Vitest + Testing Library
E2E: Playwright

E2E Agent Option

For large journey suites, you can run Playwright test agents:

npx playwright test --init-agents
npx playwright test --agent=planner
npx playwright test --agent=generator
npx playwright test --agent=healer --repeat

Quality Rules

Test behavior, not private implementation details.
Prefer semantic queries (getByRole, getByLabelText) for UI tests.
Keep one assertion intent per test case.
Add explicit edge cases and failure-path coverage.

References

Playwright best practices: https://playwright.dev/docs/best-practices
Vitest guide: https://vitest.dev/guide/

Mehr aus diesem Repository

gleiches Repository

prompt-pilot

materialofair/claudecode-omc

Optimize a rough prompt with an independent subagent, present several CONCISE ready-to-run variants for the user to pick or edit, then EXECUTE the chosen prompt directly in the current session. Unlike prompt-optimizer (advisory only — it just hands back text), prompt-pilot closes the loop: optimize → choose → run. TRIGGER when the user wants both optimization AND execution: "优化并执行", "优化提示词后直接做", "优化指令然后执行", "帮我把这个需求优化好再做", "optimize and run my prompt", "improve this prompt then do it", "refine my prompt and execute it", or when the user explicitly invokes /prompt-pilot. DO NOT TRIGGER when the user only wants advice/text back with no execution ("优化prompt", "改进prompt", "rewrite this prompt", "how to write a prompt for") — that is prompt-optimizer. DO NOT TRIGGER for "优化代码" / "优化性能" / "optimize this code" / "optimize performance" — those are refactoring or performance tasks. DO NOT TRIGGER when the user says "直接做" / "just do it" with no request to optimize — execute the task normally without this skill.

2026-06-291

prompt-optimizer

materialofair/claudecode-omc

Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite this prompt", or explicitly asks to enhance prompt quality. Also triggers on Chinese equivalents: "优化prompt", "改进prompt", "怎么写prompt", "帮我优化这个指令". Specially handles short Chinese bug reports (the dominant real-world use case): runs Bug Report Triage to extract repro/expected/actual/environment, asks up to 3 clarifying questions if ≤ 2 fields are present, and inserts systematic-debugging as a hard prerequisite before any code change. DO NOT TRIGGER when: user wants the task executed directly, or says "just do it" / "直接做". DO NOT TRIGGER when user says "优化代码", "优化性能", "optimize performance", "optimize this code" — those are refactoring/performance tasks, not prompt optimization (unless the user exp

2026-06-101

swiftui-expert-skill

materialofair/claudecode-omc

Use when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management, view composition, performance, Liquid Glass adoption, or Instruments `.trace` capture/analysis for hangs, hitches, CPU hotspots, or excessive view updates.

2026-05-191

h5-to-swiftui

materialofair/claudecode-omc

Convert an H5 / web app's source into a native SwiftUI iOS app by native rewrite (NOT a WebView shell, NOT a transpiler). Use when the user wants to port, re-implement, or migrate a web/H5 frontend to native SwiftUI with high visual fidelity, asks to "turn this web app into a real iOS app", or wants a measured render-diff convergence loop against a browser baseline. Auto-detects the web stack (v1: vanilla + React; other stacks are detected then gated, not guessed), extracts design tokens, calibrates a cross-renderer fidelity floor, rewrites per component, and drives a bounded render→diff→correct loop that reports a quantified visual residual plus an independent judge verdict. It does NOT promise literal pixel-identity: cross-renderer differences impose a measured floor it reports honestly. Triages canvas/WebGL/complex-animation/3rd-party-SDK/backend surfaces instead of silently emitting wrong code.

2026-05-191

conductor-distill

materialofair/claudecode-omc

Distill methodology from superpowers and BMAD-METHOD docs into the active conductor track's spec.md / plan.md / review.md as intent-layer overlays. Use when user asks to "distill superpowers into conductor", "把 superpowers/bmad 提炼到 conductor", "import method docs to track", "seed conductor with brainstorming/TDD/verification gates", or "feed BMAD PRD/architecture/story/QA principles into the track". Writes only inside marker blocks so it never competes with code-derived facts and re-runs cleanly. DO NOT use for general superpowers invocation, code refactors, or to summarize this codebase.

2026-05-091

de-ai-writing

materialofair/claudecode-omc

Humanize PROSE drafts — articles, blog posts, public-account 公众号 copy, marketing copy, sermons, technical write-ups — that read like an LLM produced them. Chinese-first, supports zh/en mixed text. Cross-checks output against the Wikipedia "Signs of AI writing" taxonomy before delivery. TRIGGER when user asks to remove AI tone or humanize TEXT/DRAFT/ARTICLE/COPY/稿/文章/帖子: "去 AI 味", "去ai味", "降低机器感", "改得像真人写的", "不要 AI 腔", "humanize this draft", "humanize this article", "remove AI tone", "de-ai this writing". DO NOT TRIGGER for code cleanup, dead-code removal, AI-generated source code, or "deslop" of codebases — those belong to ai-slop-cleaner. DO NOT TRIGGER for prompt optimization — that is prompt-optimizer.

2026-04-291

name	tdd-generator
description	Test-driven workflow for unit, component, and E2E testing. Enforces Red-Green-Refactor and generates the right test type for changed code.

TDD Generator

Use this skill to drive implementation through tests first.

Workflow

Detect target type:
- Pure logic -> unit tests
- UI behavior -> component/integration tests
- User journeys -> E2E tests
RED:
- Write failing test first
GREEN:
- Implement minimal code to pass
REFACTOR:
- Improve structure while keeping tests green
Add regression cases for discovered bugs and edges.

Recommended Stack

Unit/component: Vitest + Testing Library
E2E: Playwright

E2E Agent Option

For large journey suites, you can run Playwright test agents:

npx playwright test --init-agents
npx playwright test --agent=planner
npx playwright test --agent=generator
npx playwright test --agent=healer --repeat

Quality Rules

Test behavior, not private implementation details.
Prefer semantic queries (getByRole, getByLabelText) for UI tests.
Keep one assertion intent per test case.
Add explicit edge cases and failure-path coverage.

References

Playwright best practices: https://playwright.dev/docs/best-practices
Vitest guide: https://vitest.dev/guide/