my-os

Use this skill when designing, creating, or modifying API endpoints; defining contracts between services; evaluating protocol choices (REST, GraphQL, gRPC, WebSockets); versioning or deprecating an API; designing error responses or pagination; or reviewing an existing API for consistency, security, or ergonomics. Signal phrases: "design the API", "create an endpoint", "REST", "GraphQL", "gRPC", "API versioning", "backward compatible", "breaking change", "error response", "pagination", "rate limiting", "API contract", "OpenAPI", "Protobuf", "webhook", "idempotency", "deprecation", "endpoint structure". Also activate when API responses expose database column names, collection endpoints return unbounded results, or breaking changes are being introduced to active versions without a migration plan. Do NOT shape the API contract around implementation convenience — design for the consumer and the future.

Use this skill when designing system boundaries, data flows, component interfaces, or making structural technology decisions. Activated when the user is initializing a new project, service, or major feature; designing data flow between components; breaking apart a legacy system; defining folder structures or project organization; evaluating core technology or framework choices; or when the current system fails to scale. Examples: "how should I structure this?", "should this be a microservice?", "design the architecture for X", "what's the best way to organize this codebase?", "how should data flow between these components?". Do NOT use for pure implementation (use coding skill) or infrastructure provisioning (use devops-infra skill).

Use this skill when analyzing a brand's positioning, auditing an existing website's brand communication, identifying mismatches between brand intent and visual/copy execution, or defining the brand strategy for a new business from scratch. Activated when the user asks to "audit the brand", "diagnose the brand's positioning", "align copy and visuals to the brand", "define the brand perception", "what phase is this brand in", or "how does the brand extend to visuals and animations". Do NOT use for writing actual copy (use copywriting), editing copy (use copy-editing), or configuring animations without brand direction (use cinematic-motion).

Use this skill when designing or implementing highly animated, immersive, and cinematic web user interfaces. Activated when the user asks to build animations, integrate GSAP, use ScrollTrigger, build Three.js R3F models, implement video-scrubbing, image mask scaling, modulo-based infinite sliders, bento grid lighting, or premium interactive web layouts. Do NOT use for standard, non-animated web interfaces or pure backend APIs.

Use this skill when building cinematic, animated, or immersive web experiences. Covers scroll-driven storytelling (GSAP, ScrollTrigger, SplitText, video scrubbing, parallax, mask reveals), 3D product showcases (R3F, Zustand, studio lighting, model switching, video textures), layout composition (bento grids, masonry, power lines, overlapping typography), and register-aware creative direction. Activated when the user asks to "build a cinematic landing page", "add scroll animations", "create a 3D product viewer", "scrub video on scroll", "build a bento grid with scroll reveals", "animate text on scroll", "add parallax effects", "create a mask reveal", "build an infinite slider", "implement model switching", "add studio lighting to 3D scene", "map video textures on 3D screens", or any task producing premium animated web surfaces. Also activated for FFmpeg keyframe encoding, GSAP ScrollTrigger configuration, SplitText typography, gltfjsx model conversion, Zustand state for 3D, or scroll-bound timeline orchestratio

Use this skill when writing, modifying, or generating code of any kind. Activated when the user asks to build features, implement functions, create components, write endpoints, set up forms, wire things together, or produce any working implementation. Trigger phrases: "build this", "implement", "write the code for", "create a function that", "add this endpoint", "make it work", "update this code to", "wire this together". Do NOT use for: pure architectural decisions before implementation starts (use architecture skill), root-cause debugging of existing broken code (use debugging skill).

Specialized rules for repairing Markdown lint errors in Gold Context files (MD025, MD060, MD024).

Monitors conversation complexity and manages session boundaries. Proactively secures state and memory before advising the user to split work across separate chat sessions, preventing context bloat.

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.

Use this skill when designing schemas, writing queries, planning migrations, or evaluating data model decisions. Activated when the user mentions creating or modifying database tables, writing SQL, data integrity issues, slow queries, indexing, data migrations, ORM behavior, or choosing a database technology. Signal phrases: "design the schema", "create the tables", "add a column", "migration", "database is slow", "query optimization", "indexing", "normalize / denormalize", "data model", "foreign key", "relationship between", "N+1 queries", "data integrity", "ORM", "access pattern". Also activate for any work involving data that crosses service boundaries or any data integrity concern. Do NOT proceed with schema design without first understanding the actual access patterns.

Use this skill when investigating errors, crashes, unexpected behavior, or system failures. Activated when the user reports a bug, shares a stack trace or error message, describes tests failing unexpectedly, notices a regression (a feature that used to work no longer does), or when production telemetry alerts have fired. Examples: "this is broken", "I'm getting an error", "the tests are failing", "this stopped working after my last change", "the system is down". Do NOT use for general implementation work (use coding skill) or architecture decisions (use architecture skill).

Use this skill when designing, writing, or troubleshooting Deriv Bot (DBot) XML strategies, Blockly configurations, or trading algorithms for the Deriv platform. Activated when the user mentions "Deriv bot", "DBot", "XML5 format", "Accumulator strategy", "trade_definition", or asks to build/fix a trading bot file. Do NOT use for standard web or backend development (use coding skill) or generic Python/JS trading algorithms outside the DBot ecosystem.

