taste

Evaluates code, architecture, product, design, and communication quality through a calibrated five-dimension rubric.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill taste-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taste
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/taste
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill taste-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineers often need to know whether code, architecture, or design is genuinely good — not just whether it works. This Skill provides calibrated qualitative judgment across five dimensions, replacing vague gut feelings with articulated, defensible reasoning about craftsmanship. ## Core Features & Use Cases - Quick Judgment: Delivers a prose verdict plus the single highest-leverage fix for single files, snippets, or simple "is this good" questions. - Deep Review: Performs dimension-by-dimension analysis with optional 1-5 scores for large codebases, architecture documents, or PRDs, with an optional reviewer agent for targets spanning five or more files. - Guide & Compare: Applies taste principles during code generation and refactoring with codebase pattern adaptation, and compares approaches while labeling taste judgments versus objective tradeoffs. - Use Case: Paste a newly written module and ask whether it is well-designed; receive a verdict on naming, cognitive load, error handling, and consistency, plus the one change that would most improve it. ## Quick Start Ask the assistant to review the taste of a specific file or code snippet and tell you whether it is well-designed.

Frequently Asked Questions about taste

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

FAQPage Schema
How do I get a quality review of my code beyond bug checking?

Ask for a taste review of the file or snippet. The skill returns a prose verdict explaining what is good and what is off, plus the single highest-leverage fix, without forcing scores or templates.

What dimensions does a taste-based code review cover?

Five dimensions: Code (consistency over cleverness), Architecture (resilience over elegance), Product (composability over completeness), Design (intentionality over decoration), and Communication (teaching over describing). Each has a dedicated reference file with principles and examples.

When should I use deep review versus quick judgment?

Quick judgment is the default for single files and simple questions. Deep review applies when the target spans three or more files, is an architecture document or PRD, or when you explicitly request a detailed review.

When should I not use a taste evaluation skill?

Do not use it for specific bug fixes, performance optimization, security audits, writing tests, or functional requests with concrete goals like fixing mobile spacing. It activates only for holistic quality judgment questions.

Does the taste review work with my existing codebase conventions?

Yes. In generation mode it extracts naming, structure, and framework patterns from up to three sibling files and aligns output with them. Existing patterns take priority over reference principles unless they are actively harmful.

How are the 1-5 taste scores calibrated?

Scores range from 1 (harmful) to 5 (masterful) and are assigned only with direct evidence in the provided artifacts. Thin evidence restricts scores to 2-4 with uncertainty marked, and dimensions without evidence are skipped rather than guessed.