kintsukuro1
- 30 skills
- 0 followers
- last month last updated
- ▌ Artisan 2 · kintsukuro1Write production-quality frontend components (React, Vue, Svelte) with TypeScript, accessibility, and clean architecture.
- ▌ Builder 2 · kintsukuro1Builds production-ready, type-safe backend logic, APIs, and data models with strong validation and reliability practices. Use when implementing business logic or integrating external services.
- ▌ Palette 2 · kintsukuro1UX-focused coding assistant for usability, interaction quality, cognitive load reduction, and accessibility (WCAG 2.2).
- ▌ Thinking 2 · kintsukuro1Enforces careful, minimal, and goal-driven coding practices. Use when writing, editing, or reviewing code to avoid overengineering, unclear assumptions, and unnecessary changes.
- ▌ Frontend Desing 2 · kintsukuro1Create distinctive, production-grade frontend interfaces with strong visual identity. Use when building or improving web UIs to avoid generic design and produce polished, memorable results.
- ▌ Flow 2 · kintsukuro1Implement UI animations (hover, transitions, loading, gestures) with performance and accessibility in mind.
- ▌ Muse 2 · kintsukuro1Define and apply design tokens for color, spacing, and typography. Use for design system consistency and removing hardcoded styles.
- ▌ Nexus 2 · kintsukuro1Orchestrates multiple skills to solve complex tasks using structured thinking and minimal effective workflows.
- ▌ Radar 2 · kintsukuro1Adds high-value tests, fixes flaky tests, and improves coverage with minimal and reliable changes. Use when tests are missing, unstable, or insufficient.
- ▌ Scout 2 · kintsukuro1Investigates bugs, performs root cause analysis (RCA), builds reproduction steps, and assesses impact without writing fixes.
- ▌ Sigil 2 · kintsukuro1Generates project-specific coding skills based on repository structure, tech stack, and conventions. Use when creating reusable prompts, workflows, or coding patterns tailored to a project.
- ▌ Darwin 2 · kintsukuro1Detects project health, agent relevance, and evolution opportunities. Use when evaluating system quality, identifying inefficiencies, or deciding what to improve, remove, or simplify.
- ▌ Ripple 2 · kintsukuro1Enforces structured pre-change impact analysis. Use before modifying code to evaluate dependency risk, blast radius, and consistency issues. Does not write code.
- ▌ Sherpa 2 · kintsukuro1Breaks complex tasks into small, executable steps (5–15 min each), guides progress, and prevents scope creep or drift.
- ▌ Vision 2 · kintsukuro1Define UI/UX direction, redesign strategy, and design system decisions. Use for design planning, not implementation.
- ▌ Flow · kintsukuro1Implement UI animations (hover, transitions, loading, gestures) with performance and accessibility in mind.
- ▌ Muse · kintsukuro1Define and apply design tokens for color, spacing, and typography. Use for design system consistency and removing hardcoded styles.
- ▌ Nexus · kintsukuro1Orchestrates multiple skills to solve complex tasks using structured thinking and minimal effective workflows.
- ▌ Radar · kintsukuro1Adds high-value tests, fixes flaky tests, and improves coverage with minimal and reliable changes. Use when tests are missing, unstable, or insufficient.
- ▌ Scout · kintsukuro1Investigates bugs, performs root cause analysis (RCA), builds reproduction steps, and assesses impact without writing fixes.
- ▌ Sigil · kintsukuro1Generates project-specific coding skills based on repository structure, tech stack, and conventions. Use when creating reusable prompts, workflows, or coding patterns tailored to a project.
- ▌ Darwin · kintsukuro1Detects project health, agent relevance, and evolution opportunities. Use when evaluating system quality, identifying inefficiencies, or deciding what to improve, remove, or simplify.
- ▌ Ripple · kintsukuro1Enforces structured pre-change impact analysis. Use before modifying code to evaluate dependency risk, blast radius, and consistency issues. Does not write code.
- ▌ Sherpa · kintsukuro1Breaks complex tasks into small, executable steps (5–15 min each), guides progress, and prevents scope creep or drift.
- ▌ Vision · kintsukuro1Define UI/UX direction, redesign strategy, and design system decisions. Use for design planning, not implementation.
- ▌ Artisan · kintsukuro1Write production-quality frontend components (React, Vue, Svelte) with TypeScript, accessibility, and clean architecture.
- ▌ Builder · kintsukuro1Builds production-ready, type-safe backend logic, APIs, and data models with strong validation and reliability practices. Use when implementing business logic or integrating external services.
- ▌ Palette · kintsukuro1UX-focused coding assistant for usability, interaction quality, cognitive load reduction, and accessibility (WCAG 2.2).
- ▌ Thinking · kintsukuro1Enforces careful, minimal, and goal-driven coding practices. Use when writing, editing, or reviewing code to avoid overengineering, unclear assumptions, and unnecessary changes.
- ▌ Frontend Desing · kintsukuro1Create distinctive, production-grade frontend interfaces with strong visual identity. Use when building or improving web UIs to avoid generic design and produce polished, memorable results.