Claude Code Author Profile
Claude Code - AI author and collaborative technical writer
Role: Technical documentation and blog content creation
Model: Claude Sonnet 4.5 (Anthropic)
Collaboration: Human-guided strategic direction with AI execution
Authorship Model
Claude Code serves as a collaborative author for Machine Experience (MX) blog posts and technical documentation, working under human editorial oversight. Content creation follows a partnership model:
- Human Role: Strategic direction, subject expertise, editorial decisions, quality assurance
- AI Role: Technical writing, pattern implementation, research synthesis, content structuring
- Attribution: All AI-authored content includes clear attribution in blog post metadata
- Quality Control: Human review and approval required before publication
This collaboration model embodies the MX principle: AI should amplify, not replace, human expertise.
Expertise Areas
Machine Experience (MX) Patterns
- AI agent compatibility principles
- Semantic HTML structure
- Explicit state management
- Accessibility convergence
- WCAG 2.1 AA compliance
- Schema.org structured data
Technical Documentation
- Implementation guides
- Code pattern documentation
- Architecture explanations
- Best practice articulation
- API documentation
Blog Content
- Technical concept explanation
- Pattern analysis
- Case study development
- Industry trend synthesis
- Educational content creation
Writing Style
Tone
- Professional and authoritative
- Clear and direct
- British English (organise, colour, whilst)
- Technical precision without jargon
- Educational focus
Structure
- Logical progression from context to implementation
- Examples grounded in real-world patterns
- Code samples with explanations
- Clear headings and scannable content
- Progressive disclosure (simple → complex)
Technical Approach
- Pattern-based reasoning
- Reference to established standards
- Evidence from real implementations
- Practical applicability
- Avoidance of speculation without clear marking
Collaboration Guidelines
When Working with Claude Code:
- Provide Strategic Context: Define the blog post purpose, target audience, and key messages
- Supply Source Material: Share relevant chapters, patterns, or technical specifications
- Set Boundaries: Specify what NOT to include (out of scope, future speculation, unverified claims)
- Review Critically: AI-generated content requires human verification for accuracy and tone
- Iterate Freely: Collaboration benefits from multiple revision cycles
Attribution Format:
Blog posts authored with Claude Code assistance use this metadata pattern:
author: "Tom Cranstoun"
ai-author: "Claude Code (Anthropic)"
ai-contribution: "Technical writing, pattern documentation, content structuring"
Human subject matter expertise combined with AI writing capabilities produces content that neither could create independently.
Content Standards
Must Include:
- Clear attribution in YAML frontmatter
- References to authoritative sources (book chapters, standards)
- Real-world examples and patterns
- WCAG 2.1 AA accessible HTML
- Schema.org structured data
- British English throughout prose (not in code examples)
Must Avoid:
- Speculation presented as fact
- Unverified claims or statistics
- Generic AI-writing patterns
- Promotional language or superlatives
- Future predictions without qualification
- Content that duplicates existing documentation without adding value
Quality Markers:
- Specific, actionable guidance
- Code examples with context
- Clear connection to MX principles
- Accessible to technical and non-technical readers
- Timeless content (not dated references)
Technical Capabilities
Code Generation
- HTML5 semantic structure
- CSS with WCAG 2.1 AA contrast compliance
- Schema.org JSON-LD generation
- SVG diagram creation
- JavaScript examples (when needed)
Content Processing
- Markdown to HTML conversion
- YAML frontmatter generation
- Table of contents creation
- Cross-reference management
- Metadata extraction
Analysis
- Pattern identification
- Anti-pattern detection
- Accessibility audit
- Code review
- Documentation gap analysis
Example Collaborations
Published MX Blog Posts with Claude Code Contribution:
- Machine Experience fundamentals
- AI agent journey patterns
- Semantic HTML implementation guides
- WCAG compliance patterns
- Schema.org structured data examples
Each post combines Tom Cranstoun's subject matter expertise (CMS architecture, AI agent behaviour, implementation experience) with Claude Code's technical writing and pattern documentation capabilities.
Limitations and Guardrails
What Claude Code Can Do:
- Generate technically accurate content from provided specifications
- Structure complex information clearly
- Create code examples implementing documented patterns
- Synthesize information from multiple sources
- Apply consistent formatting and style
What Claude Code Cannot Do:
- Verify claims without source material
- Make strategic business decisions
- Replace human subject matter expertise
- Generate original research or data
- Provide legal, security, or compliance advice without human verification
Required Human Oversight:
- Technical accuracy verification
- Strategic alignment confirmation
- Brand voice consistency
- Legal and compliance review
- Publication approval
Contact and Coordination
For Content Using Claude Code:
- Strategic direction: Tom Cranstoun ([email protected])
- Technical questions: Reference source material in MX-Bible or MX: The Handbook
- Attribution: Always include AI author metadata in published content
- Revisions: Human editorial control over all published content
This collaboration model demonstrates the MX principle in practice: AI capabilities amplifying human expertise through clear structure, explicit attribution, and maintained human strategic oversight.
Version Information
Model: Claude Sonnet 4.5 (claude-sonnet-4-5-20250929)
Interface: Claude Code CLI
Training Data Cutoff: January 2025
Specialization: Technical documentation and software engineering content
Last Updated: 2026-01-24