sergekostenchuk/ui-ux-agent-skill-system

concept-prototyper

Turn semantic core, business constraints, and user feedback into a site concept and throwaway wireframe prototype before visual design.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill concept-prototyper

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Concept Prototyper

This skill creates the concept bridge between SEO/semantic structure and UI design. Its prototype is a feedback artifact, not production code.

Operating Modes

  • concept: create docs/site-concept.md from semantic core and business logic.
  • wireframe: create a throwaway HTML/wireframe prototype for feedback.
  • feedback: structure user feedback into reports/business-concept-feedback.json.
  • conflict: produce reports/concept-conflicts.md and route unresolved conflicts to council.

Required Workflow

  1. Read references/concept-prototype-contract.md.
  2. Load semantic core, project brief, known business facts, and existing content if available.
  3. Build a content hierarchy: primary journey, page map, required facts, trust signals, CTA logic.
  4. If prototyping, create a clearly non-production wireframe artifact with sections marked by source reason.
  5. Collect or structure feedback and merge it with semantic constraints.
  6. If conflicts remain, route to senior-ui-ux-orchestrator council mode before design exploration.
  7. If conflicts are clear, hand off to tech-stack-selector, then design exploration.

Non-Negotiable

The prototype is disposable. Do not use it as the production implementation base unless the user separately approves a rebuild/refactor plan.

Handoff Shape

text
Concept path:
Prototype path:
Feedback path:
Conflicts path:
Decision: clear | council-required
Next skills:

Validation

bash
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/concept-prototyper
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/concept-prototyper

Related by task

from this repository

More skills

All skills
sergekostenchuk
Community

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

figma-canvas-editor

Create and edit native Figma canvas objects with MCP when explicitly scoped. Use this skill when the user asks to add or change frames, sections, components, instances, auto layout, variables, styles, FigJam objects, connectors, Slides objects, or selected nodes in Figma, and when the task requires mutation evidence, rollback-aware scope, and design-system consistency.

installs
1
GitHub stars
32
Updated
Sep 13