Define four foundational Kai practice skills #780

New issue

Open

opened 2026-07-29 04:01:24 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-29 04:01:24 +00:00

Member

Goal

Define a small set of foundational skills that encode Kai's durable practice across platform engineering and product design. These are lenses for technical and design work—not a flat catalog of narrowly procedural commands.

They should become root-level capabilities in the capability-tech-tree exploration (#779).

Foundational skills

1. Platform & developer experience

Shape paved paths, internal tools, CLI/API ergonomics, templates, documentation, and self-service workflows that reduce friction between intent and shipping.

2. Agentic systems & observability

Design agents as real consumers of context and observability: MCP/resource design, tool/action contracts, governed execution, agent ergonomics, and inspectable automation.

3. Governed, reliable production systems

Treat cloud/Kubernetes/IaC/observability plus security, compliance, policy, cost, and recovery as integrated experience constraints rather than separate after-the-fact concerns.

4. Ecosystem stewardship

Apply open-source maintenance, community-building, contribution pathways, and the social sustainability of technical systems as first-class product/technical considerations.

Common shape

Each skill should state:

The point of view and recurring tensions it brings to a decision
When to use it and when not to
Inputs/context it should inspect
Recommended experience or technical artifacts it produces
Cross-surface implications for human UI, CLI, API, MCP, and automation
Anti-patterns and deliberate constraints
Evidence/decision records it should leave behind

Boundary

Keep career-specific role filters, compensation, location, interview preferences, and personal circumstances in a separate private Kai career profile, invoked only for career-related work. The foundational practice skills should be broadly usable without revealing or importing those details.

Initial validation

Test the skills against:

A conversational prompt-to-visual workspace.
The public coilysiren.me/mcp design.
A representative site/app/API page or flow.

Refine the split or overlap only after those examples reveal what is genuinely reusable.

## Goal Define a small set of foundational skills that encode Kai's durable practice across platform engineering and product design. These are lenses for technical and design work—not a flat catalog of narrowly procedural commands. They should become root-level capabilities in the capability-tech-tree exploration (#779). ## Foundational skills ### 1. Platform & developer experience Shape paved paths, internal tools, CLI/API ergonomics, templates, documentation, and self-service workflows that reduce friction between intent and shipping. ### 2. Agentic systems & observability Design agents as real consumers of context and observability: MCP/resource design, tool/action contracts, governed execution, agent ergonomics, and inspectable automation. ### 3. Governed, reliable production systems Treat cloud/Kubernetes/IaC/observability plus security, compliance, policy, cost, and recovery as integrated experience constraints rather than separate after-the-fact concerns. ### 4. Ecosystem stewardship Apply open-source maintenance, community-building, contribution pathways, and the social sustainability of technical systems as first-class product/technical considerations. ## Common shape Each skill should state: - The point of view and recurring tensions it brings to a decision - When to use it and when not to - Inputs/context it should inspect - Recommended experience or technical artifacts it produces - Cross-surface implications for human UI, CLI, API, MCP, and automation - Anti-patterns and deliberate constraints - Evidence/decision records it should leave behind ## Boundary Keep career-specific role filters, compensation, location, interview preferences, and personal circumstances in a separate private `Kai career profile`, invoked only for career-related work. The foundational practice skills should be broadly usable without revealing or importing those details. ## Initial validation Test the skills against: 1. A conversational prompt-to-visual workspace. 2. The public `coilysiren.me/mcp` design. 3. A representative site/app/API page or flow. Refine the split or overlap only after those examples reveal what is genuinely reusable.

coilyco-ops added the

priority

label

2026-07-29 06:21:05 +00:00

coilyco-ops added the

autonomy

live-collab

label

2026-07-31 09:55:04 +00:00

coilyco-ops added

priority

autonomy