taste

Ground domain knowledge before drafting to align outputs with practitioner norms.

2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Hmbown/taste --skill taste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taste
Source: https://github.com/Hmbown/taste/tree/main
Command: npx skills add https://github.com/Hmbown/taste --skill taste

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Taste provides domain-grounded judgment during creation to ensure outputs reflect expert understanding of the target domain, avoiding artifacts that feel generated or shallow.

Core Features & Use Cases

  • Ground the quality bar at the start of any creation task by establishing a domain model and constraints.
  • Frame the work to identify the spine, target audience, and finish level before drafting code, visuals, or docs.
  • Create with the filter on: apply the domain model to inclusion, structure, and detail, then subtract extraneous elements and verify alignment with the spine.

Quick Start

Establish the domain grounding, define the spine, and generate a grounded first draft that matches practitioner norms.

Frequently Asked Questions about taste

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

FAQPage Schema
How do I prevent generated code and documentation from feeling shallow or ungrounded?

Domain-grounded judgment prevents shallow outputs by establishing a domain model and applying a grounding workflow—ground, frame, create, subtract, verify spine, calibrate finish—to align deliverables with practitioner norms and a defined quality bar.

What is the best way to establish a quality bar before drafting visual or data artifacts?

Frame the work before drafting by identifying the spine, target audience, and finish level, which grounds the creation process and ensures visual or data artifacts match domain-specific practitioner standards.

How do I apply domain constraints to filter content during the creation process?

Apply domain constraints by using a grounding workflow: create with the domain model active, subtract extraneous elements that fail the filter, and verify the remaining structure aligns with the defined spine.

Does this grounding workflow support both code generation and technical documentation?

Yes, the grounding workflow supports both code generation and technical documentation, applying domain judgment to inclusion, structure, and detail across deliverables where quality hinges on practitioner norms.

When should I use a domain grounding workflow for content creation?

Use a domain grounding workflow for content creation when outputs risk feeling generated, specifically across domains like code, visuals, documents, and data artifacts where expert practitioner norms dictate quality.