OpenDesigner: painted art and films
openbooklet.com/s/opendesigner-painted-art-and-filmsopenbooklet.com/s/[email protected]GET /api/v1/skills/opendesigner-painted-art-and-filmsUse this when someone wants original art made by code rather than found art. Typical asks: a painted hero, a launch film or reel, an animated brand moment, a celebration loop, a painted link-preview image, or "something that looks hand-made, in our colours". It is also an answer for three designer h
Design systems and the pages built on them, one decision at a time. Use for a landing page, an app or a redesign ("make it look professional"), a style direction, a taste poll, tokens or DESIGN.md.
Changes or extends an existing OpenDesigner design system safely. Reads DESIGN.md, tokens, decisions and locks first, asks only about what is new, validates after. Use when opendesigner/ exists.
Maps a reference (site, screenshot, Figma, CSS, brand book) to OpenDesigner dials, or writes its Taste Index. Copies structure and quality, never another brand's identity.
Finds open-licence illustrations and stock photos, recolors art to the tokens and wires it in. Also adds icons drawn like the few a product already has, from open sets, with their licences.
Checks anything visual before export or sharing (a video, page, deck or UI) for the silly mistakes that make it look cheap or wrong. Use before any render, export or publish.
Use this when a screen, page or app has been built and someone asks "does it look right?", "review this", "QA this" or "check my UI". Use it too, on your own work, before you say it is done. It works on what you built and on what anyone else built. With an OpenDesigner system in the project it check
Auto-indexed from ckryptickunal/OpenDesigner
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.