Suggested Prompts

• What component are available?
• How many components in Nuxt UI?
• Create a button component
• Create a FAQ component
• Explain how AI works in a few words

• Explain how AI works in a few words
• 90 Day Goals
• Resources for Smart Goals
• NOVA
• I'm the Steve
• Leads Offshore Resource
• Setup
• Grasp
• To to each to understand issues
• Tech Connect

Developing

Useful for me....

The ability to go between different frameworks easily. For each component, I want to show a template code example for html, htl (Sightly), bash, ruby, python, php, vue-sfc, sveltekit, angular-template, and jsx. This will help me quickly adapt to different frameworks without having to search for examples.

Organize assets

Help me to organize my assets/css folder to accomodate multiple themes. Structure it so that it supports the modern CSS cascading layers used by Tailwind CSS v4, and for an easy-to-understand for beginners or juniors being welcomed to contribute or learn from the code base

Email from VS Code project

Since Nuxt 3 has both client and server is it easily possible to have an EasyEmailer, which would allow for me to author markdown in my project, and email recipients an HTML email based on the Email template defined and a Vue SFV or MDC markdown content document.

"@vue-email/components": "^0.0.21", "@vue-email/render": "^0.0.9", "@types/nodemailer": "^6.4.17", "@vue-email/compiler": "^0.8.14", "@vue-email/nuxt": "^0.8.19", "nodemailer": "^7.0.3", "nuxt-mail": "^6.0.2", "nuxt-mailer": "^0.11.0",

Make base url, api_url, and asset paths

In my Nuxt 3 project, I need to link to assets, http://localhost:3000 to pull from a public runtimeConfig and/or set BASE_URL=http://localhost:3000, ASSET_PATH=/resources variable I'll need to update the locations where the URL is inlined to be replaced with env config base_url setting

Patch ot upgrade to flat config support

Build the Perfect #AI Prompt by Getting Help From #ChatGPT

• Act as a prompt engineer
• Review the following prompt for me
• Optimize it to make it better
• And ask me any questions before proceeding

Think step by step

Prompts

Continuing with Figma plugin capabilities, I now need to extract TextStyle's and augment a design systems style dictionary transforms to use the extracted values. Do you have knowledge about the figma.getLocalTextStylesAsync method?

What I know so far...

There is a figma.getLocalTextStylesAsync method.

My export should look like...

{
  "text": {}
}

Another sample page with the following

Typography Text Styles pulled from figma

title group h1 48/56 h2 h3 h4 h5

subhead/1 group

• light
• regular
• bold

subhead/2 group

• light
• regular
• bold

body

• light
• regular
• bold

caption

• light
• regular
• bold

eyebrow

• light
• regular
• bold

You will rewrite text according to a specific writing style. Follow these steps:

Review the writing style guidelines:

<writing_style>

• Your writing style is spartan and informative.
• Use clear, simple language.
• Employ short, impactful sentences.
• Incorporate bullet points for easy readability.
• Use frequent line breaks to separate ideas.
• Use active voice; avoid passive voice.
• Focus on practical, actionable insights.
• Use specific examples and personal experiences to illustrate points.
• Incorporate data or statistics to support claims when possible.
• Ask thought-provoking questions to encourage reader reflection.
• Use "you" and "your" to directly address the reader.
• Avoid metaphors and clichés.
• Avoid generalizations.
• Do not include common setup language in any sentence, including: in conclusion, in closing, etc.
• Do not output warnings or notes-just the output requested.
• Do not use hashtags.
• Do not use semicolons.
• Do not use emojis.
• Do not use asterisks.
• Do not use adjectives and adverbs.
• Do NOT use these words:

"can, may, just, that, very, really, literally, actually, certainly, probably, basically, could, maybe, delve, embark, enlightening, esteemed, shed light, craft, crafting, imagine, realm, game-changer, unlock, discover, skyrocket, abyss, not alone, in a world where, revolutionize, disruptive, utilize, utilizing, deep, tapestry, illuminate, unveil, pivotal, intricate, elucidate, hence, furthermore, realm, however, harness, exciting, groundbreaking, cutting-edge, remarkable, it, remains to be seen, glimpse into, navigating, landscape, stark, testament, in summary, in conclusion, moreover, boost, skyrocketing, opened up, powerful, inquiries, ever-evolving" </writing_style>

Rewrite the following text according to the writing style guidelines:

<user_text› </user_text>

Output your rewritten version inside ‹rewritten_text› tags. Adhere to the writing style guidelines.

Do not include any explanations or comments about your changes.

I inherited a project that consists of just 4 components. I've just been adding on to what was provided and haven't been thinking of best-practices. propably opportunities for hooks an for some resuable components and perhaps extracting repeated patterns, just otherwise making it a more modern React app architecture, friendly for inviting new team members to participate or contribute once the MVP is release. Please provide recommendations, document as needed, adhere to naming conventions, etc.