kick-init

Create a Design Context document from codebase exploration and gap questions.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Conradmaker/copilot-cockpit --skill kick-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kick-init
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/kick-init
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill kick-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams bootstrap a shared design context by auditing the codebase, aligning with project goals, and documenting design decisions before design work begins.

Core Features & Use Cases

  • Step-driven exploration and targeted questions to fill gaps.
  • Persists a Design Context document referenced by all ds-/fe- skills.
  • Use Case: Onboarding to a new project or starting design work with no Design Context yet.

Quick Start

Run kick-init in a project to bootstrap the Design Context document and align design expectations before design work begins.

Frequently Asked Questions about kick-init

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

FAQPage Schema
How do I bootstrap design context when onboarding to a new project?

To bootstrap design context for project onboarding, run this skill in a project to audit the codebase, align with project goals, and consolidate design direction into a Design Context document before design work begins.

What is a Design Context document and when do I need one?

A Design Context document consolidates a project's design direction, user context, brand personality, and aesthetic criteria. You need one when starting design work on a new project or onboarding to unfamiliar codebases where no design context exists yet.

How to align teams on design direction before starting design work?

Align teams on design direction by running a step-driven exploration that audits the codebase and uses targeted gap questions to fill missing context, persisting the consolidated design expectations as a shared Design Context artifact.

Does kick-init work with existing codebases to extract brand personality and aesthetic criteria?

Yes, it works with existing codebases by exploring the project structure and using gap-analysis questions to identify and consolidate brand personality and aesthetic criteria into a reusable Design Context document.

Can I reuse the Design Context document across other design and frontend skills?

Yes, the Design Context document is persisted and explicitly designed to be referenced by all ds-*/fe-* skills, ensuring that downstream design and frontend workflows reuse the same aligned project context.