Design System Component Spec Writer for Figma Handoff
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
341 prompts · last added
260 results for “ci” · page 4 of 11
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
Audits a user flow from screenshots or descriptions and returns an evidence-labeled issue table plus a fix-now, next, defer plan for a sprint decision.
Create a writer-ready content brief from SERP observations you supply. It covers intent, required sections, evidence gaps, and a go or no-go call on whether the page is worth producing.
Converts pasted monthly KPI results and targets into a variance analysis, driver hypotheses, and prioritized actions that a leadership team can decide on in one meeting.
Create a ranked risk register, early warning signs, and a two-week action plan for a project. Supports the go/no-go and resourcing decision at the next checkpoint.
Convert a call transcript or notes into a concise follow-up email, structured CRM notes, and a risk check on the deal. Helps the rep decide the next step and what to say.
Plan a custom GPT before building it. Produces the instruction text, knowledge file plan, conversation starters, and a test set so you can decide whether to build, narrow, or skip it.
Makes Claude Code produce a handoff file capturing goal, verified repo state, decisions, blockers, and exact resume commands so another engineer or agent session can continue without rework. Use it before ending a long task.
Runs a behavior-preserving refactor in Codex exec. It pins current behavior with characterization tests, refactors in small verified steps inside an allowed scope, and ends with an evidence-based handoff for the merge decision.
Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.
Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Has GitHub Copilot review your branch diff against the base branch, flag defects and missing tests, and draft a PR description with evidence. Use it to decide whether to open the PR or fix issues first.
Guides GitHub Copilot agent mode to inspect the repository, state assumptions, plan a minimal change, implement it, and add tests. It ends with a verification report you can use to decide whether to open a PR.
Compares products you are choosing between using current reviews and spec sheets, with cited sources, real-world complaints and a recommendation based on how you will use it.
Builds a blog post outline for one keyword by first deciding the search intent, then structuring headings, questions and examples that match what searchers expect to find.
Writes a 250-word cover letter that picks the employer's top three needs from the job post and answers each with a specific example from your resume.
Turns your common support questions and policies into ten reusable reply macros with a warm tone, the right policy detail, and a placeholder only where agents must personalise.
Turns raw meeting notes or a transcript into decisions, action items with owners and dates, open questions, and a short follow-up email you can send right after the call.
Turns the transcript of a recorded walkthrough into a numbered SOP with prerequisites, steps, screenshots to capture, decision points, and common mistakes, ready for a team wiki.
Gives tough, rubric-based feedback on an essay with specific line references and questions to fix each problem, while refusing to rewrite the essay for you.
Claude Code inspects your repository and writes a CLAUDE.md under 200 lines with verified commands first, checkable conventions, anti-patterns and the reasons behind key decisions.
Turns a product brief into a timed explainer script, shot list, and production checklist so a team can decide whether to greenlight, revise, or shoot the video.
Analyzes a recurring manual task and produces an automation blueprint with trigger, steps, data mapping, error handling, and a test plan. It also helps you decide whether the task is worth automating at all.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.