Use this skill when the work involves infrastructure provisioning, deployment pipelines, observability, monitoring, incident response, or operational reliability. Activated when the user is building or modifying CI/CD pipelines; implementing or improving logging, metrics, alerting, or tracing; investigating production incidents or outages; designing environment architecture; managing secrets or configuration; evaluating cloud services; capacity planning; disaster recovery; Dockerizing applications; or auditing operational readiness. Signal phrases: "deploy", "CI/CD", "infrastructure", "Terraform", "Docker", "Kubernetes", "monitoring", "observability", "alerting", "logging", "staging", "production", "secrets", "rollback", "disaster recovery", "incident", "outage", "on-call", "scaling", "health check", "canary", "blue-green", "environment drift". Do NOT use for application code logic (use coding skill) or pure architecture decisions (use architecture skill).

Use this skill when diagnosing or resolving performance problems, optimizing slow systems, or proactively preparing for load. Activated when the user mentions slow response times, high resource consumption, timeouts, memory leaks, or anticipates increased traffic. Signal phrases: "it's slow", "optimize this", "bottleneck", "memory leak", "high CPU", "query is slow", "Core Web Vitals", "lighthouse score", "cache this", "timeout", "throughput", "latency", "load testing", "can it handle X users", "scale this", "performance is degrading". Also activate for capacity planning and performance-aware code review. Do NOT optimize without profiling evidence.

Use this skill when evaluating whether a feature is worth building, scoping work against business goals, identifying assumptions behind a proposal, or connecting engineering decisions to measurable outcomes. Activated when the question of WHAT to build or WHY to build it is open. Signal phrases: "should we build this?", "is this worth building?", "what's the MVP?", "scope this", "what should we prioritize?", "what problem does this solve?", "business impact", "success metric", "jobs to be done", "outcome", "assumption", "experiment", "why are we building this?", "requirements are unclear", "nobody is using this". Also activate when a task lacks a defined success metric, when requirements contradict, or when scope has no stated boundary. Do NOT use as a substitute for implementation — it must fire BEFORE coding begins when the problem or value is unclear.

Use this skill when improving code structure without changing external behavior, reducing technical debt, deciding between refactor vs rewrite, or planning legacy system modernization. Activated when the user mentions cleaning up code, reducing complexity, making code maintainable, improving a module that keeps breaking, deleting dead code, or performing a strangler fig migration. Signal phrases: "refactor", "clean this up", "technical debt", "legacy code", "rewrite vs refactor", "too hard to change", "no one understands this module", "we keep breaking this", "make this maintainable", "dead code", "code smell", "this area slows us down", "modernize", "migrate". Also activate when repeated bugs originate from the same structural confusion. Do NOT mix refactoring (structure changes) with feature work or bug fixes in the same changeset — they must stay separate.

Use this skill when comparing tools, technologies, frameworks, or approaches, or when conducting technical feasibility analysis. Activated when the user asks "Should I use X or Y?", requests pros and cons, needs a build vs. buy evaluation, asks "What is the best way to..." where the answer depends on context, or needs research into industry norms, standards, or technical alternatives. Examples: "compare Redis and Memcached", "should we build this or use a SaaS?", "what are the tradeoffs of GraphQL vs REST for our case?", "research options for background job processing". Do NOT use for pure implementation work (use coding skill) or for architecture decisions already made (use architecture skill).

Use this skill when evaluating existing code for correctness, security, maintainability, or architectural alignment. Activated when the user asks for a code review, a pull request (PR) review, asks "Is this code good?", "What's wrong with this?", or needs an audit of a legacy codebase for technical debt or modernization. Also activated at the self-review phase (Phase 7: Critique) of any significant implementation. Examples: "review this PR", "audit this module", "what issues do you see in this code?", "check this before I merge". Do NOT use for implementation work (use coding skill). Always apply security lens during every review.

Use this skill when the work involves authentication, authorization, trust boundaries, sensitive data, input validation, or vulnerability assessment. Activated when designing or modifying AuthN/AuthZ flows; handling or storing PII, financial, or health data; processing user input or file uploads; integrating with third-party APIs; designing system boundaries; reviewing pull requests (implicitly always active); or when the user mentions security concerns, vulnerabilities, or asks for a security audit. Examples: "is this secure?", "audit this for vulnerabilities", "how should I handle auth?", "is this input validation sufficient?", "what are the security risks here?", mentions of XSS, CSRF, SQLi, IDOR. Security is ALWAYS active as a secondary lens during code review and architecture design — never skip it.

Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts, directing a scene, fixing generation errors, or building an AI short film, product ad, or music video.

Detect and remove hollow AI filler language, empty superlatives, and vague boosters that degrade Seedance 2.0 prompt quality. Use when a prompt feels generic, over-written, or 'AI-sounding', or when generation output looks bland and needs a quality pass.

