{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "kostja94-bricks--design-agent-task-input-states",
 "repo": "kostja94/bricks",
 "repo_url": "https://github.com/kostja94/bricks",
 "repo_slug": "kostja94-bricks",
 "title": "Design an agent task input with full states",
 "page_title": "How to design an agent task input with full states with Bricks",
 "summary": "Get a Task Input component that covers loading, cancellation, invalid input, and recovery.",
 "who": "A product engineer adding an AI task box to an internal tool who needs the component to handle failures, not only the happy path.",
 "problem": "Agent-generated task inputs often omit loading, cancellation, invalid input, or result recovery.",
 "outcome": "A Task Input component with the expected interaction states, built from the project's own primitives and checked inside its real page.",
 "steps": [
  "Install the skill with `npx skills add kostja94/bricks --skill component-builder`.",
  "Describe the task surface and where the input sits in the existing page or workspace.",
  "Have the agent load the Task Input reference and list the states it will implement before coding.",
  "Review the states for loading, cancellation, invalid input, and result recovery, then ask for the verified build."
 ],
 "agent_prompt": "Use the component-builder skill from kostja94/bricks to build a Task Input for <target project>. Cover loading, cancellation, invalid input, and result recovery, reusing the project's existing primitives. Verify the component inside its real page and report which states were tested.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README gives Task Input as an example of a component that needs these states, but it does not provide a ready-made agent backend, so you still wire the behavior to your own tools.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "javascript",
 "requirements": [
  "A project codebase with routes, components, design tokens, and a frontend framework the agent can read",
  "A coding agent that can run shell commands such as npx in the project",
  "Node.js and npm, needed for npx and for npm test in the Bricks repo"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/kostja94-bricks/design-agent-task-input-states/",
 "md": "https://dedupedai.com/use-cases/kostja94-bricks/design-agent-task-input-states/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/kostja94-bricks--design-agent-task-input-states.json",
 "api_version": "v1"
}