Skip to content
Skills Library
Programming · Conversion & formats

creator

/creator

Use when the person runs the creator command to turn a Figma frame, an HTML file or a URL into a WordPress page on the Roots stack - routes the source, runs the ingest, builds and checks the match plan, and stops for approval before anything is emitted. Resumes a run with --run=.creator/<run>. For one step on its own use html-ingest, figma-ingest, section-matching, block-scaffolding-from-design or visual-fidelity.

Repository
kivo-wise ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the person runs the creator command to turn a Figma frame, an HTML file or a URL into a WordPress page on the Roots stack - routes the source, runs the ingest, builds and checks the match plan, and stops for approval before anything is emitted. Resumes a run with --run=.creator/<run>. For one step on its own use html-ingest, figma-ingest, section-matching, block-scaffolding-from-design or visual-fidelity.

Original author description

Use when the person runs the creator command to turn a Figma frame, an HTML file or a URL into a WordPress page on the Roots stack - routes the source, runs the ingest, builds and checks the match plan, and stops for approval before anything is emitted. Resumes a run with --run=.creator/<run>. For one step on its own use html-ingest, figma-ingest, section-matching, block-scaffolding-from-design or visual-fidelity.

How it works

  1. When to use
  2. Inputs required
  3. Procedure
  4. Verification
  5. Failure modes
  6. Escalation
Original SKILL.md headings · 46 lines, 570 words
SKILL.md preview
---
name: creator
description: Use when the person runs the creator command to turn a Figma frame, an HTML file or a URL into a WordPress page on the Roots stack - routes the source, runs the ingest, builds and checks the match plan, and stops for approval before anything is emitted. Resumes a run with --run=.creator/<run>. For one step on its own use html-ingest, figma-ingest, section-matching, block-scaffolding-from-design or visual-fidelity.
disable-model-invocation: true
license: MIT
compatibility: Requires the kivo-wise plugin (stack detection, runner context). Node 20+; Playwright in the target project for HTML sources and verification; the official Figma MCP server for Figma sources.
---

# /creator

Arguments: `<figma.com URL | file.html | https URL>` or `--run=.creator/<run>` to resume.

## When to use

- The person typed the command with a source or a run folder.
- Never start it on your own; the individual skills cover single steps.

## Inputs required

1. A source (Figma frame URL with `node-id`, an `.html` file or an `http(s)` URL), or an existing run folder.
2. The target stack: `.roots-stack.json` at the project root. If it is missing, run kivo-wise `/roots-detect --write` first (or ask the person).
3. The kivo-creator plugin root (two levels above this skill's folder).

## Procedure

1. **Route the source.** `figma.com/design/...` or `figma.com/file/...` → `figma-ingest`. A path ending in `.html` or an `http(s)` URL → `html-ingest`. `--run=` → skip to step 3 with that folder. Anything else: ask. There is no fallback: if the Figma MCP server is missing, stop with the instructions from `figma-ingest`.
2. **Ingest** with the routed skill. It ends with valid specs in `.creator/<run>/specs/`.
3. **Match** with `section-matching` until `node <kivo-creator>/scripts/match.mjs --run=.creator/<run> --check --project=.` passes.
   - **Block type for new blocks.** New blocks follow the project's existing pattern: ACF Composer projects get ACF blocks, `block.json` projects get native blocks, whatever the profile. `match.mjs` prints `blockType` (also in `match-plan.json` and `match-plan.md`). `creator.blocks` in `.roots-stack.json` wins (`source: "override"`); otherwise the count of existing blocks decides when one type holds at least 80% (`source: "count"`).
   - When `blockType.type` is `null` and the plan scaffolds anything, ask the person **once**: for `reason: "mixed"` show `counts` and ask which type new blocks use; for `reason: "none"` recommend `blockType.recommended` (the profile default). Then offer to record the answer: `node <kivo-creator>/scripts/block-type.mjs --set=<acf|native> --project=.` writes `"creator": { "blocks": "<type>" }` into `.roots-stack.json` and keeps its other keys. If the person does not want it recorded, pass `--blocks=<type>` to `match.mjs --check` and later to `emit.mjs` (`source: "asked"`). Never pick the type yourself.
4. **Stop.** Show `.creator/<run>/match-plan.md`, the gaps and any question still open, and ask the person to approve the plan. Do not emit, scaffold or edit project files in this turn.
5. After the person approves (a later message): `block-scaffolding-from-design`, then `visual-fidelity` (at most three fix rounds). Finish with the fidelity report.

## Verification

- At the stop point the working tree of the project is unchanged apart from `.creator/` (`git status`).
- `match.mjs --check` passes on the plan you show.

## Failure modes

| Symptom | Cause | Fix |
|---|---|---|
| No profile found | No `.roots-stack.json` and no detector output | Run kivo-wise `/roots-detect --write`, then resume with `--run=` |
| Figma tools unavailable | The Figma MCP server is not connected in this session | Stop; follow the connection steps in `figma-ingest` |
| Plan check fails | Open or invalid decisions | Finish `section-matching` before stopping |
| `New blocks need a block type` | Mixed project (neither type reaches 80%) or no blocks yet, and no `creator.blocks` | Ask the person once; record with `block-type.mjs --set=` or pass `--blocks=` |
| `creator.blocks must be "acf" or "native"` | Invalid value in `.roots-stack.json` | Fix the value (or remove the key to go back to counting) |
| Files appear in the project before approval | Emit started too early | Revert them; emitting waits for approval |

## Escalation

Every run stops at the match plan for the person's approval. Ask again before emitting if the plan changed after it was approved.

Versions

RepositoryScoreLicence
This page · hekivo/kivo-wise100MIT
marswaveai/skills100MIT
thematteroftime/agentic-md-for-dummies100MIT

Database snapshot: 13.11.2026 · package version 5258df9bbdf5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100html-ingest
    Use when an HTML file, a URL or a published page has to become kivo-creator section specs - rendering it at 390 and 1440 px with the project's own Playwright, splitting it into sections, recording text slots, links, media, computed styles and one reference screenshot per section…
  • 100section-matching
    Use when kivo-creator section specs in .creator/<run>/specs must be mapped to the project's existing blocks before anything is generated - building the match plan, applying the compatibility filter, judging the remaining candidates with the written rubric (including an explicit…
  • 100design-to-wp-block
    Create WordPress block patterns from Figma designs or screenshots using the design-specialist agent. Auto-activates when user provides a Figma URL or design mockup and asks to create a WordPress block pattern, component, or section. Invoke when user says "create a WordPress…
  • 100dx-figma-all
    Full Figma design-to-code flow in one command — extract, prototype, verify. Use when a story has a Figma URL: 'figma all', 'turn this figma into code'.
  • 90figma-to-page
    Implement a frontend page or component from a Figma URL or node using Figma MCP and Playwright QA. Use when exact visual, copy, and structural fidelity to Figma is the top priority.
  • 100figma-implement-design
    Translate Figma designs into production-ready application code with 1:1 visual fidelity. Use for Figma URLs, node IDs, implementation requests, or components that must match Figma specs; use the local `figma` skill for general Figma MCP context and setup.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.