create-instructions

Create .instructions.md files that codify project rules and coding conventions.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill create-instructions-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-instructions
Source: https://github.com/Tyrizx/Tyrizx/tree/main/extensions/copilot/assets/prompts/skills/create-instructions
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill create-instructions-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams repeatedly correct AI agents for the same style or convention violations because those rules are never written down. This Skill turns ad-hoc corrections and preferences from a conversation into a persistent, reusable instructions file. ## Core Features & Use Cases - Conversation Mining: Reviews the chat history to extract corrections, enforced patterns, and project-specific conventions worth persisting. - Guided Clarification: Asks targeted questions about scope, affected file types, and whether a rule is mandatory or a preference when intent is unclear. - Iterative Refinement: Drafts the instruction, probes the weakest or most ambiguous parts, and finalizes with a summary plus suggested follow-up customizations. - Use Case: After repeatedly telling the agent to "always use early returns" and "never use default exports", invoke this Skill to capture those rules in a .instructions.md file that applies automatically in future sessions. ## Quick Start Ask the agent to create an instructions file that enforces the coding conventions we discussed in this conversation.

Frequently Asked Questions about create-instructions

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

FAQPage Schema
How do I create an instructions file for AI coding agents?▼

Invoke the create-instructions skill and describe the rule or convention to enforce. It reviews the conversation for corrections and preferences, drafts a .instructions.md file, and refines it with you before saving.

How to turn repeated agent corrections into a persistent rule?▼

The skill scans conversation history for patterns like "always use X" or "never do Y" and generalizes them into a written instruction. You confirm scope and affected file types before the rule is saved.

Can instructions apply only to specific files or technologies?▼

Yes. During clarification, the skill asks whether the rule applies everywhere or only to specific files, technologies, or file types, and encodes that scope in the instructions file.

What if no clear rule emerges from the conversation?▼

The skill asks clarifying questions about scope, affected technologies, and whether the rule is mandatory or a preference. It can also explore the codebase with subagents to gather more context.

When should I use an instructions file instead of inline prompts?▼

Use an instructions file when a convention recurs across sessions, such as style rules or project patterns. One-off requests are better handled directly in the prompt rather than persisted as standing rules.