chore: prettier

Author: sinedied

.github/instructions/genaiscript.instructions.md

@@ -1,6 +1,6 @@
 ---
-applyTo: "**/*.genai.*"
-description: "Instructions for working with GenAIScript files"
+applyTo: '**/*.genai.*'
+description: 'Instructions for working with GenAIScript files'
 ---
 
 ## GenAIScript Code Generation Instructions

.github/prompts/create-agents.md.prompt.md

@@ -24,50 +24,64 @@ When creating the `AGENTS.md` file, prioritize clarity, completeness, and action
 ## Instructions
 
 1. Examine the current project to understand its context, requirements, constraints, architecture, tech stack and specificities, and any existing files that may provide insights.
-  - For example, look for files that may contain the project name, idea, vision, requirements, technology stack and constraints. This may include README files, project documentation, configuration files (e.g., package.json, pyproject.toml, etc.), CI/CD workflows and any other relevant files.
-  - If the project is a monorepo or has multiple distinct project roots, identify the relevant subdirectories that may require their own `AGENTS.md` files.
+
+    - For example, look for files that may contain the project name, idea, vision, requirements, technology stack and constraints. This may include README files, project documentation, configuration files (e.g., package.json, pyproject.toml, etc.), CI/CD workflows and any other relevant files.
+    - If the project is a monorepo or has multiple distinct project roots, identify the relevant subdirectories that may require their own `AGENTS.md` files.
 
 2. Once you have all the necessary information, create or update the `AGENTS.md` file with all relevant project context, requirements, stack and constraints for the code agents that will implement the project.
-  - When doing so, use this the template for structuring the document:
+
+    - When doing so, use this the template for structuring the document:
+
     ```md
     # [project_name]
+
     [Project summary]
 
     ## Overview
+
     - [Brief description of what the project does, its purpose and audience]
     - [Architecture overview if complex]
     - [Project structure if relevant]
 
     ## Key Technologies and Frameworks
+
     - [List of main technologies, frameworks, and libraries used in the project]
 
     ## Constraints and Requirements [if any]
+
     - [Any specific constraints, requirements, or considerations for the project]
 
     ## Challenges and Mitigation Strategies [if any]
+
     - [Potential challenges and how they will be addressed]
 
     ## Development Workflow [if applicable]
+
     - [Most important scripts, commands, and tools for development, testing, and deployment. How to start dev server, run tests, build for production, etc.]
 
     ## Coding Guidelines [if any]
+
     - [Any specific coding standards, style guides, or best practices to follow]
 
     ## Security Considerations [if any]
+
     - [Any security practices or considerations relevant to the project]
 
     ## Pull Request Guidelines [if any]
+
     - [Any specific guidelines for creating pull requests, such as, title format, required checks, review process, commit message conventions, etc.]
 
     ## Debugging and Troubleshooting [if applicable]
+
     - [Common issues and solutions, logging patterns, debug configuration, performance considerations]
     ```
-  - If a section is not relevant, you can omit it.
-  - **Be specific and concise**: include exact commands, and information from the provided context, do not make any assumptions or add unnecessary details.
-  - Only use information you found to fill the sections.
-  - Use standard Markdown formatting.
-  - If needed, you can add specific sections relevant to the project that are not covered by the template if they provide important context for the code agents.
-  - If the file already contains enough relevant information, you can skip this step.
+
+    - If a section is not relevant, you can omit it.
+    - **Be specific and concise**: include exact commands, and information from the provided context, do not make any assumptions or add unnecessary details.
+    - Only use information you found to fill the sections.
+    - Use standard Markdown formatting.
+    - If needed, you can add specific sections relevant to the project that are not covered by the template if they provide important context for the code agents.
+    - If the file already contains enough relevant information, you can skip this step.
 
 ## Best Practices
 
@@ -81,6 +95,7 @@ When creating the `AGENTS.md` file, prioritize clarity, completeness, and action
 ## Monorepo Considerations
 
 For large monorepos:
