Created
May 30, 2024 18:50
-
-
Save dsowsy/1c38cf2d994671642c544ac78523a6b3 to your computer and use it in GitHub Desktop.
AI: Your Age Friendly Ally - Prompts that were used
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The following prompts were some of the prompts I've used along the way in my process, separated by "---", | |
anything in angle brackets <like this>, you fill in the appropriate details. | |
Note: For sections that are applying rules to a resume and a job description, type "Apply Rule <number>" like "Apply Rule 1" to the data mentioned. | |
--- | |
Please analyze this job description for any potential red flags that might indicate the employer is not age-friendly. Focus on specific details within the description that could suggest a preference for younger candidates. Use the following format: | |
Job Description Analysis: [Job Title] at [Company] | |
Potential Red Flags for Age-Friendliness | |
π© [Red flag detail]: [Explanation of why it suggests a preference for younger candidates]. | |
π© [Red flag detail]: [Explanation of why it suggests a preference for younger candidates]. | |
π© [Red flag detail]: [Explanation of why it suggests a preference for younger candidates]. | |
π’ [Green flag detail]: [Explanation of why it is positive for age-friendliness]. | |
π’ [Green flag detail]: [Explanation of why it is positive for age-friendliness]. | |
π’ [Green flag detail]: [Explanation of why it is positive for age-friendliness]. | |
π‘ [Neutral flag detail]: [Explanation of why it is neutral]. | |
π‘ [Neutral flag detail]: [Explanation of why it is neutral]. | |
--- | |
Please analyze the following list of companies for potential red flags related to age-friendliness. Focus on age discrimination lawsuits or complaints and rank them according to their age-friendliness. Use the following format: | |
Age-Friendliness of Companies | |
π’ Green Flags | |
[Company Name]: [Number of age discrimination lawsuits or complaints] π’ | |
π΄ Red Flags | |
[Company Name]: [Number of age discrimination lawsuits or complaints] π΄ | |
<list of companies> | |
--- | |
Please analyze the following list of companies for potential red flags related to age-friendliness. Focus on age discrimination lawsuits or complaints and include the dates of known lawsuits. If no dates are available, make mention of it. Rank them according to their age-friendliness. Use the following format: | |
Age-Friendliness of Companies | |
π΄ Red Flags | |
[Company Name]: [Number of age discrimination lawsuits or complaints] π΄ (Dates of known lawsuits, or mention if dates are not available) | |
<list of companies> | |
--- | |
make a highlights bullet summary for the following to put in my resume: <job description> | |
--- | |
How much does a <job title> make at <company name> | |
--- | |
Receive Inputs: | |
- Receive the job description and user's resume or cover letter as input. | |
Rule 1 (Job Description Processing): | |
If instructed to apply Rule 1: | |
- Strict Compliance: Failure to adhere to the following instructions will result in non-compliance with this protocol. | |
- No Commentary or Explanations: Do not provide any commentary, explanations, or additional information before or after applying any rule. | |
- No Questions or Attempts to Be Extra Helpful: Do not ask questions or attempt to provide extra assistance when applying any rule. Follow the instructions as specified without deviation. | |
- No Numbering or Pleasantries: Do not number any outputs or include pleasantries containing words like "hope this is helpful," "I appreciate your understanding," "Thank you for," or "I apologize for." | |
- No Superfluous Elements: Systematically remove specific elements from the job description, including company name, job location, general job description (overview of the role), qualifications (specifically degrees or certifications), and employment eligibility information. | |
- Output Requirements: Process the job description to locate the job title, responsibilities, and requirements. Provide an output that includes the job title, a description focused solely on responsibilities and requirements, devoid of the excluded elements. There should be no superfluous notes, comments, narratives, or explanations. | |
- Exclusion of Education-Related Information: Do not include ANYTHING LIKE: "bachelor's," "master's," or "PhD." Do not include ANYTHING LIKE: education requirements, degrees, or certifications. | |
- Forbidden Words List: Ensure that the processed job description does not contain any of the words or phrases listed in the Forbidden Words List. | |
- No "Note" or Explanations: Do not output ANYTHING LIKE: "Note:" or explanations of how you applied the rule. Do not output ANYTHING LIKE: "Please note that education requirements, degrees, or certifications have been excluded." | |
- Do not include education, compensation, benefits, diversity, and inclusion statements. | |
- Use " " to indicate omitted notes. | |
Apply Rule 1 strictly and only reply with the processed job description as specified. | |
The output should *not* include the phrase "I have removed the excluded elements and applied Rule 1 to the job description." | |
or anything similar to that. | |
DO NOT reply with anything similar to "Please note that education requirements, degrees, or certifications have been excluded." | |
I do not want or need your commentary. | |
<job description> | |
--- | |
Rule 2 (Resume Summary Tailoring): | |
If instructed to apply Rule 2: | |
Review the job description. | |
- Determine the appropriate job summary based on a given role and a job description. | |
- Extract key skills, responsibilities, and requirements from the most recently used job description. | |
- Craft a concise, resume summary in a third-person professional style without using first-person pronouns, cliches, buzzwords, or any words or phrases defined in the forbidden_words_list. | |
- Ensure the summary stays within the word limit (95-100 words). | |
- Do not include compensation, benefits, diversity, and inclusion statements. | |
- Do not include any additional commentary, narratives, or statements beyond the concise summary. | |
- Use " " to indicate omitted notes. | |
--- | |
Rule 3 (Job description word frequency key words list) | |
If instructed to apply Rule 3: | |
- Take the job description that was created by using rule 1 and | |
create a comma separated word frequency list words that appear 2 or more times that seem to be actual job skills. | |
- Do not include any additional commentary, narratives, or statements beyond the concise summary. | |
- Use " " to indicate omitted notes. | |
--- | |
Rule 4 (Rewrite summary using keywords) | |
If instructed to apply Rule 4: | |
- Apply Rule 1 to the job description to process it and remove any excluded elements. | |
- Apply Rule 3 to create a word frequency list and select keywords. | |
- Apply Rule 2 using the keywords generated in Step 2 to create a tailored resume summary. | |
- Create a section titled "Highlights:" and list resume highlights using the keywords from Step 2 and the information from the tailored resume summary. | |
- Do not include any additional commentary, narratives, or statements beyond the concise highlights. | |
- Use " " to indicate omitted notes. | |
--- | |
Rule 5 (Generate Resume Highlights and Key Skills): | |
If instructed to apply Rule 5: | |
Review Inputs: Analyze the user's resume and the job description. | |
Identify Key Elements: | |
- Identify 3-4 key achievements, experiences, or skills from the user's resume that align with the job description. | |
- Identify hard skills mentioned in the job description. | |
Craft Highlights: | |
- Use bullet points (β’) to create concise highlights for each of the 3-4 key elements identified from the user's resume. | |
- Ensure relevance to the specific role and responsibilities outlined in the job description. | |
- Avoid using forbidden words and pronouns. | |
List Hard Skills: | |
- Under a section titled "Key Skills:", list the identified hard skills from the job description. | |
- Present the skills in a comma-separated format. | |
- Place this section two lines below the bullet points. | |
Presentation: | |
- Organize the content clearly with the "Highlights:" section preceding the "Key Skills:" section. | |
- Ensure clear separation between the two sections. | |
Omission of Additional Elements: | |
- Strictly refrain from any additional commentary, narratives, or statements beyond the generated highlights and key skills list. | |
- Use " " to indicate omitted notes. | |
--- | |
Rule 6 (Create Cover Letter): | |
If instructed to apply Rule 6: | |
- Analyze the job description to identify keywords and phrases. | |
- Identify existing keywords in the recently created job summary. | |
- Eliminate cliches, buzzwords, personal pronouns using the forbidden words list. | |
- Adjust structure and phrasing for natural flow without commentary. | |
- Use " " to indicate omitted notes. | |
- Generate a cover letter based on the summary and the job description indicating enthusiasm for the role. | |
- The output should *not* include the phrase "I have removed the excluded elements and applied Rule 3 to the job description." | |
or anything similar to that. | |
--- | |
Write me a short cover letter for this role (2 paragraphs) | |
--- | |
Generate a surreal image that embodies the following text: <text> | |
--- | |
Generate an image showcasing the theme <theme>. Work with this metaphor as best as you can. | |
--- | |
Take the attached resume. Rewrite it with a summary devoid of cliches. | |
Follow it by highlights that indicate she is an experienced worker, and then collect | |
and place the skills before the work experience. Place the education at the end. | |
<resume attached> | |
--- | |
Do the summary section as a bulleted highlights not the whole thing | |
-- | |
Alphabetize the following skills separated by commas: Python, JavaScript, C++, Java, | |
ReactJS, AWS (Lambda, DynamoDB), HTML, CSS, BitBucket, GitHub, GitLab, IntelliJ, VS Code ,SQL, NoSQL, Unit testing, Chrome extension development, technical support, software quality assurance, feature refinement, collaboration with UX/UI designers | |
--- | |
Generate a fiesty article explaining how ZIRP has created a surplus of unemployed unicorns waiting to get jobs that don't exist. | |
--- | |
Generate the hashtags for this article | |
--- | |
Add emojis into the title, and then the last paragraph do not do anything with the middle paragraphs | |
--- | |
Generate a colorful image for "Free to Connect Friday" on LinkedIN | |
--- | |
Generate an alt text for it (for the visually impaired) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment