Design polished terminal UX for CLIs and TUIs. Use for setup flows, dashboards, tables, and actionable errors. NOT for web UIs, desktop windows, API schemas, or shell automation.
日本語の概要は準備中です。原文の説明を表示しています。
939 件 ・ 関連度順
概要と使いどころ
Design polished terminal UX for CLIs and TUIs. Use for setup flows, dashboards, tables, and actionable errors. NOT for web UIs, desktop windows, API schemas, or shell automation.
日本語の概要は準備中です。原文の説明を表示しています。
Discipline an AI agent needs to work an issue/task tracker (Jira, Linear, GitHub Issues) as the shared source of truth: pull the right next item instead of inventing work, search before creating to avoid duplicates, write actionable items with checkable acceptance criteria, keep status transitions honest, and link work to items via branches/PRs/commits so progress is legible. Use when an agent picks up tracker work, files a new issue, updates status, or closes an item. NOT for authoring the PR itself (use agent-pr-authoring), roadmap-level planning and prioritization (use legible-roadmap-with-sidequests), or the mechanics of multiple agents coordinating on the same codebase (use multi-agent-coordination).
日本語の概要は準備中です。原文の説明を表示しています。
Introduce people to AI, agentic AI, and AI skills with appropriate pedagogy for any audience. Covers LLM analogies, progressive complexity paths, aha-moment demos, audience-tailored explanations, workshop design, and overcoming emotional barriers to AI adoption. Activate on 'explain AI', 'introduce AI', 'AI workshop', 'AI demo', 'teach AI', 'AI literacy', 'onboard to AI', 'AI evangelism', 'explain agentic', 'explain skills to', 'AI training session', 'AI onboarding'. NOT for teaching ML engineering (use ai-engineer), not for building AI features (use ai-engineer), not for prompt engineering (use prompt-engineer), not for building training data pipelines.
日本語の概要は準備中です。原文の説明を表示しています。