wiki-editing

name	wiki-editing
version	1.0.0
description	Guides contributors when editing wiki documentation files. Provides dependency context, related file suggestions, and style enforcement.
triggers	[{"file_changed":"standards/**"},{"file_changed":"playbooks/**"},{"file_changed":"ai/**"},{"file_changed":"workflows/**"},{"file_changed":"principles/**"},{"file_changed":"onboarding/**"},{"file_changed":"skills/**"},{"file_changed":"architecture/**"},{"file_changed":"decision-records/**"}]

Wiki Editing Skill

Purpose

Assist contributors when editing or creating documentation in the Frontend OS wiki. Automatically provides dependency context, suggests related file updates, and enforces writing standards.

When This Activates

• Any markdown file in the wiki directories is opened for editing
• A new file is being created in a wiki directory
• User asks for help writing documentation in this repository

Core Behaviors

1. Dependency Awareness

Before suggesting or making changes:

1. Read .github/wiki-dependencies.yml to understand the dependency graph
2. Identify which documents depend on the file being edited
3. Identify which documents the current file depends on
4. Alert the user if their change may affect related documents

Output format:

📋 This file is referenced by:
  - playbooks/component-design/build-feature-component.md (implements)
  - ai/skills/component-design/SKILL.md (extends)

⚠️ Your change to "layer naming" may affect these files.

2. Structure Enforcement

Verify the document follows the correct template:

• Standards → Must have: Foundational Principles, Overview, Goals, Decision Framework, Examples (✅/❌), Related
• Playbooks → Must have: Goal, Prerequisites, Steps with Checkpoints, Troubleshooting
• ADRs → Must have: Status, Date, Context, Decision, Consequences, Alternatives
• Skills → Must have: YAML frontmatter per ai/skills/agent_skills_spec.md
• Onboarding → Must have: Who This Is For, Steps with Checkpoints

3. Writing Style

Enforce from .github/copilot-instructions.md:

• Active voice
• Pragmatic and concise
• Code examples with language tags
• ✅/❌ example pattern for standards
• No jargon without context
• Relative links for internal references

4. Code Example Validation

For any TypeScript code blocks:

• Verify syntax is valid TypeScript (strict mode)
• Check that patterns align with standards/tech-stack.md versions
• Ensure examples are self-contained and realistic
• Use proper variable names (not foo, bar, data)

5. Cross-Reference Suggestions

When content mentions concepts from other documents:

• Suggest adding a link to the related document
• Verify existing links still resolve
• Suggest updating the dependency manifest if new relationships are created

Context Files

Always load these for context:

• .github/wiki-dependencies.yml — dependency graph
• .github/copilot-instructions.md — writing style rules
• standards/_template.md — standard document template
• standards/tech-stack.md — current technology versions

Example Interaction

User edits standards/01-architecture/reference/layers.md and renames "core layer" to "foundation layer":

📋 Dependency Impact Analysis:

This file has 6 dependents:
  - playbooks/component-design/build-feature-component.md (implements) ← ⚠️ uses "core layer"
  - playbooks/component-design/extract-shared-component.md (implements) ← ⚠️ uses "core layer"
  - playbooks/component-design/refactor-growing-component.md (implements)
  - ai/skills/component-design/SKILL.md (extends) ← ⚠️ references layer names
  - standards/code-standards.md (references)
  - standards/16-code-organization/README.md (references)

Suggestion: Update "core layer" → "foundation layer" in the 4 flagged files.

Limitations

• Cannot verify patterns against production code (suggest human validation)
• Dependency manifest may be incomplete (suggest additions when detected)
• Cannot assess domain correctness (only structural and referential)