24 reviewed prompts.
Turns your notes into a structured annual summary covering results, lessons, challenges and goals for next year. Use it for performance reviews, team updates or personal planning.
Drafts a themed literature review from sources you supply, with a reference list in the citation style you name and a gaps section. Use when writing a thesis chapter, report background or paper introduction.
Reviews an algorithm you describe or paste, finds weak points and bottlenecks, and proposes ranked improvements with trade-offs. Use it when something works but is slow, inaccurate or will not scale.
Reviews smart contract code for security flaws, risky admin powers and wasteful gas use, with exploit scenarios, fixes and tests to add. Use it before an external audit or any deployment that holds funds.
Critiques a product requirements draft or one-pager, ranking its weakest points, listing missing evidence and suggesting the questions to answer before building. Use before committing engineering time.
Reviews pasted bank or card transactions to find top payees, recurring charges, unusual items and ways to save. Use when checking your own or your small business statements monthly.
Checks an invoice's line totals, subtotals, discounts, tax amounts, dates and missing details, and lists discrepancies. Use before sending an invoice or paying one you received.
Maps how a feature or system you own could be attacked or misused and lists prioritized defenses, detection and tests. Use during design or before a security review of your own product.
Reviews an infrastructure-as-code change and its plan output for destroyed or replaced resources, leaked secrets, blast radius and version drift, then gives a validation and rollback plan. Use it before applying changes to shared environments.
Looks at what came in and went out this month, compares it with your plan, spots where money leaked and suggests small changes for next month. Use at the end of each month in about ten minutes.
Turns rough notes about your work into an evidence-based self-review with impact stories, collaboration examples and a growth plan. Use it before an annual or mid-year review.
Reads a product requirements document (PRD) and points out missing pieces, vague requirements, untested assumptions and open questions, ranked by how much they could hurt the project. Use before sign-off or handover to design and engineering.
