ux-workflow-patterns

A collection of user-experience rules based on problems found and fixed during a product sprint. It includes lessons about browser security, file selection, and matching frontend workflows with backend expectations.

In plain words
What is it for?
Use it when designing or reviewing image-upload and local-file workflows, especially when a browser interface needs to work with server-side file processing.
Why use it?
It helps prevent confusing workflows that fail because the browser, user interface, and server handle files differently.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/rm2thaddeus/pixel_detective/ux-workflow-patterns
Clone the repo
git clone --depth 1 https://github.com/rm2thaddeus/Pixel_Detective

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 4,616 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.04616
Opus 5 $0.00000 $0.02308
Sonnet 5 $0.00000 $0.00923
Haiku 4.5 $0.00000 $0.00462

Measured 2d ago against content hash 9ca576383514, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ux-workflow-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

frontend/.cursor/rules/ux-workflow-patterns.mdc · 678 lines

How it starts

The opening of the file, as written. The whole thing — 678 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UX Workflow Patterns

🎯 USER EXPERIENCE PATTERNS (From Sprint 10 UX Lessons)

Based on critical UX discoveries, user feedback, and workflow improvements implemented during Sprint 10.

🚨 CRITICAL UX FLAW DISCOVERED & FIXED

The "Add Images" Workflow Disaster
// ❌ CRITICAL UX FLAW: Browser security violation
function AddImagesModal() {
  const [directoryPath, setDirectoryPath] = useState('')
  
  return (
    <Modal>
      <ModalBody>
        <Text>Enter the directory path containing your images:</Text>
        <Input 
          placeholder="C:\Users\username\Pictures\..." 
          value={directoryPath}
          onChange={(e) => setDirectoryPath(e.target.value)}
        />
        <Button onClick={() => processDirectory(directoryPath)}>
          Process Directory
        </Button>
      </ModalBody>
    </Modal>
  )
}

Why this was a disaster:

  • Security Violation: Browsers cannot access local file system paths
  • 100% Failure Rate: This workflow would fail for every user
  • Confusing UX: Users don't understand why it doesn't work
  • Backend Mismatch: Backend expects server paths, not client paths
✅ SOLUTION: Proper File Upload Workflow
// ✅ CORRECT: Browser-compatible file upload
function AddImagesModal() {
  const [selectedFiles, setSelectedFiles] = useState<FileList | null>(null)
  const fileInputRef = useRef<HTMLInputElement>(null)
  
  const handleFolderSelect = (event: React.ChangeEvent<HTMLInputElement>) => {
    if (event.target.files) {
      setSelectedFiles(event.target.files)
    }
  }
  
  const handleUpload = async () => {
    if (!selectedFiles) return
    
    const formData = new FormData()
    Array.from(selectedFiles).forEach(file => {
      formData.append('files', file)
    })
    
    const response = await api.post('/api/v1/ingest/upload', formData, {
      headers: { 'Content-Type': 'multipart/form-data' }
    })
    
    // Navigate to job tracking
    router.push(`/logs/${response.data.job_id}`)
  }
  
  return (
    <Modal>
      <ModalBody>
        <VStack spacing={4}>
          <Text>Select a folder containing your images:</Text>
          
          <Box
            p={6}
            border="2px dashed"
            borderColor="gray.300"
            borderRadius="md"
            cursor="pointer"
            onClick={() => fileInputRef.current?.click()}
            _hover={{ bg: 'gray.50' }}
          >
            <VStack>
              <Icon as={FiUploadCloud} boxSize={12} color="gray.500" />
              <Text fontWeight="medium">Click to select a folder</Text>
              <Text fontSize="sm" color="gray.500">
                Files will be uploaded to the server for processing
              </Text>
            </VStack>
          </Box>
          
          <Input
            type="file"
            ref={fileInputRef}
            onChange={handleFolderSelect}
            style={{ display: 'none' }}
            {...{ webkitdirectory: 'true', mozdirectory: 'true' }}
          />
          
          {selectedFiles && (
            <Alert status="success">
              <AlertIcon />
              <Text>{selectedFiles.length} files selected</Text>
            </Alert>
          )}
        </VStack>
      </ModalBody>
      
      <ModalFooter>
        <Button 
          colorScheme="blue" 
          onClick={handleUpload}
          isDisabled={!selectedFiles}
        >
          Upload and Process
        </Button>
      </ModalFooter>
    </Modal>
  )
}

Read the full file on GitHub · 678 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 678 lines · 0 tokens per session scan A 9ca576383514

Subscribe to this mod's changes

ux-workflow-patterns is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,616 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.