搜索

PythonReactSEOPDF
GitHub Skill

creating-instructions

Create VS Code Copilot custom instruction files for ui-kit. Use when defining coding standards, conventions, or context that should automatically apply to specific file patterns.

coveo☆ 61 仓库 Stars40 仓库 Forks

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

查看来源 ↗使用指南

技能说明

Creating Custom Instructions

Process

Step 1: Plan the Instruction

Before creating, check for overlap and determine scope:

# List existing instructions with patterns
for f in .github/instructions/*.instructions.md; do
  echo "=== $(basename $f) ==="
  grep "applyTo:" "$f"
done

Answer:

  1. What file pattern(s) should this apply to?
  2. Does this overlap with existing instructions?
  3. What are the 3-5 most critical rules?

Decision:

  • Exact match exists → Modify existing (see "Modifying" below)
  • Partial overlap → Extend existing OR create with distinct scope
  • No overlap → Create new
Step 2: Initialize
node .github/skills/creating-instructions/scripts/init_instruction.mjs {name}

# With custom pattern
node .github/skills/creating-instructions/scripts/init_instruction.mjs {name} --apply-to "glob-pattern"

Creates: .github/instructions/{name}.instructions.md with frontmatter and TODO sections.

Naming conventions:

Scope Pattern Example
Package {package}.instructions.md atomic.instructions.md
File type general.{type}.instructions.md general.typescript.instructions.md
Tests tests-{package}.instructions.md tests-atomic.instructions.md
Technology {tech}.instructions.md msw-api-mocking.instructions.md

See naming-conventions.md for details.

Step 3: Complete the Instruction

Fill in the generated file:

  1. Start with the most critical rule
  2. Organize by topic with clear headings
  3. Provide concrete code examples
  4. Reference related files with Markdown links
  5. Document hierarchy if conflicts possible

For format details, see SPECIFICATION.md. For writing guidance, see best-practices.md. For examples, see examples.md.

Step 4: Validate
node .github/skills/creating-instructions/scripts/validate_instruction.mjs .github/instructions/{name}.instructions.md

Manual checks:

  • Most critical rule appears first
  • Concrete examples provided
  • No duplicated content
  • Hierarchy documented if needed

Modifying Existing Instructions

Extending:

  1. Read existing file to understand scope
  2. Add new sections logically
  3. Re-run validation

Changing scope:

  1. Update applyTo frontmatter
  2. Check for new conflicts
  3. Update hierarchy documentation

Renaming:

  1. Rename file following conventions
  2. Search for references: grep -r "{old-name}.instructions.md" .github/
  3. Update references
  4. Re-validate

Deprecating:

  1. Verify no active references
  2. If merging, copy unique content to target
  3. Delete file

Existing Instructions

File Pattern Purpose
general.instructions.md ** Core principles
general.typescript.instructions.md **/*.ts, **/*.tsx TypeScript rules
atomic.instructions.md packages/atomic/** Atomic conventions
tests-atomic.instructions.md **/atomic/**/*.spec.ts Atomic test patterns
playwright-typescript.instructions.md **/*.e2e.ts, **/*.spec.ts E2E patterns
msw-api-mocking.instructions.md packages/atomic/**/*.stories.tsx Storybook MSW

Update this table when creating new instructions.

Reference Documentation

Reference When to Load
SPECIFICATION.md VS Code instruction format, frontmatter, patterns
best-practices.md Writing effective instructions, terminology
examples.md Real-world instruction examples
naming-conventions.md File naming patterns

Scripts

Script Purpose
init_instruction.mjs Initialize with template
validate_instruction.mjs Validate structure per spec

使用示例

查看来源仓库中的使用示例与配置说明。

查看来源 ↗

来源历史

收录时间
2026-01-20
索引更新时间
2026-02-04
Branch
main

收录与同步日期属于本站记录。源码修改历史请查看来源仓库。

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!