Skip to main content
SanchikaEvidence contracts
Primary navigation
Search Source

tools-local-artifact pattern

ToolCard

Describe one bounded tool by user job, input, output, review owner, and local boundary.

tools/local-artifact · candidate · @sanchika/patterns

Product job

Inspect a tool's input, draft output, review owner, and boundary before following its single destination.

Describe one bounded tool by user job, input, output, review owner, and local boundary.

Anatomy and required fields

category

Work category label.

title

Specific job-oriented tool name.

summary

Bounded user outcome.

input

Facts or artifacts the user provides.

output

Draft artifact produced.

review

Professional or source review requirement.

boundary

Local or workspace boundary.

status

Availability or limitation in text.

action

Open or inspect action.

Required fields
  • category
  • title
  • summary
  • input
  • output
  • review
  • boundary
  • status
  • action

Default and edge states

available

Tool can be opened.

  • input
  • output
  • review
limited

Tool has a known limitation.

  • limited
  • reason
  • alternative
unavailable

Tool cannot be used.

  • unavailable
  • reason
  • fallback

Composed synthetic exemplar

02
Drafting

Notice response outline

Organise source points into a response outline.

Input
User-entered facts and source references
Output
Editable response outline
Review
Professional review required
Open bounded tool mode

State coverage

Default and consequential edges remain inspectable.

availableTool can be opened.input · output
limitedTool has a known limitation.limited · reason
unavailableTool cannot be used.unavailable · reason

Trust, source, and consumer obligations

Trust boundaries
  • Search terms, entered facts, and draft outputs stay in the browser unless a named adopter action says otherwise.
  • Every tool names its input, output, review requirement, and local or external boundary before opening.
Consumer owns
  • Provide each tool specification, runtime, source mapping, draft generation, export, storage, and any external handoff.
Responsive behavior
  • Keep input, output, and review labels visible; do not reduce them to icons.
  • Move action after boundary metadata on narrow screens.
Forced colors and reduced motion
  • Retain text status, result boundaries, native focus, link underlines, and selected filters using system colors.
  • Keep directory results, empty state, draft status, and next action understandable without animated filtering or confirmation.

Compact API reference

Package
@sanchika/patterns
CSS
@sanchika/patterns/styles.css
Base class
sk-pattern-tool-card
Group
tools-local-artifact