edmund-architecture-contract

Define architectural and design constraints for the Edmund Markdown editor.

164|13|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/I7T5/Edmund --skill edmund-architecture-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edmund-architecture-contract
Source: https://github.com/I7T5/Edmund/tree/main/.agents/skills/edmund-architecture-contract
Command: npx skills add https://github.com/I7T5/Edmund --skill edmund-architecture-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill defines the architectural and design constraints for the Edmund Markdown editor, ensuring consistent and predictable behavior across development.

Core Features & Use Cases

  • Design Contract: Outlines the core design principles and constraints that govern the editor's development.
  • Technical Guidelines: Provides detailed guidelines on the usage of TextKit 2, handling IME composition, and rendering model.
  • Use Case: Before implementing any significant changes to the editor, developers consult this Skill to ensure adherence to the established architecture.

Quick Start

To review the architecture contract for the Edmund Markdown editor, open the 'SKILL.md' file within the '.agents/skills/edmund-architecture-contract' directory.

Frequently Asked Questions about edmund-architecture-contract

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

FAQPage Schema
How do I define the architecture contract for a Markdown editor using TextKit 2?

An architecture contract for a Markdown editor establishes core design principles, rendering pipelines, edit/undo flows, and the TextKit 2 drawing model to ensure consistent and predictable development behavior.

How does the TextKit 2 drawing model handle rendering pipelines in a code contract?

The TextKit 2 drawing model governs the rendering pipeline by providing technical guidelines for text layout, IME composition handling, and drawing constraints defined within the architecture contract.

When do I need to consult development guidelines for an editor refactoring process?

You need to consult development guidelines before implementing any significant changes or refactoring the editor, ensuring new features adhere to established architectural constraints and predictable behavior.

Does this architecture contract cover IME composition handling for TextKit 2?

Yes, the architecture contract covers IME composition handling, providing detailed technical guidelines on how input methods interact with the TextKit 2 rendering and edit flow.

What is the best way to enforce design constraints during editor development?

The best way to enforce design constraints is to define a code contract outlining core principles, rendering pipelines, and edit/undo flows, ensuring all refactoring aligns with the established architecture.