anime-video

byKommu Laxman

LAXMAN AI — ULTIMATE PRODUCTION-GRADE UPGRADE You are now acting as a world-class AI video platform engineering team consisting of senior full-stack developers, AI video-generation engineers, anime directors, animation pipeline architects, backend engineers, security specialists, QA engineers and performance engineers. Upgrade the EXISTING LAXMAN AI project into a fully functional, end-to-end AI anime production platform. IMPORTANT: Do not create a new project. Do not remove working features. Inspect the entire existing application, identify incomplete features, bugs, broken workflows, missing backend integrations and architectural weaknesses. Preserve all working functionality and improve it. MY MAIN REQUIREMENT: I must be able to submit a complete anime story, screenplay, characters, dialogue, scene descriptions, reference images, voices and production instructions. LAXMAN AI must process these details, generate the actual anime scenes, combine them in the correct order, and deliver a downloadable final anime episode video. A prompt generator or static UI is NOT an acceptable final product. 1. COMPLETE END-TO-END ANIME PRODUCTION Implement two complete production workflows. A. ONE-CLICK COMPLETE EPISODE User enters all production details once and selects Generate Complete Episode. The system must: 1. Validate the submitted project. 2. Understand and organize the screenplay. 3. Create an episode production plan. 4. Break the screenplay into scenes and shots. 5. Build a character continuity bible. 6. Prepare visual and animation instructions. 7. Generate required reference images when supported. 8. Submit actual video-generation jobs to configured providers. 9. Track each job and its status. 10. Store completed video clips. 11. Detect failed or incomplete scenes. 12. Allow failed scenes to be retried. 13. Assemble approved scenes in screenplay order. 14. Synchronize dialogue, voice, music and sound effects. 15. Generate subtitles when requested. 16. Validate the final video. 17. Provide a real downloadable MP4 file. B. SCENE-BY-SCENE PRODUCTION Allow users to generate and review individual scenes before assembling the episode. Every scene must have: - Scene description. - Script and dialogue. - Character references. - Character actions and expressions. - Location and background. - Camera angles and movements. - Lighting and color direction. - Animation style. - Voice and audio instructions. - Duration and aspect ratio. - Visual prompt and negative prompt. - Continuity information. Provide functional Generate, Preview, Approve, Regenerate, Retry and Delete actions. 2. PROFESSIONAL ANIME CONTINUITY ENGINE Build a reusable production bible for each project. Maintain: - Exact character appearance. - Face and hairstyle references. - Costume and accessories. - Character height and proportions. - Character relationships. - Voice identity. - Emotional state. - Location and environment. - Time of day and weather. - Props and important objects. - Scene order and story chronology. - Screen direction and camera continuity. - Previous-scene context. Never silently change an established character's appearance or story facts. If a continuity conflict is detected, show a warning and request approval. 3. REAL AI VIDEO GENERATION This is the highest-priority feature. Build a provider-independent video generation architecture. Requirements: - Integrate only real, documented AI video-generation APIs. - Keep all provider API keys on the server. - Support provider-specific capabilities and limits. - Validate prompts, input media and output formats. - Use background jobs for long-running generation. - Track queued, processing, completed, failed and cancelled states. - Save provider job IDs. - Support retries and safe recovery. - Prevent duplicate jobs. - Store generated clips and metadata. - Handle timeouts and provider quota errors. - Never claim that a video was generated if no valid output exists. If no video provider is connected, clearly explain how to configure one. Do not substitute fake video previews. 4. REAL VOICE AND AUDIO PIPELINE Implement real supported integrations for: - Telugu dialogue generation. - Character-specific voices. - Voice uploads. - Emotion-aware delivery where supported. - Dialogue timing. - Dubbing. - Lip-sync. - Background music. - Ambient audio. - Sound effects. - Audio mixing. Track which audio tasks are completed, unavailable or failed. 5. COMPLETE EPISODE ASSEMBLY Implement a real media assembly backend. Use FFmpeg or another suitable server-side media-processing solution. It must: - Combine scenes in the correct order. - Handle different clip durations. - Normalize video dimensions and frame rates where possible. - Synchronize audio. - Add subtitles when requested. - Mix BGM and SFX. - Add transitions where supported. - Generate a final MP4. - Verify that the output file exists and is playable. - Record export status and errors. Never display a fake download button or a false export-success message. 6. POWERFUL PROJECT WORKSPACE Fully implement: - Dashboard. - Story Studio. - Screenplay Writer. - One-Click Episode Generator. - Scene-by-Scene Generator. - Anime Image Generator. - Anime Video Generator. - Character Library. - Upload Library. - Voice Studio. - Music and SFX Studio. - Video Editor. - Episode Assembly. - My Projects. - Saved Prompts. - Export History. - Settings. - Provider Configuration. - Generation Job Monitor. Every visible button must perform its actual intended action or clearly show that its integration is not yet configured. 7. RELIABLE BACKEND AND DATA Use a suitable persistent database and object storage. Implement: - Authentication. - Project ownership. - Secure media access. - Autosave. - Recovery. - Generation job records. - Export records. - Error logs. - Backup and restore. - Safe deletion. - Data validation. Do not store important project data only in temporary browser state. 8. CREDIT LEDGER Implement the requested credit policy using a server-authoritative ledger: - 100,000 daily credits. - Unused credits carry forward indefinitely. - Exactly 1 credit per eligible successful generation job. - Failed jobs receive a refund. - Cancelled jobs before processing are not charged. - Each job has a unique ID. - Duplicate requests must not cause duplicate deductions. - Display balance and transaction history. Never simulate successful credit transactions. 9. SECURITY AND PRIVACY - Keep projects private by default. - Never expose API keys in frontend code. - Use secure server-side authorization. - Validate file uploads. - Restrict access to private project media. - Protect against duplicate and unauthorized actions. - Include confirmation before destructive operations. - Provide error logs without exposing secrets. - Do not automatically activate paid services. 10. PERFORMANCE AND QUALITY Optimize for Windows laptops and Android phones. Requirements: - Responsive layouts. - Smooth navigation. - Efficient media loading. - Pagination for large project lists. - Background processing. - Retry and recovery mechanisms. - Clear progress indicators. - Meaningful empty states. - Accessible error messages. - No broken routes. - No silent failures. - No incomplete placeholder screens. - No fake statistics or fake generated media. 11. AUTOMATED TESTING Create and run tests for: - Authentication. - Project creation. - Autosave. - Character persistence. - Upload validation. - Scene generation submission. - Job status updates. - Retry and cancellation. - Credit deduction and refund. - Episode assembly. - Export validation. - Mobile responsiveness. - Authorization and private media access. Fix discovered bugs before marking a feature complete. 12. STRICT COMPLETION RULES Do not mark any feature as COMPLETE unless: 1. Its frontend works. 2. Its backend works. 3. Its data persists. 4. Its errors are handled. 5. Its important workflows are tested. 6. Its external integrations are actually configured and verified. Maintain a feature status system: - COMPLETE AND TESTED - IMPLEMENTED, PROVIDER REQUIRED - IN PROGRESS - BLOCKED Do not hide missing integrations. 13. EXECUTION INSTRUCTIONS First inspect the current project and produce an implementation audit. Then fix the highest-priority issues and implement the application in phases. Prioritize this real production pipeline: STORY INPUT → SCREENPLAY ANALYSIS → SCENE BREAKDOWN → CHARACTER CONTINUITY → REAL AI VIDEO GENERATION → VOICE AND AUDIO → SCENE REVIEW → EPISODE ASSEMBLY → FINAL MP4 EXPORT. Continue working on the existing project until the available environment's implementation and testing work is complete. Do not stop after designing the dashboard. Do not replace actual generation with mock data. Do not claim unlimited free AI generation. Clearly disclose provider quotas, duration limits, costs and unavailable capabilities. FINAL OBJECTIVE: LAXMAN AI must become a genuine anime production workspace that can take my complete story and production instructions, generate real video scenes through configured AI providers, assemble them into an episode and deliver the verified final video file.