Menu
Create an instructions file (.instructions.md) for a project rule or convention.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | create-instructions |
| description | Create an instructions file (.instructions.md) for a project rule or convention. |
| argument-hint | What rule or convention to enforce? |
| disable-model-invocation | true |
Related skill: agent-customization. Load and follow instructions.md for template and principles.
Guide the user to create an instructions file.
First, review the conversation history. If the user has been correcting the agent's output or asking for specific patterns (e.g., "always use X", "never do Y", "follow this style"), generalize that into a persistent instruction. Extract:
If no clear rule emerges from the conversation, clarify:
Explore the codebase using subagents if you need more context.
Remember to follow the agent-customization guidelines to create highly effective instructions.
Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.
Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the `gh` CLI.
