app-design-input-user-corrections-2

Extract recurring user corrections into reusable rules and apply them to tasks.

171|10|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fmflurry/settings-opencode --skill app-design-input-user-corrections-2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-design-input-user-corrections-2
Source: https://github.com/fmflurry/settings-opencode/tree/main/.claude/skills/app-design-input-user-corrections-2
Command: npx skills add https://github.com/fmflurry/settings-opencode --skill app-design-input-user-corrections-2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This pattern helps teams convert recurring user corrections into reusable guidance that can be applied across tasks, reducing drift and improving consistency.

Core Features & Use Cases

  • Extract corrections as concrete rules and apply them to current work and related decisions.
  • Revalidate outputs against updated expectations and capture corrections for reuse.
  • Use case: apply a recurring user instruction across multiple tasks to ensure consistent outcomes.

Quick Start

Extract the user correction as a concrete rule and apply it to current work to update decisions.

Frequently Asked Questions about app-design-input-user-corrections-2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I formalize recurring user corrections into reusable guidance for my workflows?

User corrections are formalized by extracting them as concrete rules and applying them to current tasks and related decisions. This pattern ensures consistent outcomes and reduces drift across multiple workflows by validating results against updated expectations.

What's the best way to stop output drift when applying a recurring user instruction across multiple tasks?

To stop output drift, extract the user instruction as a concrete rule and apply it consistently across all tasks. Revalidate outputs against updated expectations and capture corrections for reuse to maintain consistent outcomes throughout the workflow.

How does a feedback loop for user corrections prevent regressions in design patterns?

A feedback loop prevents regressions by validating outcomes through logs, tests, and reviews after applying corrections. This guards against drift by ensuring outputs consistently meet updated expectations before the workflow proceeds.

Can I apply a single user correction rule to nearby decisions without re-explaining it each time?

Yes, once a correction is extracted as a concrete rule, it can be applied to current work and nearby decisions automatically. This reusable guidance maintains consistency without needing to re-explain the instruction for every related task.

How do I validate that applied user corrections are actually preventing quality assurance issues?

Validate applied corrections by checking outcomes through logs, tests, and reviews. This quality assurance step confirms the rules are properly integrated and guards against regressions or drift in the workflow outputs.