Prompts tagged "工作流" in the PromptCraft library.
A two-platform workflow: generate the main track in Suno, then fine-tune in Udio — use inpainting to select the 2 seconds where the enunciation is muddy or off-key, and regenerate only that section instead of re-rolling the whole song.
A workflow mindset office workers can copy directly. Complex tasks (writing a proposal, building a report) done in one giant prompt come out poorly; this teaches you to split it into four steps — outline → expand each section → proofread and polish → convert to bullet points — with the output of each step feeding the next, plus four ready-to-use Traditional Chinese prompts. You can even change direction mid-task by rerunning just one step instead of starting over.
Turn messy source material like meeting notes and report paragraphs into a slide outline formatted 'one point per page, separated by ---,' ready to paste straight into Gamma or Canva AI to produce a deck. Page titles are forced into statements of insight rather than labels, the conclusion goes on page two, and it comes with a 30-second opening script.
Brings obra/superpowers' "spec-first + true red-green TDD" development discipline into your agent: brainstorm to clarify requirements first, break the work into verifiable 2-5 minute tasks, then strictly follow RED-GREEN-REFACTOR, with a two-stage subagent review.
Uses cc-sdd's --codex-skills install to load reusable skills (SKILL.md) into Codex CLI on demand, and replicates its /kiro-impl autonomous execution loop — a fresh implementer per task, an independent reviewer, and automatic root-cause debugging on failure — so Codex advances steadily through a task list one task at a time.
Uses codex exec's non-interactive execution plus a restricted sandbox to plug Codex CLI into CI / scripted workflows for unattended tasks like lint fixes, batch refactors, and auto-repair, guarding the safety boundary with approval_policy=never paired with a workspace-write sandbox.
GitHub's official open-source tool for Spec-Driven Development. Using /speckit.specify → /plan → /tasks → /implement, it turns a vague requirement into an executable specification end to end, then has the AI generate code from that spec — fixing the unpredictability of 'vibe coding.'
Uses two Markdown templates (create-prd.md and generate-tasks.md) to turn 'dumping a pile of requirements on AI' into a controlled process: first generate a PRD, break it into a checkable task list, then complete one subtask at a time — pausing after each for your go-ahead before continuing.
An advanced workflow: generate two keyframes with Nano Banana first, then hand them to Veo to interpolate into a fully realized camera move.