Design sound layers, specify dialogue lip-sync, and troubleshoot audio failures for Seedance 2.0 video generation. Covers @Audio1 reference input, multi-character constraints, known failure modes (silent output, desync, audio rewrite bug), and the boundary between Seedance 2.0 video generation and the separate Jimeng Digital Human tool. Use when adding audio to a Seedance prompt, fixing lip-sync errors, building multi-character dialogue scenes, or diagnosing why uploaded audio is ignored or replaced.

Specify camera movement, shot framing, multi-shot sequences, and anti-drift locks for Seedance 2.0. Covers dolly, crane, orbit, push-in, one-take, and storyboard reference methods. Use when writing camera instructions, shooting a scene with a specific angle or movement, or fixing a wandering or locked camera.

Lock character identity, assign @Tag references, and maintain face and hand consistency across multi-character scenes in Seedance 2.0. Covers 360-degree consistency testing and first-frame art direction for image-to-video. Use when a character changes appearance between shots, when building multi-person scenes, or when hands or faces are distorting.

Check prompts against Seedance 2.0 content policy, apply safe IP substitutions, and navigate real-person and brand restrictions. Updated with live Feb 2026 enforcement data from Disney, Paramount, MPA, and SAG-AFTRA actions. Use before every generation that involves named characters, franchise IP, celebrity likenesses, brand logos, or streaming originals.

Browse 16+ battle-tested, production-ready Chinese prompt examples for Seedance 2.0 across 8 genres: drama, action, advertising, animation, product, one-take, VFX, and music sync. Use to learn advanced prompt structure, copy-paste working examples, or find inspiration for new scenes.

'Navigate the Seedance 2.0 content filter, diagnose false-positive rejections, and write prompts that pass. Use when a prompt is blocked, rejected, or produces generic/degraded output due to filter misjudgment. Covers filter intelligence, intent evaluation, and safe-prompting techniques.'

'A guided creative journey to craft a production-ready prompt under the hard 2000-character limit. Follow the "Director\\'s Journey" workflow: Vision → Narrative → Visuals → Technical → Final Compressed Brief.'

'Guide users through a multi-stage creative journey to craft cinematic stories and single clips for Seedance 2.0. Use when a user has a vague idea, needs a script, or wants to elevate a simple prompt into a professional production brief. Follow the "Director\\'s Journey" workflow: Vision → Narrative → Visuals → Technical → Final Brief.'

Specify lighting, atmosphere, and light transitions for Seedance 2.0 prompts using named light sources, core parameters, and atmosphere contracts. Use when the scene needs a specific mood, time of day, or lighting style, or when lighting is flat, inconsistent across shots, or clipping.

Control motion timing, beat density, action choreography, and sequential video extension chains for Seedance 2.0. Covers fight-scene physics, per-shot motion contracts, and multi-clip continuation techniques. Use when motion is too fast, too slow, or jittery, when choreographing action sequences, or when extending a video across multiple clips.

Integrate Seedance 2.0 with ComfyUI nodes and post-processing chains covering upscale, frame interpolation, color grade, composite, and metadata cleanup. Use when building automated video pipelines, connecting Seedance to external tools, or finishing and delivering a generated video clip.

Build, validate, and compress Seedance 2.0 prompts to a hard 2000-character limit using the Five-Layer Stack, @Tag delegation, and the new Compression Engine. Use when constructing or debugging any T2V, I2V, V2V, or R2V prompt for the short-form workflow.

'Construct a production-ready prompt for Seedance 2.0 using the Director\'s Formula. Use when a user has a clear vision and needs to translate it into a genre-aware, intent-driven prompt. Covers genre routing, I2V gate, 30-100 word target, physics language, and anti-slop check.'

Apply genre recipe templates to Seedance 2.0 — product ads, fight scenes, brand films, mood pieces, dialogue clips, one-take journeys, music videos, novel adaptations, architecture walkthroughs, and action transfers. Use when you need a ready-made prompt structure for a known genre or format.

Control visual style, render-engine tokens, animation registers, period aesthetics, CGI material contracts, and style transfer via reference for Seedance 2.0. Use when setting a specific look — cinematic, anime, 3D, vintage, photorealistic — or when style is inconsistent across a shot chain.

'Diagnose and fix failing or low-quality Seedance 2.0 prompts using a 5-step diagnostic tree. Use when a prompt is consistently failing, producing generic output, or being rejected. Covers blurry/jittery output, camera chaos, character drift, stiff action, and ambiguous results.'

Specify VFX physics contracts, energy effects, particle systems, destruction physics, and multi-layer VFX hierarchies for Seedance 2.0. Use when adding explosions, fire, water, lightning, magic effects, or any physically simulated element to a scene.

Look up 450+ Spanish cinematic, photography, and production terms — Castilian and Latin American — with English equivalents and prompt-ready phrases for Seedance 2.0 across 20 categories, including filter-safe vocabulary for action, weapons, and combat. Use when writing prompts in Spanish or translating production concepts into Spanish Seedance vocabulary.

Look up 450+ Japanese cinematic, photography, and production terms with English equivalents and prompt-ready phrases for Seedance 2.0 across 20 categories, including filter-safe vocabulary for action, weapons, and combat. Use when writing prompts in Japanese or translating production concepts into Japanese Seedance vocabulary.