XIP Writing (XerahS Improvement Proposals)
XIP Writing Skill
This skill guides writing XerahS Improvement Proposals (XIPs) that are actionable, well-structured, and aligned with project architecture.
Workflow: GitHub is the source of truth for XIPs; the tasks/ folder is a backup. Create and edit XIPs as GitHub issues (label xip), then run the sync script to update the tasks folder. See sync-xips for create/edit/sync workflows.
What is a XIP?
A XIP (XerahS Improvement Proposal) is a design document that:
- Describes a new feature, enhancement, or architectural change
- Provides implementation guidance for developers
- Serves as the single source of truth for the feature scope
- Links to a GitHub issue for tracking
XIP Structure
More from sharex/xerahs
design-ui-window
Redesigns or normalises any XerahS Avalonia .axaml page, dialog, or tool window to consistent app quality. Enforces layout, spacing, theming, surfaces, buttons, scrollbars, accessibility, and visual hierarchy. Only changes visuals, layout, and styles; never business logic, bindings, or public view-model API. Reusable by updating target_view_path.
71sharex core standards
License headers, build configuration rules, dependency version guidance, and general coding standards for XerahS
61sharex workflow and versioning
Canonical Git, commit/push, and Directory.Build.props versioning workflow for XerahS. Use for any task that changes version numbers or requires commit/push.
61changelog management
Rules and workflows for updating CHANGELOG.md, including version grouping, consolidation, and commit handling.
59sharex feature specifications
Detailed specifications for Uploader Plugin System and Annotation Subsystem features
58sharex architecture and porting
Platform abstraction rules, porting guidelines, and architecture standards for XerahS
57