creative-workflow

Coordinate creative development tasks across design, frontend, and backend.

8|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kensaurus/cursor-kenji --skill creative-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creative-workflow
Source: https://github.com/kensaurus/cursor-kenji/tree/main/skills/creative-workflow
Command: npx skills add https://github.com/kensaurus/cursor-kenji --skill creative-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end workflow to coordinate creative development from ideation through delivery, aligning design, frontend, and backend work to produce cohesive features.

Core Features & Use Cases

  • End-to-end feature planning and execution from discovery through polished delivery.
  • Promotes design-system consistency and production-ready implementation.
  • Use Case: When starting a new feature, building a complete component/page, or implementing a full-stack feature, apply this workflow to ensure coherence and quality.

Quick Start

Start a new feature by following this end-to-end creative workflow from discovery to production-ready delivery.

Frequently Asked Questions about creative-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage end-to-end feature builds from design to frontend development?

End-to-end feature builds require coordinating discovery, design direction, component architecture, implementation, and validation to ensure cohesive frontend development and production-ready delivery.

What is the best way to maintain design-system consistency when building full-stack implementations?

Maintaining design-system consistency during full-stack implementations requires enforcing structured architecture and workflow optimization across all components to produce cohesive, polished features.

How do I structure component architecture for production-ready frontend delivery?

Structure component architecture by following a workflow that enforces design direction, implementation steps, and validation, ensuring frontend development results in production-ready, polished delivery.

Does this creative workflow approach work for building complete pages and new components?

Yes, this creative workflow applies directly to building complete pages and new components, enforcing the discovery, architecture, and implementation steps needed for production-ready features.

When should I use a structured workflow for frontend development instead of ad-hoc implementation?

Use a structured workflow for frontend development when starting new features or full-stack implementations that require design-system consistency, component architecture coordination, and polished end-to-end delivery.