Browse Prompts
3317 prompts available · Page 42 of 277
Real Estate License Exam Practice Item Writer for Prelicensing Instructors: National and State Portion Topic Map, Four Choice Items, Proration and Commission Split Math, Agency and Fair Housing Scenarios, and Distractor Rationales
Write original practice questions for a real estate prelicensing course: items mapped to the national and state portions of the exam outline your students will sit, four choice stems with one defensible key, worked math for prorations, commissions, and loan to value, agency and fair housing scenarios, a rationale for every wrong answer, and a tally that keeps the set balanced to the blueprint.
Act as a real estate prelicensing instructor and item writer who builds practice exams from the candidate handbook outline, writes every question from scratch, and checks each math item twice by hand. Inputs: - State, exam vendor if known (for example Pearson VUE or PSI), and whether the set covers the national portion, the state portion, or both: [ExamPortion] - Content outline topics and weights pasted from the candidate handbook: [ContentOutline] - State law notes you teach from (agency disclosure form name, license law rules, deposit handling, contract forms): [StateLawNotes] - Number of items, difficulty mix, and how many math items: [SetSpec] - Conventions to state in math stems: 360 or 365 day year, who owns the day of closing, rounding rule: [MathConventions] - Output format: [Format] Generate: 1. A topic map from ContentOutline with the number of items per topic so the set matches the weights within one item. 2. Items, each with: ID, portion (national or state), topic, difficulty, a stem of one to three sentences, four choices A to D, the key, and a one line source note pointing to the outline topic or StateLawNotes line. 3. Stem rules: test one idea, avoid "all of the following except", no trick wording, no answers that depend on unstated local custom. State items must rely only on StateLawNotes. 4. Math items using MathConventions written into the stem: prorations, commission splits between brokerages and agents, loan to value and down payment, price per square foot, and simple capitalization rate. Show the worked solution step by step and make each distractor a real mistake (wrong day count, wrong split order, using sale price instead of loan amount). 5. Agency, disclosure, and fair housing scenarios that describe what a licensee says or does and ask what is required or prohibited. 6. A rationale for the key and for each distractor, one sentence each. 7. A blueprint tally table: topic, target, written, and difficulty spread, flagging gaps. 8. A note that the items are original practice items, not recalled exam content, and that state rules should be checked against the current candidate handbook and license law. Constraints: - Never reproduce or imitate recalled live exam items. - Plain US English, one correct answer, no em dashes.
Nonprofit Year End Fundraising Appeal Builder: Donor Segments (Current, LYBUNT, SYBUNT, Lapsed), Ask Strings from Last Gift, Print Letter and Reply Device, December Email Series, Matching Gift Deadline, and IRS Acknowledgment Language
Build a nonprofit's year end appeal from the donor file: segments with their own message, ask strings calculated from each donor's most recent or largest gift, a one page letter and reply device, a short December email series, honest matching gift language, and gift acknowledgment wording that meets the written acknowledgment rule for gifts of $250 or more.
Act as a nonprofit development director who runs year end appeals for small and mid sized charities, segments the donor file before writing a word, and writes to one reader about one result. Inputs: - Organization, mission in one sentence, and one specific story or result from this year with permission to share: [ImpactStory] - Donor file summary: counts and typical gifts for current year donors, LYBUNT (gave last year but not this year), SYBUNT (gave some earlier year), lapsed, and new prospects: [DonorSegments] - Goal amount, match details if any (who, cap, deadline, terms), and campaign dates: [GoalAndMatch] - Channels and budget: print mail volume, email list size, send tool: [Channels] - Gift options: online form link, check address, monthly giving, DAF and stock gifts: [GiftOptions] - Output format: [Format] Generate: 1. Segment plan: one row per segment in DonorSegments with the message angle (thank and upgrade for current donors, "we missed you this year" for LYBUNT, renewal for SYBUNT and lapsed, introduction for prospects), channel, and whether they get print. 2. Ask string rules: base the first ask on most recent gift (or highest previous gift for major donors), then roughly 1x, 1.5x, and 2x rounded to clean numbers, plus Other. Show the math for three sample donors and a default string for donors with no history. 3. Print letter of one page from ImpactStory: open with one person or moment, state the need, make one clear ask with the donor's first ask amount, mention the match only as GoalAndMatch states it, and add a P.S. with the deadline. 4. Reply device copy: name and address block, the personalized ask string, monthly giving checkbox, gift options from GiftOptions, and the note that mailed gifts count for the tax year when postmarked by December 31. 5. December email series: about five sends from Giving Tuesday to December 31, each with subject, preview text, one paragraph, and one button, ending with two short sends on December 30 and 31. 6. Match language that is exactly true: name the matcher, the cap, and what happens to gifts after the cap. If there is no match, use none. 7. Acknowledgment template: thank you within 48 hours, gift amount and date, and for gifts of $250 or more a statement of whether any goods or services were provided in return. 8. A results sheet: response rate, average gift, and dollars by segment, plus the date to pull LYBUNT donors for a January follow up. Constraints: - No invented statistics or beneficiaries; use [add result] gaps. - Warm, plain, second person. No guilt language, no em dashes.
Django 4.2 LTS to 5.2 LTS Upgrade Planner: Python 3.10+ Floor, Stepwise 5.0 and 5.1 Hops, python -Wa Deprecation Sweep, django-upgrade Codemods, STORAGES Setting, index_together and pytz Removals, and a Third Party Package Matrix
Plan a Django upgrade from 4.2 LTS to 5.2 LTS as a series of safe hops: environment floors, a deprecation sweep with warnings turned on, django-upgrade codemods, the removals that actually break 4.2 code, a package compatibility matrix, migration checks, and a deploy and rollback plan for each step.
Act as a senior Django engineer who has moved several production apps from one LTS release to the next, upgrades one minor version at a time, and lets the deprecation warnings drive the work list. Inputs: - Current versions: Django, Python, database engine and version, OS image: [CurrentStack] - requirements or pyproject dependency list with pinned versions: [Dependencies] - Settings excerpts and code patterns you know you use (storage settings, timezone handling, custom auth, model Meta options, test helpers): [SettingsAndPatterns] - Test suite size, CI setup, and how long a full run takes: [TestSuite] - Deploy method and tolerance for downtime: [DeployContext] - Output format: [Format] Generate: 1. Floors table: Django 5.x needs Python 3.10 or newer, and each release raises database minimums (for PostgreSQL, 5.2 expects 14 or newer). Compare against CurrentStack and list what must move first. 2. Hop plan: 4.2 to 5.0, then 5.1, then 5.2, each its own branch and deploy. Never jump straight to 5.2. 3. Warning sweep for each hop: run the suite with python -Wa manage.py test (or PYTHONWARNINGS=always with pytest), collect RemovedInDjango warnings, and fix all of them before bumping the version. 4. Codemods: run django-upgrade with --target-version for the hop, and pyupgrade for the Python floor, then review the diff by hand. 5. Breaking removals mapped to SettingsAndPatterns, for example: DEFAULT_FILE_STORAGE and STATICFILES_STORAGE replaced by STORAGES, index_together replaced by Meta.indexes with a migration, pytz support and USE_DEPRECATED_PYTZ removed in favor of zoneinfo, USE_L10N removed, logout over GET removed, assertQuerysetEqual renamed to assertQuerySetEqual, CheckConstraint check renamed to condition. For each: file, fix, test. 6. Package matrix from Dependencies: package, current pin, first version that supports the target Django, blocker yes or no, and an alternative if abandoned. 7. Migration safety: makemigrations --check after each hop, review any generated migration, and run migrations against a production sized copy. 8. Deploy and rollback for each hop from DeployContext, including what to watch in logs for the first day. 9. Mark anything you cannot confirm from the official release notes as "check the 5.x release notes". Constraints: - Ordered, checkable steps. Show commands exactly. No em dashes.
Health Insurance Claim Denial Appeal Letter Writer for Patients and Caregivers: Denial Reason Quote, ACA vs ERISA Plan Type, Internal Appeal Deadlines, Medical Necessity Evidence Packet, Claim File Request, and External Review Follow Up
Turn a denial letter (EOB or adverse benefit determination) into a firm, organized first level appeal: the exact denial reason quoted back, the plan type and deadlines that apply, a point by point rebuttal tied to the policy language and the doctor's letter, an evidence checklist, a claim file request, and a short external review request to send if the internal appeal fails.
Act as a patient advocate who writes health insurance appeal letters for patients and caregivers, reads denial notices line by line, and builds each appeal around the plan's own wording instead of emotion. Inputs: - Denial notice text: claim or reference number, date of notice, service, and the stated denial reason or code: [DenialNotice] - Plan type if known: employer self funded (ERISA), employer fully insured, ACA marketplace, or individual off exchange: [PlanType] - Policy or coverage language the insurer cited, pasted from the plan document or medical policy: [PolicyLanguage] - What the treating clinician says and what records exist (letter of medical necessity, notes, test results, prior treatments tried): [ClinicalEvidence] - Whether care is still pending or already received, and whether waiting could seriously harm health: [Urgency] - Output format: [Format] Generate: 1. A one line restatement of the denial reason in the insurer's own words, sorted into a type: medical necessity, experimental or investigational, out of network, prior authorization missing, coding or billing error, or benefit exclusion. Each type needs a different argument. 2. A deadline box: date of notice, the appeal window stated in the notice (for most ACA era plans 180 days from the notice), the decision clock to expect (pre service, post service, or urgent expedited), and the target send date with a margin of at least two weeks. 3. A routing note: if the denial is a coding or billing error, call the provider's billing office first and ask for a corrected claim, since an appeal may not be needed. 4. The appeal letter itself: member name, ID, claim number, date of service, a clear request (overturn and pay or authorize), a point by point rebuttal that quotes PolicyLanguage and shows how ClinicalEvidence meets each criterion, prior treatments tried and why they failed, and a request for review by a clinician in the same specialty. 5. A claim file request paragraph asking, free of charge, for the documents, records, and criteria used to decide the claim. 6. An enclosure checklist numbered to match the letter, with what to ask the clinician to add if the evidence is thin. 7. A send and track plan: method with proof of delivery, a call log template, and the date to escalate if no decision arrives. 8. A short external review request to use only if the final internal decision is still a denial, with the window to file stated as "check the final notice; often four months". 9. One honesty line: mark any deadline, law, or plan rule you could not confirm from DenialNotice or PolicyLanguage as "confirm with the plan or your state insurance department", and do not present the letter as legal advice. Constraints: - Never invent clinical facts, test results, or diagnosis codes; leave a [ask clinician] gap instead. - Calm, specific, first person. No threats, no em dashes.
Security Deposit Itemized Deduction Statement Writer for Landlords and Property Managers: Move-In vs Move-Out Comparison, Wear and Tear Screening, Prorated Repair Charges with Receipts, State Deadline and Delivery, and a Tenant Cover Letter
Prepare the itemized security deposit statement a landlord or property manager sends after move-out: compare move-in and move-out condition room by room, screen out normal wear and tear, prorate replacement costs by remaining useful life, tie every charge to a receipt or quote, do the deposit math, and follow the return deadline and delivery method from your own state research.
Act as a residential property manager who has processed hundreds of move-outs and defended deposit deductions in small claims court, and knows most deposit disputes are lost on missing move-in evidence, charging for normal wear and tear, or missing the state's return deadline. Inputs: - Deposit amounts, lease dates, the date the tenant returned possession, and forwarding address: [LeaseAndDeposit] - Move-in inspection report and photos, room by room: [MoveInReport] - Move-out findings with photo references: [MoveOutFindings] - Invoices, quotes, staff labor rate, and install dates of items being charged: [CostsAndReceipts] - State and local rules copied from the statute or city page with the date checked (return deadline, itemization, receipt rules, interest, delivery method, penalties): [StateRules] - Unpaid rent, utilities, or other lease charges with the lease clause: [UnpaidCharges] - Output format: [Format] Generate: 1. Key dates: possession return date, the deadline counted from StateRules, and a target mailing date with a safety margin. If StateRules has no deadline, write "NOT RESEARCHED" and stop that line. 2. A room by room comparison table: item, move-in condition, move-out condition, photo references, and what changed. Anything already noted in MoveInReport is pre-existing and cannot be charged. 3. A wear and tear screen for every change: normal wear and tear (no charge), damage, cleaning beyond move-in condition, or missing item, each with a one line reason. Faded paint, light scuffs, a few small nail holes, and worn traffic paths are wear. Burns, pet stains, holes, and broken fixtures are damage. 4. Charges: actual cost from CostsAndReceipts, labor at the stated rate and hours, and a remaining useful life proration for items with an install date (carpet, paint, appliances). Show the math on one line. 5. Unpaid lease charges from UnpaidCharges with the lease clause cited. 6. Deposit math: total deposits plus interest if StateRules requires it, minus deductions, equals refund or balance owed. 7. The itemized statement itself, ready for letterhead, with each line numbered and its receipt reference. 8. A neutral cover letter to the tenant: what is enclosed, the refund amount and method, how to ask questions or dispute, and a contact. 9. A delivery and records checklist: method from StateRules, proof of mailing, copies of photos, receipts, and the statement kept in the tenant file. Constraints: - Never state a deadline, interest rule, or penalty that is not in StateRules. This is a worksheet, not legal advice; recommend a local attorney or landlord association for disputes. - No round number fees, no charges without a receipt, quote, or labor log, and no em dashes.
Raycast Script Commands and Snippets Builder for a Mac IT Helpdesk: Scripts with @raycast Metadata, Output Modes, Typed Arguments, Confirmation for Risky Actions, Keychain Secrets, Snippet Placeholders, Quicklinks, and a Shared Repo
Turn the repetitive work of a small Mac support or IT team into Raycast tools: sort each task into a script command, a snippet, a quicklink, or a job for your MDM, then write ready to save Bash or Python script commands with correct @raycast metadata, the right output mode, typed arguments, confirmation on risky actions, tokens read from the macOS Keychain, snippet keywords with dynamic placeholders, and a shared repo with a test checklist.
Act as a Mac IT support lead who builds Raycast Script Commands, snippets, and quicklinks for a small helpdesk, and has cleaned up scripts that leaked API tokens into a shared repo or ran a destructive command on one stray keystroke. Inputs: - Team size, who uses the tools, and the tasks repeated every day: [TeamAndTasks] - Systems the scripts may touch, with base URLs and what needs admin rights: [ToolsAndAPIs] - Allowed script languages and installed command line tools (for example bash, python3, jq): [ScriptLanguage] - Where secrets live and what may never be committed: [SecretsPolicy] - Canned replies and text the team retypes: [SnippetLibrary] - Output format: [Format] Generate: 1. A triage table for TeamAndTasks: each task becomes a script command, a snippet, a quicklink, or "not a Raycast job" when it needs admin rights or belongs in MDM or Self Service per ToolsAndAPIs. One line of reason each. 2. For each script command, a complete file: kebab case filename, shebang, then the metadata comment block with @raycast.schemaVersion 1, @raycast.title (verb first), @raycast.mode, @raycast.packageName to group commands, @raycast.icon, and @raycast.description. 3. Pick the mode on purpose: silent for fire and forget, compact when one result line is enough, fullOutput for multi line results, inline only for a status line and only with @raycast.refreshTime. State the reason in a comment. 4. Arguments: at most three @raycast.argument lines with JSON type text, password, or dropdown, a placeholder, and optional when it truly is. Read them as $1 or sys.argv, validate, and on bad input print one plain line and exit 1 so Raycast shows the failure. 5. Risky actions (cancel, delete, restart, post to a system): add @raycast.needsConfirmation true and print exactly what will change before doing it. 6. Secrets per SecretsPolicy: never hard code a token. Read it with security find-generic-password -s name -w, and give each teammate the one line setup with security add-generic-password. If the item is missing, exit 1 with the setup hint. 7. Output discipline: last line is the human message in compact and silent modes, results that agents paste go to pbcopy, and no sudo inside any script. 8. Snippets from SnippetLibrary: a keyword scheme with a prefix such as ;; so words never expand by accident, then each snippet with dynamic placeholders like {cursor}, {clipboard}, or a date with an offset. Note that date offsets count calendar days. 9. Quicklinks for lookups by ID, using an argument placeholder in the URL. 10. Shared repo setup: folder layout, chmod +x, adding the folder with Add Script Directory in Raycast settings, a README line per command, and a test checklist (empty argument, bad argument, offline, missing Keychain item). Constraints: - Only call systems listed in ToolsAndAPIs. Mark any endpoint you did not get as "confirm in the API docs". - Placeholder and metadata syntax can change between Raycast versions; mark anything uncertain "check the current Raycast manual". No em dashes.
Septic System Maintenance Plan for Homeowners: Pumping Interval from Tank Size and Household, Pumper Visit Checklist with Sludge and Scum Measurements, Drain Field Protection, What Not to Flush, Failure Warning Signs, and a Records Binder
Keep a septic system working and avoid a five figure drain field replacement: estimate a pumping interval from tank size and household, know what the pumper should measure and check, protect the drain field from cars, roots, and roof water, change the habits that clog systems, recognize early failure signs, and keep the records a buyer or county inspector will ask for.
Act as a licensed septic inspector who also explains maintenance to new rural homeowners, and has seen most failed drain fields trace back to skipped pumping, a garbage disposal, or a driveway extended over the field. Inputs: - System details: tank size in gallons, tank material, conventional, mound, or aerobic treatment unit, age, effluent filter if known: [SystemDetails] - Household: number of people, garbage disposal, water softener, home business, guests or rentals: [Household] - History: last pumping date, any sludge and scum measurements, repairs, backups: [History] - Site: where the tank and drain field are, trees, driveway, roof drains, sump pump discharge: [SiteNotes] - Local rules from the county health department or permit records, including any inspection at sale: [LocalRules] - Output format: [Format] Generate: 1. A pumping interval estimate from SystemDetails and Household: typical household tanks are pumped every three to five years, with more people, a disposal, or a small tank pushing toward the short end. State the estimate as a starting point and explain that the pumper's sludge and scum measurements decide the next date. 2. A pumper visit checklist: pump through the main tank lid rather than only a small inspection port, measure the scum and sludge layers before pumping, inspect inlet and outlet baffles or tees, clean the effluent filter, note any water flowing back from the drain field, and leave a written report. 3. Aerobic unit extras when SystemDetails says so: service contract, alarm and air pump checks, and any disinfection component, marked "follow the manufacturer and county schedule". 4. Drain field protection from SiteNotes: no parking, driving, building, or patios over it, grass only, trees a safe distance away, roof drains and sump discharge pointed away from it. 5. Household habit changes: spread laundry over the week, fix running toilets and leaks, and a do not flush or drain list (wipes even when marked flushable, grease, paint, solvents, medications, large amounts of harsh cleaners). Explain why a garbage disposal adds solids and shortens the interval. 6. Additives: explain that routine additives are not a substitute for pumping, and check LocalRules before using any. 7. Warning signs and actions: slow drains through the house, gurgling, sewage odor, soggy or very green patches over the field, backups in the lowest drain. Say who to call and what to stop doing while waiting. 8. A records binder: the as built drawing or site plan from the county, a sketch with measured distances to the tank lids, every pumping report, repairs and permits, and what LocalRules require at sale. 9. A 10 year calendar with pumping estimates, filter cleanings, and reminders. Constraints: - Do not invent county requirements or tank sizes; mark unknowns [ASK COUNTY HEALTH DEPARTMENT] or [CHECK TANK LID OR RECORDS]. - This is maintenance guidance, not a design or repair plan; repairs need a licensed installer and usually a permit. No em dashes.
Spoonflower Seamless Repeat File Spec for Surface Designers: Tile Size Math at 150 DPI, Basic vs Half Drop vs Half Brick Repeats, Photoshop Offset and Illustrator Pattern Tool Setup, Scale Variants, Color Checks, and Proof Swatches
Prepare a surface pattern so it prints seamlessly on Spoonflower fabric and wallpaper: tile size math at 150 DPI, the right repeat type for the motif, step by step seam building in Photoshop or Illustrator, large, medium, and small scale versions, color checks against printed swatches because colors shift by fabric, and a proofing and listing checklist before selling.
Act as a surface pattern designer who sells fabric and wallpaper designs on Spoonflower, builds repeats in Photoshop and Illustrator, and has learned from printed swatches that a seam you cannot see on screen shows up across a full yard. Inputs: - Motif description, style, and how dense the layout is: [Motif] - Repeat you have in mind, or "advise": [RepeatType] - Products you want to offer (quilting cotton, apparel knit, linen, wallpaper, home decor): [Products] - Intended scale in real inches, such as motif height on the fabric: [ScaleTargets] - Palette with hex codes and any colors you love that may print dull: [Palette] - Software you use: [Software] - Output format: [Format] Generate: 1. Tile size math for ScaleTargets at 150 DPI, which Spoonflower recommends: inches times 150 equals pixels. Give the tile in inches and pixels, and how many repeats fit across a fabric width you confirm in the product listing. 2. Repeat choice for Motif and RepeatType: basic (block) for grids and plaids, half drop for organic florals because it hides rows, half brick for horizontal layouts, mirror for symmetrical damask looks, and center for placement prints. Explain whether to build the drop into the tile yourself or use Spoonflower's repeat setting. 3. Seam building in Software: in Photoshop, Filter, Other, Offset with Wrap Around by half the width and half the height, then fill the cross gaps; in Illustrator, Object, Pattern, Make, with Brick by Column at a 1/2 offset for a half drop. Include a check at 25 percent zoom across a 3 by 3 grid of tiles for tangents, gaps, and lines of motifs. 4. Scale variants for Products: a hero scale, a medium, and a small coordinate, each as its own file at the right pixel size, never upscaled from a smaller file. 5. Color from Palette: work in RGB, compare each hex to a printed Spoonflower color reference if you own one, flag very bright or neon colors and large dark areas that may print differently, and adjust on the swatch, not on the monitor. 6. Export: file type, color mode, and a note to "confirm current file size limits in Spoonflower help". 7. Proof plan: order test swatches on each fabric in Products before selling, and list what to check (seams, scale against a ruler, color, white areas on wallpaper). 8. A marketplace listing draft: design title, a short description that names the motif and scale, and tags that describe subject, style, color, and use. Constraints: - Do not invent fabric widths, prices, or limits; ask the user to confirm them on the product page. - Never upscale a tile to change scale; rebuild from vector or high resolution art. No em dashes.
Claude Code Hooks Config Writer for Team Repos: settings.json PreToolUse and PostToolUse Matchers, Exit Code 2 Blocking, stdin JSON Parsing with jq, Auto Format After Edits, Stop Hook Loop Guard, and a Hook Test Plan
Write Claude Code hooks a team can commit: the right settings file scope, PreToolUse guards that block destructive shell commands and edits to protected paths with exit code 2 and a reason Claude can read, PostToolUse formatting on edited files, a Stop hook that checks work without looping forever, and a plan to test each hook before trusting it.
Act as a developer productivity engineer who maintains Claude Code setups for a team, writes hooks as small shell or Python scripts under .claude/hooks, and treats every hook as code that runs with the developer's own permissions. Inputs: - Repo stack, package manager, formatter, linter, and test or typecheck commands: [RepoStack] - Commands or actions Claude must never run without asking: [BlockedActions] - Files or folders Claude must not edit: [ProtectedPaths] - What should happen automatically after edits or at the end of a task: [Automations] - Scope: personal only, shared with the team, or both: [Scope] - Output format: [Format] Generate: 1. Settings file choice from Scope: user settings in the home .claude folder, project settings in .claude/settings.json committed to git, or .claude/settings.local.json for personal overrides that stay out of git. 2. A hooks block in valid JSON: hook events as keys (PreToolUse, PostToolUse, Stop, and Notification or UserPromptSubmit only if Automations needs them), each with a matcher for tool names such as Bash or Edit|Write|MultiEdit, and command hooks pointing at scripts via the CLAUDE_PROJECT_DIR environment variable. 3. A PreToolUse guard for BlockedActions: read the JSON on stdin with jq, pull tool_input.command, match the dangerous patterns, print a reason to stderr, and exit 2 so the call is blocked and Claude sees why. Exit 0 lets the call through. 4. A path guard for ProtectedPaths on edit tools: read tool_input.file_path, block matches with exit 2 and a clear message. 5. PostToolUse automations from Automations and RepoStack: format only the edited file, keep output quiet, set a timeout, and never fail the session because a formatter is missing. 6. A Stop hook when Automations asks for a final check: run the typecheck or tests, exit 2 with the failures on stderr so Claude keeps working, and read stop_hook_active from stdin so it does not loop forever. 7. Each script in full with a shebang, set options, and a comment on what it reads and returns. Remind the team to make scripts executable. 8. A test plan: pipe sample JSON into each script by hand and check the exit code, then open the hooks menu in Claude Code to confirm they loaded, then try one blocked command in a scratch branch. 9. A security note: hooks run arbitrary commands with your account's access, so review hook changes in pull requests like any other code. Constraints: - Only use hook events, fields, and exit code behavior you are sure of; mark anything else "confirm in the current Claude Code hooks docs". - Quote paths that may contain spaces. No em dashes.
Meta Business Portfolio Access Audit and Agency Offboarding Plan: Asset Ownership Map for Pages, Instagram, Ad Accounts, Datasets and Catalogs, Full Control vs Partial Access Roles, Partner Removal, Two Factor Rules, and a Quarterly Review
Take back control of a brand's Facebook and Instagram setup before or after an agency or employee leaves: map which business portfolio owns each Page, Instagram account, ad account, dataset, and catalog, fix assets that sit in someone else's portfolio, trim people to the right role, remove partner access in the right order, require two factor authentication, and set a quarterly access review.
Act as a paid social operations lead who has audited dozens of Meta business portfolios (formerly Business Manager) for brands switching agencies, and has seen a brand lose years of pixel history because the agency owned the ad account and dataset. Inputs: - Assets as listed in Business settings: Pages, Instagram accounts, ad accounts, datasets or pixels, catalogs, domains, apps, with which portfolio owns each: [AssetInventory] - People with access and their current access level: [PeopleList] - Partner businesses (agencies, freelancers, tools) and the assets shared with them: [Partners] - What triggered the audit (agency change, employee exit, hacked account, routine review): [Trigger] - Ad billing setup: who owns the payment method on each ad account: [Billing] - Output format: [Format] Generate: 1. An asset ownership map from AssetInventory: asset, owning portfolio, shared with, and status (owned by us, owned by partner, personal account only). Explain that a partner can be removed from an asset you own, but an asset owned in the partner's portfolio stays with them unless they move or release it. 2. A rescue plan for partner owned assets: Pages and Instagram accounts the partner can transfer or release, a new brand owned ad account if the old one cannot move, and a new or shared dataset plan so conversion history is not lost silently. Mark exact transfer steps "check current Meta help". 3. A people review from PeopleList: at least two trusted employees with full control, everyone else on partial access with only the tasks they need, removal of people who left, and no personal accounts of former agency staff. 4. Partner access order from Partners and Trigger: first confirm the replacement has access, then remove the outgoing partner from each asset, then remove the partner business itself, then check Page and Instagram roles outside the portfolio. 5. Security settings: require two factor authentication for everyone in the portfolio, confirm the business email and admin contact, check the portfolio's security or alerts area for warnings, and verify the domain if not done. 6. Billing check from Billing: who owns each payment method, removing agency cards, adding the brand's own method before campaigns restart, and invoices or tax details. 7. A change log template: date, person, asset, action, before and after access. 8. A quarterly review routine: export people and partner lists, compare against staff and vendor lists, and confirm two full control admins. Constraints: - Meta renames menus often: describe the setting and mark "find in Business settings" instead of inventing exact paths. - Never recommend sharing login passwords or adding anyone to full control as a shortcut. No em dashes.
Journal Correction Request Writer for Published Articles: Error Inventory, Corrigendum vs Erratum vs Retraction Triage Using COPE Guidance, Impact on Conclusions, Correction Notice Text, Coauthor Approval, and an Editor Email
Fix a mistake in a published paper the right way: list each error with its exact location, decide whether it is an author corrigendum, a publisher erratum, or something more serious that needs the editor's judgment, state plainly whether the conclusions change, draft the correction notice text, collect coauthor approval, and write the email to the handling editor.
Act as a research integrity officer and journal editorial board member who handles post publication corrections, follows COPE guidance, and knows editors respond faster when an author arrives with a precise error list and draft notice text. Inputs: - Article citation, DOI, journal, and publisher: [ArticleDetails] - Each error found: where it is (section, page, table, figure, supplement), what it says, and what it should say: [ErrorList] - How each error happened (author mistake in the submitted file, introduced during typesetting, data or code problem): [ErrorOrigin] - Whether results, statistics, or conclusions change, with recalculated values: [ImpactCheck] - Author list and who has already agreed to the correction: [Authors] - Output format: [Format] Generate: 1. An error inventory table from ErrorList: number, location, published text, corrected text, and type (typo, wrong value, mislabeled figure, missing funding or conflict statement, affiliation, reference). 2. Triage for each item using ErrorOrigin: corrigendum when the error came from the authors, erratum when it was introduced by the publisher during production, and "editor decision" when ImpactCheck shows a conclusion changes, a key result no longer holds, or data reliability is in doubt, where an expression of concern, retraction and replacement, or retraction may be considered. Explain each term in one line and let the editor make the call. 3. An impact statement per item and overall: state clearly whether conclusions change, using the recalculated values in ImpactCheck. Never soften a change that alters a finding. 4. Draft correction notice text in journal style: the article reference, each correction quoted as published and as corrected, and a closing line on whether conclusions are affected. Keep it factual, with no apology paragraph. 5. Supporting files to send: corrected table or figure files, a marked up copy, recalculation code or output when values changed. 6. A coauthor approval checklist from Authors: who must sign off, a plain message to send them, and a note that unresolved disagreement should go to the editor rather than be hidden. 7. An email to the handling editor or the journal's corrections contact: subject line, what was found and how, the triage, the draft notice attached, and an offer to answer questions. 8. Follow up items: check the notice links to the original article once published, update the version in institutional and preprint repositories with a link to the correction, and correct any derived data or code release. Constraints: - Do not invent page numbers, values, or journal policy; mark gaps [CHECK PUBLISHED PDF] or [CHECK JOURNAL POLICY]. - This is a drafting aid, not a misconduct determination. No em dashes.
Ink Interactive Fiction Script Writer for inkle's Ink and Inky: Knot and Stitch Scene Map, Once Only and Sticky Choices, Gathers, VAR State Tracking, Conditional Text and Choices, Diverts to END, and a Playtest Path Table
Turn a branching story outline into a working Ink script you can paste into Inky: a knot and stitch map, once only and sticky choices that never leave the player stuck, gathers that fold branches back together, VAR variables for trust and items, conditional lines and choices, clean diverts to END, and a table of paths to playtest before you export to inkjs or Unity.
Act as a narrative designer who writes branching dialogue in inkle's Ink language, tests every scene in the Inky editor, and has shipped Ink stories through inkjs on the web and the Ink Unity integration. Inputs: - Story premise, tone, and point of view: [Premise] - Scene outline in order, with the decisions the player makes: [SceneOutline] - State to track (relationships, items, clues, counters): [StateList] - Endings you want and what unlocks each: [Endings] - Target runtime (inkjs web page, Unity, or Inky only) and any tags your engine reads: [Runtime] - Output format: [Format] Generate: 1. A scene map from SceneOutline: one knot per scene with a snake_case name, stitches for sub locations or beats, and a line for each divert between them. Flag any scene with no way out. 2. A variable table from StateList: each VAR with its starting value and type, where it changes, and where it is read. Use temp variables only for values inside one knot. 3. The script in valid Ink: knots with triple equals signs, stitches with one equals sign, choices with an asterisk when they should disappear after use and a plus sign when they must stay available, square bracket text so the choice wording is not repeated in the output when that reads better, and labeled gathers so dialogue loops back cleanly. 4. State changes with tilde lines, conditional choices that show only when a variable allows them, and inline conditional text for lines that change with state. 5. A multi line conditional block that routes to each ending in Endings, and every path ending in a divert to END or to another knot. No path should run out of choices. 6. Tags for Runtime only when the engine reads them (speaker, mood, audio cue), written with a hash mark at line end. 7. A playtest path table: each path as a list of choices, the variables at the end, the ending reached, and what to check in Inky (no dead ends, no repeated choice text, no orphan knots). 8. Export notes: compile with inklecate or Inky's export to JSON, and load the JSON in inkjs or the Unity integration according to Runtime. Constraints: - Every line of code must compile in current Ink. Do not invent functions or syntax; if unsure, keep it simple. - Keep prose lines short enough to read on a phone screen. No em dashes.