AGENT SKILL

principle-experience-first

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

License 许可
Apache-2.0
所属仓库
caudra/caudra
最近更新
2026-11-04
Stars
★ 11
Forks
1

01 前言 Front Matter

name
principle-experience-first
description
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
disable-model-invocation
true

03 SKILL.md 正文

Experience First

When implementation convenience conflicts with user delight, choose delight.

  • Every feature, control, and option must be justified
  • Ship less, ship better (polished experience with three features beats rough one with ten)
  • Prototype before committing (design decisions are cheaper in throwaway HTML than production code)
  • Get the details right (transitions, alignment, spacing, feedback, error states)
  • Tighten the core loop (every feature should serve the central workflow or get out of the way)

The user is whoever consumes the work. For a UI that is the end user. For a library or an internal API it is the colleague who imports it. The engineer who maintains the code next is a user too. Weigh their experience the same way, and explain impact from their perspective.

Foundations should serve the experience. Foundational thinking governs the sequence of work. This principle governs the target.

04 同仓库更多 Skills

caudra
caudra/caudra

caudra-workflow-dev

Write, validate, run, and debug Caudra workflows. A workflow is a durable Rhai script that fans work out to subagents in phases, checks what comes back, and keeps a journal so it can resume. Load this before writing a workflow file, before calling the workflow tool, or when a repeatable multi-agent plan would serve the user better than doing the steps by hand.

★ 11
caudra
caudra/caudra

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 11
caudra
caudra/caudra

unslop

Cut AI tells from any writing.

★ 11
caudra
caudra/caudra

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 11
caudra
caudra/caudra

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 11
caudra
caudra/caudra

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 11