tegwick
7d115b6325
Enhanced schema-list and schema-validate commands to support efficient batch validation of multiple schemas, especially useful when the metaschema changes. **schema-list enhancements:** - Added numbered references (#1, #2, etc.) to all output formats - Simple format: [1] prefix for each schema - Table format: # column as first column - JSON/YAML: number field added to each schema **schema-validate enhancements:** - Number selection: `markitect schema-validate 1` - Range selection: `markitect schema-validate 1-3` - List selection: `markitect schema-validate 1,3,5` - Batch validation: `markitect schema-validate --all` - Filename selection: `markitect schema-validate schema.md` - Filesystem path: `markitect schema-validate ./schema.md` - Batch results displayed as clear summary table - Registry schemas take precedence with filesystem fallback - Full backward compatibility maintained **Implementation details:** - Added ValidationResult dataclass for structured results - Added helper functions: parse_schema_selector, resolve_schema_source, is_filesystem_path, format_validation_summary - Changed schema_selector from Path to str for flexible input - Added --all flag for validating all registered schemas - Comprehensive error handling and helpful usage messages **Testing:** - All selection methods tested and working - Backward compatibility verified - Parsing utilities tested with unit tests Completes Phase 5 of Schema-of-Schemas implementation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
MarkiTect Documentation
Welcome to the MarkiTect documentation. This directory contains comprehensive documentation for developers, users, and contributors.
Documentation Structure
📐 Architecture Documentation (architecture/)
Deep technical documentation about system design, performance, and implementation details.
- Capabilities Architecture - Critical: How capabilities work as independent git submodules and separation of concerns
- Caching System - Why and how MarkiTect's AST caching delivers 60-85% performance improvements
- Coming soon: Database Schema, CLI Architecture
👥 User Guides (user-guides/)
End-user documentation for working with MarkiTect CLI and features.
- Coming soon: Getting Started, Command Reference, Best Practices
🔧 Development Documentation (development/)
Documentation for contributors and developers extending MarkiTect.
- Coming soon: Contributing Guide, Testing Strategy, Release Process
Quick Links
For Users
- Installation & Setup
- Command Reference (coming soon)
- Performance Guide (coming soon)
For Developers
- Architecture Overview - System design and component relationships
- Development Setup - Local development environment
- API Documentation (coming soon)
Project Management
- Project Status - Current development status
- Roadmap - Strategic development plan
- Current Tasks - Task management using Keep a Todofile format
Key Concepts
Core Architecture Principles
- Parse Once, Use Many Times - AST caching for 60-85% performance improvement
- Convention Over Configuration - Sensible defaults with minimal setup
- Schema-Driven Processing - Structured markdown with validation
- Relational Metadata - Database-powered document relationships
Performance Philosophy
MarkiTect treats markdown documents as structured, queryable data rather than plain text. This approach enables:
- Lightning-fast document processing through intelligent caching
- Complex querying and relationship management
- Schema validation and consistency enforcement
- Scalable performance that grows with your content
Contributing to Documentation
Documentation follows the same quality standards as code:
- Clear Structure - Logical organization and navigation
- Practical Examples - Real-world usage patterns
- Performance Context - Why architectural decisions matter
- User-Focused - Written for the intended audience
Documentation Standards
- Use clear, concise language
- Include practical examples
- Explain the "why" behind design decisions
- Keep technical accuracy as the highest priority
- Update docs when changing functionality
This documentation is maintained alongside the codebase. For the most current information, always refer to the latest version in the repository.