Technical Specification (TS) for developing a script for automatic generation of product descriptions using Gemini API
1. Project name: Development of an automated system for generating SEO-optimized product descriptions for the online store "https://www.pulsar.ua/" using Google Gemini API.
2. Customer:Online store "Pulsar" (specialization: anime goods, manga, figures, artbooks).
3. Project goal:Automate the process of creating unique, high-quality, SEO-optimized, and E-E-A-T-compliant descriptions of products in Russian and Ukrainian. Descriptions should be generated using Google Gemini API and strictly follow the detailed Style Guide and Prompt-structure provided by the Customer (hereinafter – "Guide"). The system must be capable of processing both existing and new batches of products.
4. Scope of work:* 4.1. Analysis and adaptation of the Guide:* Thorough study of the Style Guide and Prompt-structure provided by the Customer for description generation. * Development of an effective "master prompt template" for Google Gemini API based on the Guide. The template should include placeholders for dynamic data insertion for each product. *
4.2. Script development (preferred language – Python):* The script should read source product data from a provided file (e.g., CSV, Excel, Google Sheets). * For each product, the script should: * Generate an individual prompt by filling the "master prompt template" with current product data. * Send the formed prompt to Google Gemini API (using Customer's or Contractor's API key with subsequent cost reimbursement – upon agreement). * Process the API response, extracting generated descriptions in Russian and Ukrainian in the specified HTML format, as well as HTML comments with recommendations (meta-tags, Schema.org, etc., according to the Guide). * Ensure proper handling of API errors, request rate limits, and, if necessary, implement a retry mechanism. * The script should save the generated HTML descriptions and recommendations in a structured format (e.g., add to new columns in the source file or create a new output file) for easy verification and subsequent website import. *
4.3. Testing and debugging:* Conduct testing of the script and "master prompt template" on a pilot batch of products (10-20 units) provided by the Customer. * Iterative refinement of the "master prompt template" and script based on testing results and Customer feedback to achieve maximum compliance with the Guide and required description quality.
* 4.4. Documentation and handover:* Prepare brief documentation for the script: description of its operation, dependencies installation instructions, launch and configuration (e.g., data file path, API key input). * Transfer the source code of the script and the final version of the "master prompt template" to the Customer.
* 4.5. (Optional) Training:* Conduct a brief demonstration of the script's operation for the Customer.
5. Input materials (provided by the Customer):* Detailed Style Guide and Prompt-structure for description generation (document previously provided). * Product data file for pilot launch (and future full processing) in CSV or Excel format. Required fields for each product include (but are not limited to): Product name, Category, Current description (if any), Key features (material, dimensions, set contents, etc.), Brand, Series, Release date, Target audience, Unique selling propositions (USP), Contextual information (anime world, artist, etc.), list of relevant keywords (if any). * API key for Google Gemini (or agreement on using the Contractor's key and payment procedures). * Examples of existing descriptions that the Customer considers successful or unsuccessful (besides the Guide). * Access to a contact person from the Customer for prompt issue resolution.
6. Expected deliverables:* Fully functional script (source code in Python or another agreed language) implementing the functionality described in clause 4. * Final version of the "master prompt template" for Gemini API. * Generated descriptions (in the required HTML format with comments) for the pilot batch of products, saved in a structured format (e.g., CSV/Excel). * Brief usage instructions (README file).
7. Technical requirements and qualifications of the Contractor:* Mandatory:* Proven experience with large language model APIs (Google Gemini, GPT, or similar). * Deep understanding of prompt engineering principles. * Proficiency in Python (preferably) or another programming language suitable for this task (e.g., Node.js). * Experience with data processing in CSV, Excel, JSON formats. * Skills in programmatic HTML generation and parsing. * Attention to detail, ability to follow complex instructions and technical requirements precisely. * Ability to write clean, well-documented, maintainable code. * Desirable:* Experience automating tasks in e-commerce or content management. * Basic understanding of SEO in content context.
8. Interaction process and work stages (suggested):* Stage 1: Preparatory* The Contractor studies the TS, Guide, and provided materials. * An introductory call/meeting to discuss details, "master prompt" formation strategy, data format agreement. * Stage 2: Development and internal testing (Y days)* Contractor develops the "master prompt template" and initial script version. * Stage 3: Pilot launch and iterations (Z days, including Customer review time)* Launch of the script on the pilot batch of products. * Customer provides feedback on description quality. * Contractor makes adjustments to the "master prompt template" and/or script. Possibly multiple revision cycles. * Stage 4: Finalization and project delivery (W days)* Complete all revisions, prepare final documentation. * Transfer all results to the Customer. * Stage 5: (Optional) Warranty support (e.g., 1-2 weeks)* Fixing possible errors identified after delivery, consultations on script operation.
9. Acceptance criteria:* The script correctly processes the provided product data and generates descriptions via Gemini API without failures on the pilot batch. * Descriptions generated for the pilot batch strictly meet all Customer Guide requirements (HTML format, structure, volume, tone, keyword usage, E-E-A-T elements, naturalness, two-language versions, correct comments with recommendations). * Description quality for the pilot batch is rated as high and meets expectations by the Customer. * The script is documented and can be used by the Customer for processing new batches (independently or with minimal support). * Proper handling of standard API errors demonstrated.
10. Project timeline: Determined upon agreement with the Contractor after assessing the scope of work. Please provide your estimated timelines for each stage.
11. Budget and payment procedure: Please provide your commercial proposal (cost of work). Payment can be staged (e.g., 30% prepayment, 40% after successful pilot launch, 30% after project completion) or another scheme upon agreement. Clarify whether Gemini API costs are included in the work price or paid separately by the Customer.
12. Confidentiality: The Contractor commits not to disclose commercial information and data of the Customer obtained during the project. A separate NDA may be signed.
