Use the Kent CLI to create, inspect, start, list, and comment on workflow tasks. Use when the user asks to manage tickets/tasks, or mentions Jira-like IDs such as KENT-42.
How to use the Kent CLI to author and edit Kent workflow graphs — nodes, edges, transitions, parameters, context modes, and project links. Use when the user asks to define, build, inspect, or modify Kent workflows.
Create or improve agent skills. Use when the user wants to add a new skill or update an existing skill.
Write, rewrite, review, or validate Kent product specifications under docs/dev/specs. Must use before any task that changes or evaluates those specifications.
How to use `kent` cli to change your behavior, environment, config, or debug issues. Read when the user asks you to use/manage a worktree, set a goal, change Kent config.toml/settings/behavior/hooks/subagents, or to debug project/workspace/worktree/workflow…
Find wide code mechanisms with narrow or unproven product value and turn one coherent candidate into a plain-language deletion decision. Proactively use for architecture audits, simplification, redundant IDs or state, retry/recovery machinery, protocol…
How to design TUI frontends. Use when requests involve TUI layout, spacing, colors, UX/UI and working on user-facing surfaces.
Kent GUI design guide for desktop/web UI work. Use when designing or implementing Kent GUI screens, layouts, visual tokens, animations, writing React or Compose UI code.