Prompts tagged "開發工作流" in the PromptCraft library.
Has Claude Code scan your repo and produce a tight, verifiable CLAUDE.md project memory file under 200 lines—covering build/test/lint commands, directory structure, conventions, and prohibitions—while routing anything that doesn't belong there into skills or path-scoped rules instead.
Turns the checklist or multi-step process you re-paste every time into a custom slash command (.claude/commands/<name>.md, or the newer .claude/skills), with correct frontmatter, $ARGUMENTS parameters, live context pre-injected via `!cmd` (git diff, PR content), and permissions scoped down with allowed-tools.
Has Claude Code interview you about a repetitive manual process, then produce a fully-structured Agent Skill (SKILL.md) covering name/description/trigger conditions/step-by-step instructions/acceptance criteria/supporting references, and verify it can be triggered automatically as well as invoked via a /slash command.
Has Claude Code help you connect an MCP server (a database, Notion, GitHub, your own API...), choosing the right transport and scope, using .mcp.json or claude mcp add, handling secrets and OAuth securely, and finally demonstrating how mcp__server__tool tools and @resource pull external data into your workflow.
Applies the spirit of Plan Mode so Claude Code hands over a structured plan (files affected, steps, risks, acceptance criteria) before touching any file—you review, correct, and approve it before execution begins. Prevents the AI from charging ahead and writing a pile of things you didn't want.
Forces Claude Code through a strict red→green→refactor cycle: for every behavior, first write a test that fails (red) and actually run it to prove the failure, then write the minimal implementation that just makes it pass (green), and finally refactor under the safety of the passing tests. Cures the AI's old habit of jumping straight to the happy path, skipping edge cases, and faking test coverage.
Have the agent interview you about your project, then produce a structured, no-fluff AGENTS.md that spells out build/test commands, code style, commit conventions, and off-limits areas in one shot — auto-loaded every time work starts.
Turns a vague requirement into a full Codex workflow: first force it to nail down a 'definition of done,' use plan mode to produce a plan for your approval, then implement in small steps, run its own tests, and finally produce a reviewable diff with verification evidence.
Once your code changes are done, have Codex read the staged diff, produce a Conventional Commits message, and write a PR description covering background, what changed, why, how it was verified, and risks — without bundling in unrelated changes, exaggerating, or fabricating tests.
Has the agent automatically inventory your Cursor project (.cursorrules, .cursor/rules, .cursor/mcp.json), produce a step-by-step migration plan, and generate the corresponding CLAUDE.md or AGENTS.md, slash commands, and MCP config — so you're not stuck 'dumber than Cursor' on day one.
A Definition of Done template you can paste into any coding agent, turning 'what counts as done' into a checklist the agent must self-verify item by item: behavior meets acceptance criteria, tests/lint/typecheck/build all pass (or it states why they didn't run), risky changes come with a rollback plan, and a final 'verification story' is delivered. Puts an end to agents claiming 'done' while everything is actually broken.