instructions-architect

Design and review AI agent instruction files for consistent runtime behavior.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/alatyshau/duet --skill instructions-architect-alatyshau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: instructions-architect
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/tools/instructions-architect
Command: npx skills add https://github.com/alatyshau/duet --skill instructions-architect-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agent instructions often fail because they are bloated, overfit to one-off failures, or written for human reviewers instead of the agent executing them. This Skill provides a disciplined methodology for writing, editing, and reviewing instruction files so agents behave predictably at runtime. ## Core Features & Use Cases - Instruction Writing Guidelines: Apply principles like behavioral WHY, progressive disclosure, and examples-over-explanations to produce instructions agents actually follow. - Edit Protocol: Distinguish minor in-place edits from paradigm shifts, generating _v2 sibling files for structural changes so users can diff and review before adopting. - Skill and Persona Authoring: Enforce the skill_file.md schema with valid YAML frontmatter (name, description, trigger) so files are discoverable in the dynamic catalog. - Use Case: When an agent repeatedly misinterprets a rule, use this Skill to diagnose whether the instruction lacks behavioral reasoning, then rewrite it with a leading WHY pattern instead of stacking rigid ALWAYS/NEVER constraints. ## Quick Start Ask the agent to review an existing skill file and rewrite it following the instructions-architect principles, cutting design rationale and adding behavioral reasoning to each rule.

Frequently Asked Questions about instructions-architect

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

FAQPage Schema
How do I write effective AI agent instructions?

Write rules with behavioral reasoning that explains why the rule matters at execution time, not rigid ALWAYS/NEVER constraints. Lead with the motivation so the constraint feels obvious, and use concrete examples instead of abstract descriptions of good output.

How to structure a skill file for AI agents?

A skill file needs YAML frontmatter with name and description, a body under 500 lines that starts with the job the agent should perform, and pointers to companion resources loaded on demand. Without valid frontmatter, the file will not appear in the catalog.

When should I create a v2 file instead of editing instructions in place?

Create a sibling _v2 file for paradigm shifts: new phases, reframed purpose, new mandatory artifacts, or changed invariants. Minor wording fixes and small rule additions are edited in place. The user reviews and replaces the original after accepting the v2.

What content should be cut from always-loaded instruction files?

Cut design rationale, defence of choices for future maintainers, documentation framing, and restatements of rules the agent already has in its system prompt. If removing a sentence does not change what the agent does on a turn, it has no reader.

Why do rigid ALWAYS and NEVER rules fail in agent instructions?

Rigid rules break on edge cases because they give no reasoning for the agent to generalize from. Explaining the behavioral motivation lets the agent apply the intent to novel situations, producing more robust behavior than stacked MUSTs.