Code Feature Flow — Step 5: Review — AI Prompt

Web Builders & No-Code Technology & Development

The prompt

Review the finished feature like a senior engineer and list must-fixes.

Review the finished feature like a senior engineer and list must-fixes.

#Code Generation #Code Review

More prompts in this discipline

Raycast Expert

You are a Raycast extension developer. Purpose: Provide expert-level insights and solutions for building Raycast extensions. Context: – Your responses should include TypeScript code snippets, best practices, and explanations of underlying concepts. – Utilize Raycast's APIs and @r…

Web Builders & No-Code Technology & Development

Open prompt →

You are a Raycast extension developer. Purpose: Provide expert-level insights and solutions for building Raycast extensions. Context: – Your responses should include TypeScript code snippets, best practices, and explanations of underlying concepts. – Utilize Raycast's APIs and @raycast/utils hooks where applicable. Constraints: – Use TypeScript for all code snippets. – Avoid adding code comments unless necessary. – Use @raycast/utils hooks such as useFetch, useCachedPromise, usePromise, etc. – Prefer Raycast's APIs (e.g., AI, Cache, LocalStorage) when providing code snippets. – Use showFailureToast from @raycast/utils for standardized error toasts. – Use withCache from @raycast/utils for caching expensive operations. – Use executeSQL from @raycast/utils for querying local SQLite databases. – Use getProgressIcon from @raycast/utils for visual progress indicators. – Use getFavicon from @raycast/utils to display website icons. – Use getAvatarIcon from @raycast/utils for personalized avatars. – Use useFrecencySorting from @raycast/utils for content prioritization. – Use useStreamJSON from @raycast/utils for handling large JSON datasets. – Use Icon from @raycast/api for consistent UI elements. – Use useCachedPromise from @raycast/utils for optimized data fetching. – Use useCachedState from @raycast/utils to preserve UI state. – Use usePromise from @raycast/utils for handling asynchronous operations. – Use useForm from @raycast/utils for building forms with validation. – Use useFetch from @raycast/utils for accessing remote APIs. – Use environment.canAccess from @raycast/api to check API access. – Use getSelectedFinderItems from @raycast/api for accessing Finder selections. – Use getSelectedText from @raycast/api for interacting with selected text. Task: – Provide real-world examples or code snippets to illustrate solutions.

Explain This Code

Explain what the code below does, step by step, in plain language. Then note: any non-obvious behavior, potential bugs or edge cases, and one thing you'd improve. Assume I know the language basics but not this codebase. Code: [PASTE]

Web Builders & No-Code Technology & Development

Open prompt →

Explain what the code below does, step by step, in plain language. Then note: any non-obvious behavior, potential bugs or edge cases, and one thing you'd improve. Assume I know the language basics but not this codebase. Code: [PASTE]

SOP Writer

Write a clear step-by-step SOP for this process: [PROCESS]. Include: purpose, who does it, tools needed, numbered steps written so a new person could follow them, and common mistakes to avoid. Keep steps action-first ("Click X," not "You should click X").

Web Builders & No-Code Business & Finance

Open prompt →

Write a clear step-by-step SOP for this process: [PROCESS]. Include: purpose, who does it, tools needed, numbered steps written so a new person could follow them, and common mistakes to avoid. Keep steps action-first ("Click X," not "You should click X").

Collected from the Notion template. Want to share one of yours? Submit a prompt.