Pawrrtal Taste

Purpose

Use this skill to make Pawrrtal feel cleaner, simpler, and more deliberate. It applies to the web UI, Telegram rendering, CLI human output, agent tool labels, flow definitions, and any code that turns backend state into something a user reads.

Taste Rules

• Prefer calm density over dumps. Show the useful slice first, then counts and ways to drill in.
• Keep labels specific and title-cased: List Folder: backend/app, Read File: README.md, Search Code: Telegram media.
• Avoid vague labels like List folder, raw tool names, raw schema keys, or long argument blobs in user-facing output.
• Put the object after the action. List Folder: src is clearer than Folder list or list_directory.
• Do not show a long folder/file list unless the user asked for exhaustiveness. Group by kind, cap visible rows, and say how many are hidden.
• Show thinking in Pawrrtal. Do not suppress it; make it readable, compact, and visually distinct from final answers and tool output.
• Prefer native Pawrrtal words over provider or SDK words. Users should see Pawrrtal concepts first, internals only when useful.
• Human CLI output should be compact and aligned; JSON should carry the full evidence.
• Avoid ornamental UI and one-note palettes. Use the repo design tokens and the quiet Craft Agents tone already encoded in DESIGN.md.

Tool Output Shape