+
 - Place a main `AGENTS.md` at the repository root
 - Create additional `AGENTS.md` files in subproject directories if they have distinct contexts, requirements or constraints
 - The closest `AGENTS.md` file takes precedence for any given location

.github/scripts/create-banner.genai.js

@@ -1,41 +1,41 @@
-import { existsSync, mkdirSync, readdirSync, readFileSync, writeFileSync } from "node:fs";
-import { join } from "node:path";
+import { existsSync, mkdirSync, readdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { join } from 'node:path';
 
 // Must be openai:gpt-image-1 or azure:gpt-image-1
-const imageModel = "azure:gpt-image-1";
+const imageModel = 'azure:gpt-image-1';
 
 script({
-  title: "Create banner",
-  description: "Create a social banner for a software project",
+  title: 'Create banner',
+  description: 'Create a social banner for a software project',
   parameters: {
     question: {
-      type: "string",
-      description: "Context for the banner",
+      type: 'string',
+      description: 'Context for the banner',
       required: true,
     },
     text: {
-      type: "string",
-      description: "Text to include in the banner",
-      required: true
+      type: 'string',
+      description: 'Text to include in the banner',
+      required: true,
     },
     count: {
-      type: "integer",
-      description: "Number of banner variations to generate",
+      type: 'integer',
+      description: 'Number of banner variations to generate',
       default: 4,
     },
   },
 });
 
 function getNextBannerNumber() {
-  const bannerDir = "banner";
+  const bannerDir = 'banner';
 
   if (!existsSync(bannerDir)) {
     return 1;
   }
 
   const existingFiles = readdirSync(bannerDir)
-    .filter(file => file.startsWith("banner-") && file.endsWith(".png"))
-    .map(file => {
+    .filter((file) => file.startsWith('banner-') && file.endsWith('.png'))
+    .map((file) => {
       const match = file.match(/banner-(\d+)\.png$/);
       return match ? parseInt(match[1], 10) : 0;
     })
@@ -44,38 +44,33 @@ function getNextBannerNumber() {
   return existingFiles.length > 0 ? existingFiles[0] + 1 : 1;
 }
 
-defTool(
-  "gen_image",
-  "Generate an image",
-  { prompt: "" },
-  async (args) => {
-    const { image } = await generateImage(args.prompt, {
-      size: "1536x1024",
-      model: imageModel,
-    });
+defTool('gen_image', 'Generate an image', { prompt: '' }, async (args) => {
+  const { image } = await generateImage(args.prompt, {
+    size: '1536x1024',
+    model: imageModel,
+  });
 
-    const bannerDir = "banner";
-    if (!existsSync(bannerDir)) {
-      mkdirSync(bannerDir, { recursive: true });
-    }
+  const bannerDir = 'banner';
+  if (!existsSync(bannerDir)) {
+    mkdirSync(bannerDir, { recursive: true });
+  }
 
-    const nextNumber = getNextBannerNumber();
-    const targetFilename = join(bannerDir, `banner-${nextNumber}.png`);
+  const nextNumber = getNextBannerNumber();
+  const targetFilename = join(bannerDir, `banner-${nextNumber}.png`);
 
-    const imageData = readFileSync(image.filename);
-    writeFileSync(targetFilename, imageData);
+  const imageData = readFileSync(image.filename);
+  writeFileSync(targetFilename, imageData);
 
-    env.output.appendContent(`[![banner](${targetFilename})](${targetFilename})`);
-    return targetFilename;
-  },
-);
+  env.output.appendContent(`[![banner](${targetFilename})](${targetFilename})`);
+  return targetFilename;
+});
 
-def("QUERY", env.vars.question);
+def('QUERY', env.vars.question);
 
 $`## Instructions
 Create a prompt for gpt-image-1 to generate a professional social media banner suitable for OpenGraph, Twitter, and other social sharing platforms. Context and inspiration: <QUERY>.
 Do not use the context words directly as text in the banner, but rather as inspiration for the design.
-${env.vars.text ? `Include the text: "${env.vars.text}" in the banner.` : ""}
+${env.vars.text ? `Include the text: "${env.vars.text}" in the banner.` : ''}
 Target aspect ratio is 2:1 ratio - design for this ratio and make it fit the actual size of 1536x1024 pixels, using black bars.
 Characteristics of the banner: Modern, professional, visually appealing for social media, bright colors, clean design, readable text elements if any, suitable for software project promotion.
 The banner should work well as a social media preview image and represent the project effectively.

.github/scripts/create-logo.genai.js

@@ -1,36 +1,36 @@
-import { existsSync, mkdirSync, readdirSync, readFileSync, writeFileSync } from "node:fs";
-import { join } from "node:path";
+import { existsSync, mkdirSync, readdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { join } from 'node:path';
 
 // Must be openai:gpt-image-1 or azure:gpt-image-1
-const imageModel = "azure:gpt-image-1";
+const imageModel = 'azure:gpt-image-1';
 
 script({
-  title: "Create logo",
-  description: "Create the logo for a software project",
+  title: 'Create logo',
+  description: 'Create the logo for a software project',
   parameters: {
     question: {
-      type: "string",
-      description: "2-3 keywords to use in the logo",
+      type: 'string',
+      description: '2-3 keywords to use in the logo',
       required: true,
     },
     count: {
-      type: "integer",
-      description: "Number of logo variations to generate",
+      type: 'integer',
+      description: 'Number of logo variations to generate',
       default: 4,
     },
   },
 });
 
 function getNextLogoNumber() {
-  const logoDir = "logo";
+  const logoDir = 'logo';
 
   if (!existsSync(logoDir)) {
     return 1;
   }
 
   const existingFiles = readdirSync(logoDir)
-    .filter(file => file.startsWith("logo-") && file.endsWith(".png"))
-    .map(file => {
+    .filter((file) => file.startsWith('logo-') && file.endsWith('.png'))
+    .map((file) => {
       const match = file.match(/logo-(\d+)\.png$/);
       return match ? parseInt(match[1], 10) : 0;
     })
@@ -39,33 +39,28 @@ function getNextLogoNumber() {
   return existingFiles.length > 0 ? existingFiles[0] + 1 : 1;
 }
 
-defTool(
-  "gen_image",
-  "Generate an image",
-  { prompt: "" },
-  async (args) => {
-    const { image } = await generateImage(args.prompt, {
-      size: "1024x1024",
-      model: imageModel,
-    });
+defTool('gen_image', 'Generate an image', { prompt: '' }, async (args) => {
+  const { image } = await generateImage(args.prompt, {
+    size: '1024x1024',
+    model: imageModel,
+  });
 
-    const logoDir = "logo";
-    if (!existsSync(logoDir)) {
-      mkdirSync(logoDir, { recursive: true });
-    }
+  const logoDir = 'logo';
+  if (!existsSync(logoDir)) {
+    mkdirSync(logoDir, { recursive: true });
+  }
 
-    const nextNumber = getNextLogoNumber();
-    const targetFilename = join(logoDir, `logo-${nextNumber}.png`);
+  const nextNumber = getNextLogoNumber();
+  const targetFilename = join(logoDir, `logo-${nextNumber}.png`);
 
-    const imageData = readFileSync(image.filename);
-    writeFileSync(targetFilename, imageData);
+  const imageData = readFileSync(image.filename);
+  writeFileSync(targetFilename, imageData);
 
-    env.output.appendContent(`[![logo](${targetFilename})](${targetFilename})`);
-    return targetFilename;
-  },
-);
+  env.output.appendContent(`[![logo](${targetFilename})](${targetFilename})`);
+  return targetFilename;
+});
 
-def("QUERY", env.vars.question);
+def('QUERY', env.vars.question);
 
 $`## Instructions
 Create a prompt for gpt-image-1 to generate a professional-looking logo icon suitable for a software project. Context and inspiration: <QUERY>.