create-instructions

To turn project conventions into a persistent instructions file, identify recurring user corrections and style preferences from your conversation. The skill extracts these patterns and drafts a durable .instructions.md file to ensure consistent agent behavior across future workflows.

Enforcing consistent agent behavior across multiple files requires formalizing your preferences into an instructions file. This skill extracts recurring corrections and project rules, clarifies their scope, and produces a persistent .instructions.md file to maintain consistency.

Yes, you can create a reusable instructions file from coding style preferences. The skill identifies recurring feedback and naming patterns from your conversation, then drafts a persistent .instructions.md file aligned with your project conventions.

When a project convention is ambiguous during instruction drafting, the skill initiates a clarification workflow. It prompts you for missing scope details, affected technologies, and rule strength to ensure the generated .instructions.md file accurately captures the intended agent behavior.

The best way to save repeated user corrections is to formalize them into an instructions file. This skill extracts recurring feedback and project conventions from your dialogue, producing a persistent .instructions.md file that keeps future responses consistent.