style-format

The style-format skill provides a structured framework for defining visual aesthetic templates using single markdown files. It is designed for creative developers and AI-assisted designers who need consistent artistic outputs from generative models. By creating specific style definitions in the project's styles directory, users can ensure reproducible results across different image generation prompts. This skill acts as a bridge between high-level creative concepts and technical rendering parameters, enabling teams to maintain a cohesive visual identity across various assets.

• Standardized markdown schema for describing visual style, mood, color palette, and technical rendering notes.

• Decouples artistic direction from functional prompts, allowing users to swap styles (e.g., glass, watercolor, or cyberpunk) while keeping the subject description constant.

• Supports explicit color palette definition using hex codes to guarantee brand consistency and saturation control.

• Provides clear distinction between stylistic descriptions and image-based references, enabling advanced workflows that combine text-driven style with existing visual assets.

• Includes built-in security validation to prevent shell injection, variable expansion, or command substitution within style files, ensuring safe prompt injection in automated pipelines.

• Store style templates in the project/styles/ directory; common files include glass.md, watercolor.md, or cyberpunk.md.

• Use the --style flag in generation commands to prepend the markdown content directly to the user's prompt for the AI model.

• Focus descriptions on specific visual characteristics like lighting, materials, camera angles, and rendering techniques to achieve higher-fidelity outputs.

• Combine with --ref flags for image-to-image workflows, using the .md file for artistic context and the image for spatial or compositional consistency.

• Keep files focused by adhering to a one-style-per-file pattern to simplify version control and retrieval.

• Note that style files are treated as text templates; avoid complex scripts or shell operators, as the system filters for potentially harmful injection patterns during file processing.