CodingClaude Cursor13d ago2 blanks

Explain this module to a new teammate

Daniel Okafor@danielokafor

Remix

Fill in the blanks

0 of 2 filled

Language

Paste code

The prompt

Explain this language module to a new teammate who knows the language but not our codebase.

Start with what it's for in one sentence, then the main flow, then the two things most likely to trip them up. Point to functions by name. Finish with a Mermaid sequence diagram of the call flow.

paste code

Open inChatGPT Claude Perplexity

Fill in the blanks above to copy or open the prompt with your details in it.

510 uses205 saves99 likes1 remix (0 public)Published 23 Sept 2026

A use is a copy, a fill-in copy, an insert or an open in an AI chat, counted once per person per day. Authors' own uses don't count.

More like this

Coding

A regex, with tests that prove it

Write a regex in language that matches what it should match and does not match what it should not. Then give 8 test strings: 4 that should match and 4 that shouldn't, including edge cases like empty strings and Unicode. Explain each part of the pattern in a table. If a regex is the wrong tool here, say so and show the alternative.

Arjun Mehta

Example output: a code review of a small diff, with two findings pinned to lines, concrete fixes, and the verdict “Ship after fixes”.

CodingStaff pick

Code review like a careful senior

Arjun Mehta

Coding

Unit tests for a function I paste

Write test framework tests for the function below. Cover the happy path, the boundaries, invalid input, and one property that should always hold. Use test names that read as sentences. Don't mock what you don't own. If the function is hard to test, suggest the smallest refactor that would help. paste function

Arjun Mehta

Coding

Stack trace to root cause in three sentences

Read this stack trace from service name (language / framework). In three sentences: what failed, the most likely root cause, and the first thing I should check. Then list up to three other possible causes, ranked, each with the log line or metric that would confirm it. If the trace is cut off or ambiguous, say what extra information you need instead of guessing. paste stack trace

Arjun Mehta

Human Resources

30-60-90 day onboarding plan for a new hire

Name joins as a role on start date, reporting to manager. The team is team size people working on what the team does. Draft a 30-60-90 day plan we can share with them in week one: Days 1–30: learn. Who to meet (by role, and why), which docs and tools they need access to, and one small task they can finish in the first two weeks. Days 31–60: contribute. One piece of real work they own, and how we'll both know it went well. Days 61–90: own. What they should be running without help by day 90. For each phase, add one question the manager should ask in their 1:1. Keep it realistic for full-time or part-time, and don't fill gaps with generic "build relationships" items…

Nisha Kapoor

Coding

Blameless postmortem from an incident timeline

Turn this incident timeline into a blameless postmortem. 1. Summary: what users saw, for how long, how many were affected 2. Timeline: in time zone, one line per event 3. Root cause: technical, never "human error" 4. What went well, what didn't 5. Action items: owner, due date, and whether each one prevents or detects If the timeline has gaps longer than 15 minutes, point them out. Timeline: paste timeline

Daniel Okafor

Productivity

Standup update from my git log

Here's my git log since yesterday's standup: [paste git log --oneline --since=yesterday] Write my standup update in three lines: Done, Doing, Blocked. Group related commits, use plain words instead of commit jargon, and leave Blocked as "Nothing" if there's nothing in the log that suggests a blocker.

Asha Rao

Display · responsive