anime-production-studio

byKommu Laxman

DAY 12 – AUDIO PRODUCTION STUDIO Implement: 1. Lip-sync integration. 2. Character dialogue synchronization. 3. Emotion-aware speech where supported. 4. Background music generation. 5. Cinematic music. 6. Emotional music. 7. Action music. 8. Romantic music. 9. Suspense music. 10. Sound effects. 11. Environmental sounds. 12. Audio upload. 13. Audio trimming. 14. Volume controls. 15. Audio preview. 16. Audio export. Allow users to assign dialogue and audio tracks to scenes. Support WAV, MP3 and other formats when compatible. Use real approved audio providers. Respect copyright and voice permissions. Do not create fake audio outputs or false lip-sync completion statuses.DAY 13 – MULTI-SCENE FILM PRODUCTION Build a scene-based film production system. Features: - Create scenes. - Add scene descriptions. - Scene prompts. - Assign characters. - Assign locations. - Assign dialogue. - Assign voice profiles. - Assign music. - Assign sound effects. - Upload reference images. - Scene ordering. - Scene duplication. - Scene editing. - Scene status. - Scene continuity notes. - Episode management. - Previous scene context. - Scene preview. Allow production of long films up to 3 hours through scene-based workflows, subject to provider and infrastructure limits. Add background generation queues and recoverable jobs. Never lose previously completed scenes when another scene fails.DAY 14 – PROFESSIONAL VIDEO EDITOR Build a functional video editing workspace. Features: - Timeline. - Multiple video tracks. - Audio tracks. - Scene arrangement. - Split clips. - Trim clips. - Delete clips. - Move clips. - Transitions. - Text overlays. - Subtitles. - Background music. - Sound effects. - Volume adjustment. - Preview player. - Undo and redo. - Autosave. - Project recovery. Provide a clean mobile-friendly interface and a powerful desktop editing workspace. Use actual media editing and rendering operations. If a function is not supported, clearly identify the limitation instead of showing an inactive button. Test timeline editing and save/reopen workflows.DAY 15 – ASSET LIBRARY AND SAVED PROMPTS Upgrade Upload Library and Saved Prompts. UPLOAD LIBRARY: - Image uploads. - Video uploads. - Audio uploads. - PDF uploads. - DOCX uploads. - Supported file previews. - File search. - Folders. - Tags. - Rename. - Move. - Delete with confirmation. - File metadata. - Storage usage. - Upload progress. - Retry failed uploads. SAVED PROMPTS: - Save prompts. - Edit prompts. - Categorize prompts. - Search prompts. - Favorite prompts. - Duplicate prompts. - Reuse prompts. - Link prompts to projects. Validate file types and sizes. Use secure file storage, access control and backup handling. Never expose private user files to other accounts.DAY 16 – QUALITY REVIEW AND EXPORT Build a complete quality review and export workflow. Include: - Project quality review. - Scene review. - Character consistency review. - Audio review. - Lip-sync review. - Subtitle review. - Scene continuity review. - Reuse-across-scenes notes. - Characters summary. - Previous episode continuity context. - Visual prompts. - Project status. - Character count. - Final review and submit. EXPORT: - Video export. - Image export. - Audio export. - PDF screenplay. - DOCX screenplay. - Supported resolutions. - Supported aspect ratios. - Supported formats. - Export progress. - Export history. - Retry failed exports. Show only formats and quality settings actually supported by the rendering pipeline. Never mark an incomplete export as completed.DAY 17 – CREDIT SYSTEM AND SETTINGS Upgrade the existing secure credit ledger. APPLICATION CREDIT POLICY: - Grant 100,000 LAXMAN AI credits daily. - Carry forward unused credits indefinitely. - Exactly 1 application credit per eligible generation/action. - Refund 1 credit for failed eligible generations. - Prevent duplicate charges. - Prevent duplicate refunds. - Use unique job IDs. - Use atomic database transactions. - Prevent negative balances. - Maintain audit history. Important: LAXMAN AI application credits are separate from 8080.AI platform credits and external provider costs. SETTINGS: - Account settings. - Profile settings. - Theme settings. - Language settings. - Notification settings. - Privacy settings. - Security settings. - API integration status. - Storage settings. - Credit history. - Export preferences. - Backup and recovery settings. Never silently create paid subscriptions or unexpected API charges. Test all credit transactions and settings changes.DAY 18 – SECURITY AND AUTHENTICATION Harden LAXMAN AI security. AUTHENTICATION: - Google sign-in. - Microsoft sign-in. - Email and password. - Password reset. - Passkeys where supported. - MFA. - Session management. - Secure logout. SECURITY: - Backend API key protection. - Environment variable security. - Role-based authorization. - Private project access. - Secure upload validation. - Rate limiting. - CSRF protection where applicable. - XSS protection. - SQL injection protection. - Secure session cookies. - Dependency vulnerability scanning. - Secret scanning. - Audit logging. Require confirmation before sensitive actions. Never expose private user data, passwords, API keys or tokens. Do not introduce an authentication provider that requires paid services without my approval. Run security tests and report vulnerabilities.DAY 19 – PERFORMANCE OPTIMIZATION AND TESTING Optimize the complete LAXMAN AI application. PERFORMANCE: - Fast dashboard loading. - Smooth navigation. - Efficient rendering. - Lazy loading. - Image optimization. - Video upload optimization. - Database query optimization. - Caching where appropriate. - Background processing. - Memory leak prevention. - Mobile performance. - Reliable error recovery. TEST: - All navigation. - All buttons. - All forms. - Authentication. - Project creation. - Project editing. - Uploads. - Image generation. - Video generation. - Audio generation. - Character Library. - Character consistency. - Video editing. - Export. - Credit transactions. - Settings. - Backup and recovery. Run unit, integration, end-to-end and security tests where available. Fix all critical and high-priority issues. Do not hide failed tests. Produce a complete test report.DAY 20 – FINAL LAXMAN AI RELEASE Act as the final engineering review team. Inspect the entire existing application. FINAL CHECKLIST: 1. Dashboard works. 2. All navigation works. 3. All studios work. 4. My Projects works. 5. Story Studio works. 6. Screenplay Writer works. 7. Character Library works. 8. Character consistency works within provider limitations. 9. Voice Studio works. 10. Music and sound effects work. 11. Video editor works. 12. Upload Library works. 13. Saved Prompts work. 14. Quality Review works. 15. Export History works. 16. Credit ledger works. 17. Settings work. 18. Authentication and authorization work. 19. Backups and recovery work. 20. Mobile and desktop layouts work. RELEASE REQUIREMENTS: - Run production build. - Run automated tests. - Run security scans. - Check environment configuration. - Check database migrations. - Verify API integrations. - Verify upload and export. - Verify error handling. - Verify recovery. - Verify performance. - Verify no exposed secrets. Create a staging release first. Show me the staging preview and a complete release report. Do not deploy to production until I explicitly approve. Never claim all features are complete if any feature is still unavailable, untested or incomplete. FINAL DELIVERABLE: A stable, secure, responsive and professional LAXMAN AI platform with documented working features, known limitations, test results and deployment instructions.