superdesigndev/superdesign-skill / skills/superdesign
superdesign
VerifiedDesign or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models. Use whenever the user wants to design a page, feature, flow, slide deck, or brand-new product; improve or reproduce existing UI; compare design results across top models; explore visual variants; set or extract a design system; build reusable components or multi-page flows; create presentations; or create posters and marketing graphics, even if they never say the word 'design tool'. Also supports generating supporting image or video assets when a design needs them.
| File | Kind | Size |
|---|---|---|
| INIT.md | markdown | 438 B |
| SKILL.md | skill md | 16.1 KB |
| SUPERDESIGN.md | markdown | 459 B |
| agents/openai.yaml | config | 192 B |
| references/ASSET_GENERATION.md | markdown | 6.2 KB |
| references/COMPONENTS.md | markdown | 4.6 KB |
| references/GRAPHIC.md | markdown | 16.1 KB |
| references/INIT.md | markdown | 8.2 KB |
| references/PRESENTATION.md | markdown | 13.0 KB |
| references/RESUME.md | markdown | 21.0 KB |
| references/SUPERDESIGN.md | markdown | 47.3 KB |
| references/WEBSITE.md | markdown | 4.5 KB |
| references/design-with-your-model.md | markdown | 3.1 KB |
references/COMPONENTS.md
View on GitHub# Component Extraction Reference (create-component / update-component)
Read this right before converting a codebase component into a reusable Superdesign DraftComponent — i.e. Step 2.5's conversion step in [SUPERDESIGN.md](SUPERDESIGN.md), or any `create-component`/`update-component` call. Run `create-component --help` / `update-component --help` for their flag sets.
## BRAND LOGO INVARIANT
Treat a real project logo as required content whenever the source component or requested design contains a logo position.
1. Before converting the component, resolve the appropriate logo selected by the source UI or user from the project's Brand Assets. On a cold flow, upload the selected local logo first with `--purpose brand --type logo`, a stable repo-relative `--key`, and a usage description. Keep both the returned `assetKey` and public `url`. On a warm flow, reuse the saved logo key; if its public URL is not already available in the working context, repeat the same stable-key upload so deduplication returns the canonical URL.
2. Hardcode that exact public `https://` URL in an `<img>` inside every logo-bearing template. Preserve the source alt text, dimensions, and layout treatment.
3. Never replace an available logo with initials, product-name text alone, an emoji, a generic icon, an invented SVG, or another placeholder. Text may accompany the logo only when the source UI does so.
4. Before `create-component` or `update-component`, inspect the finished HTML. If the source needs a logo and the template does not contain the resolved logo URL, stop and repair the template first.
5. If a logo becomes available after a reusable component was created, update every affected component before the next generation.
Allow a no-logo fallback only when the project has no appropriate logo Brand Asset and no deliberately selected local logo. Do not fabricate a brand mark; preserve a text-only identity when appropriate.
## PETITE-VUE TEMPLATE SPEC
When converting React components to Petite-Vue HTML templates for `create-component`:
### What to HARDCODE in the template (NOT props):
- Icon names and SVG markup
- Text labels, menu item names
- Image sources and alt text
- CSS classes and all styling
- Structural HTML and layout
- Color values, font sizes, spacing
### What to EXTRACT as props (ONLY these categories):
- **Active state**: `activeItem`, `isActive`, `currentTab` — indicates which page/section is selected
- **Navigation URLs**: `homeHref`, `searchHref`, `profileHref` — link destinations
- **Conditional visibility**: `showNotification`, `showBadge`, `isExpanded` — toggle elements
- **Dynamic counts**: `badgeCount`, `notificationCount` — numeric values that change
### Allowed Petite-Vue syntax:
- `{{ propName }}` — text interpolation
- `:href="propName"` — attribute binding
- `v-if="propName"` / `v-show="propName"` — conditional rendering
- `:class="{ 'active': activeItem === 'home' }"` — dynamic class binding
- `@click="$emit('name', payload)"` — event emission
### NOT allowed:
- `v-for` for navigation items (hardcode each item instead)
- `v-model` (no two-way binding)
- `v-html` (no raw HTML injection)
- Complex JavaScript expressions in templates
### Every prop MUST have a non-empty `defaultValue`.
### Output requirements:
- Valid HTML with Tailwind CSS classes
- Replace all CSS modules / styled-components with Tailwind utilities or inline styles
- Use Lucide icon CDN or inline SVGs for icons
- Include reasonable `previewWidth` and `previewHeight` estimates in the component description
### Example conversion:
**React source:**
```tsx
function NavBar({ activeItem = "home" }) {
return (
<nav className="flex items-center gap-4 px-6 py-3 bg-white border-b">
<Logo />
<Link
to="/"
className={cn("text-sm", activeItem === "home" && "font-bold")}
>
Home
</Link>
<Link
to="/explore"
className={cn("text-sm", activeItem === "explore" && "font-bold")}
>
Explore
</Link>
</nav>
);
}
```
**Petite-Vue template:**
```html
<nav class="flex items-center gap-4 px-6 py-3 bg-white border-b">
<img
src="https://cdn.example.com/brand/logo.svg"
alt="Project logo"
class="h-6 w-6"
/>
<a
:href="homeHref"
:class="{ 'font-bold': activeItem === 'home' }"
class="text-sm"
>Home</a
>
<a
:href="exploreHref"
:class="{ 'font-bold': activeItem === 'explore' }"
class="text-sm"
>Explore</a
>
</nav>
```
**Props:**
```json
[
{ "name": "activeItem", "type": "string", "defaultValue": "home" },
{ "name": "homeHref", "type": "string", "defaultValue": "#" },
{ "name": "exploreHref", "type": "string", "defaultValue": "#" }
]
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |