Act like a licensed, highly experienced with expertise in , combining conventional medicine with evidence-informed holistic and integrative care.
Your objective is to design a comprehensive, safe, and personalized treatment plan for a patient diagnosed with . The goal is to while supporting overall physical, mental, and emotional well-being, taking into account the patient’s unique context and constraints.
Task:
Create a tailored treatment plan for a patient with that integrates conventional treatments, complementary therapies, lifestyle interventions, and natural or supportive alternatives as appropriate.
Step-by-step instructions:
1) Briefly summarize , including common causes, symptoms, and progression relevant to .
2) Define key patient-specific considerations, including age (), lifestyle (), medical history (), current medications (), and risk factors ().
3) Recommend conventional medical treatments (e.g., medications, procedures, therapies) appropriate for , clearly stating indications, benefits, and precautions.
4) Propose complementary and holistic approaches (e.g., nutrition, movement, mind-body practices, physical modalities) aligned with the patient’s abilities and preferences.
5) Include herbal remedies, supplements, or natural alternatives where appropriate, noting potential benefits, contraindications, and interactions with .
6) Address lifestyle and environmental factors such as sleep, stress, work or daily routines, physical activity level, and social support.
7) Provide a practical sample routine or care plan (daily or weekly) showing how these recommendations can be realistically implemented.
8) Add clear safety notes, limitations, and guidance on when to consult or defer to qualified healthcare professionals.
Requirements:
- Personalize recommendations using the provided variables.
- Balance creativity with clinical responsibility and evidence-based caution.
- Avoid absolute claims, guarantees, or diagnoses beyond the given inputs.
- Use clear, compassionate, and accessible language.
Constraints:
- Format: Structured sections with clear headings and bullet points.
- Style: Professional, empathetic, and practical.
- Scope: Focus strictly on and patient-relevant factors.
- Self-check: Verify internal consistency, safety, and appropriateness before finalizing.
Take a deep breath and work on this problem step-by-step.
It is ideal for literature reviews where consistency, clarity, and proper citation structure.
I am preparing a BibTeX file for an academic project.
Please convert the following references into a single, consistent BibTeX format with these rules:
Use a single citation key format: firstauthorlastname + year (e.g., esteva2017)
Use @article for journal papers and @misc for web tools or demos
Include at least the following fields: title, author, journal (if applicable), year
Additionally, include doi, url, and a short abstract if available
Ensure author names follow BibTeX standards (Last name, First name)
Avoid Turkish characters, uppercase letters, or long citation keys
Output only valid BibTeX entries.
"Curate a collection of expert tips, advanced learning strategies, and high-quality resources (such as books, courses, tools, or communities) for mastering [topic] efficiently. Emphasize credible sources and actionable advice to accelerate expertise."
For techs and engineers who need an accurate, importable I/O list from a schematic without the AI quietly guessing contact types or ranges.
I want you to act as a controls technician building an I/O list from electrical drawings. Below is the PLC I/O sheet, typed or pasted as printed: Drawing number and revision. Target platform: any.
Transcribe it into a table with one row per channel:
Rack/Slot/Channel | Address as printed | Wire number | Terminal | Field device tag | Description as printed | Device type | NO/NC | Signal type and range | Proposed PLC tag name | Notes
Rules:
1. Copy text exactly as printed. Do not correct spelling, tag names or wire numbers. Mark anything unreadable as ILLEGIBLE.
2. Do not fill NO/NC, signal type or range from typical values. If the sheet does not state it, write NOT ON DRAWING.
3. Spare channels get their own rows marked SPARE.
4. Proposed tag names follow this convention: Area_Device_Function. Keep them separate from the printed text.
5. After the table, list: duplicate addresses or wire numbers, channels with a device but no description, redlines or clouded changes you noticed, and questions for the drawing owner.
Give the table as CSV as well, so I can import it.
=== DRAWING SHEET ===
Paste or describe the I/O sheet
For controls techs and engineers preparing a FAT or SAT who want every spec clause tested, including the failure cases.
I want you to act as a commissioning engineer writing a Factory Acceptance Test (FAT) plan. Machine: a sorting conveyor with three diverters. Below is the functional specification, numbered by clause.
Write test cases as a table:
Test ID | Spec clause | Precondition | Action (what I do or force) | Expected result (exact tags, values, HMI text and timing) | Pass/Fail | Witness
Cover, for every clause:
1. Normal operation: start, run, stop, mode changes.
2. Each sensor stuck on, stuck off and flickering. Each actuator failing to move.
3. Faults during stop and during reset. Two faults at once.
4. Power cycle, controller stop/run and communication loss: what must restart, what must not.
5. Boundary values: test just under and just over every timer and setpoint in the spec.
Where the spec does not define the reaction, write NOT IN SPEC and add a question. Do not invent behaviour.
After the table give: a clause-to-test coverage matrix (any clause with no test is a gap), and the order to run the tests so I force and clear signals the fewest times.
=== FUNCTIONAL SPECIFICATION ===
Paste spec
For techs and engineers starting up new or rebuilt equipment who want a checklist that follows the real order of work, down to every I/O point.
I want you to act as a commissioning lead. Equipment: a packaging line with 4 VFD conveyors, 2 pneumatic diverters and a PLC panel. Below are the I/O list and the functional description.
Build a commissioning checklist in the order the work is actually done:
Step | Phase | Check | Method / tool | Expected result | Done by | Initials and date
Phases, in order:
1. Before power: panel inspection, terminations, labels, grounding, network cabling.
2. Power-up: supplies, controller and I/O status, network communications, firmware and program version recorded.
3. Point-to-point I/O check: one row per I/O point from my list, input simulated or operated at the device, seen at the PLC; outputs forced and seen at the device.
4. Devices: motor rotation, VFD parameters recorded, valve and actuator travel and feedback, analog ranges checked against a reference.
5. Functional tests per the description, then fault and recovery tests.
6. Handover: backups, as-built markups, open punch list.
Use only devices in my I/O list. Where the description is missing information I need for a check, write QUESTION.
Also give the punch list template: Item | Location | Description | Severity | Owner | Target | Closed.
=== I/O LIST ===
Paste I/O list
=== FUNCTIONAL DESCRIPTION ===
Paste description