An idea worth
your next prompt.

Create an interactive task planner from the tasks I paste below. Let me change priority and estimated time, then show a realistic order for a two-hour work session. Keep my task names, flag missing estimates and explain the ordering in three lines. If interactive UI is unavailable, give me a simple table instead. Tasks: [paste your tasks].

Help me prepare a small website for launch using Codex or Claude Code. Work in checkpoints; do not publish, buy services, change permissions or send messages without my explicit instruction. Website: [URL or local project]. Audience: [who]. One job it must do: [job]. Primary action: [action]. Brand constraints: [approved assets, colors and tone]. Available evidence: [files or screenshots]. 1. Inspect only the relevant files and the actual page when available. Write a five-line brief and mark unknowns. Separate observed facts from assumptions. Identify the smallest useful page and one acceptance check for its primary action. 2. Produce a launch-readiness table: page/message, primary action, keyboard/mobile access, broken links, form receipt and delivery, title/description/canonical, robots/sitemap and public indexing intent. For each row write PASS, FAIL or UNVERIFIED, the exact evidence and the next smallest check. An HTTP200 alone does not prove a working form or a good page. 3. If changes are authorized, fix one demonstrated issue at a time and rerun its relevant check. Keep branding and unrelated behavior intact. Never paste credentials into code, URLs or reports. Use test data and approved recipients for form checks. 4. Finish with launch blockers, verified results and a short handoff for the next session. Google submission is not indexing or a ranking guarantee. Flag missing account access for Search Console; do not invent success. Check remaining provider capacity and reset time in INMC or the provider before a long task. Missing readings are unknown. Tokens, plan capacity and billed API cost are different; do not infer how many prompts remain.

Using my photo and the garment photo I attach, create one outfit preview. Preserve my face, body proportions, pose, background and lighting. Change only the garment; preserve its color and visible details. Do not retouch my appearance. Treat the result as a visual concept, not a prediction of size or fit.

Use the recording I attach to produce a concise meeting recap: decisions, next actions, owners explicitly named and unresolved questions. Include timestamps only when you can verify them. Mark unclear speech and do not invent names or deadlines. Finish with a follow-up email draft under 120 words. Do not send it.