Skip to content

docs: emphasize coding agent friendly design across documentation#26

Merged
chaliy merged 3 commits into
mainfrom
claude/update-ai-generation-tools-JUgLC
Jan 10, 2026
Merged

docs: emphasize coding agent friendly design across documentation#26
chaliy merged 3 commits into
mainfrom
claude/update-ai-generation-tools-JUgLC

Conversation

@chaliy
Copy link
Copy Markdown
Owner

@chaliy chaliy commented Jan 10, 2026

Summary

  • Update README tagline to "Coding Agent friendly tool to magically generate text and images"
  • Add CI, crates.io, and coding agent friendly badges
  • Add new specs/coding-agent-design.md documenting agent-friendly design principles
  • Update AGENTS.md top-level requirements and pre-PR checklist

What

This PR aligns documentation with the project's mission as a coding agent friendly tool by:

  • Renaming from "Magic tool to generate things" to "Trickery" with clear agent-friendly messaging
  • Adding "Agent-Friendly Design" section highlighting key features (error recovery, help system, JSON output)
  • Creating spec documenting why design choices matter for agents (discoverability, error recovery, predictable behavior)
  • Adding pre-PR requirement to update README via prompt template

Why

The tool already has excellent agent-friendly features (rich error messages, full help, JSON output), but documentation didn't communicate this clearly.

How

Documentation-only changes across README, AGENTS.md, docs/index.md, and new spec file.

Risk

  • Low
  • Documentation only, no code changes

Checklist

  • Unit tests are passed
  • Smoke tests are passed
  • Documentation is updated

- Update README tagline to "Coding Agent friendly tool to magically generate text and images"
- Add Agent-Friendly Design section to README highlighting key features
- Add coding-agent-design.md spec documenting design principles for agent compatibility
- Update AGENTS.md top-level requirements to reflect agent-friendly mission
- Update docs/index.md to reference all specs
- Update prompts/trickery_readme.md with agent-friendly messaging
- Add pre-PR checklist item: regenerate README from template
@chaliy chaliy force-pushed the claude/update-ai-generation-tools-JUgLC branch from 5d339aa to 810f812 Compare January 10, 2026 19:47
@chaliy chaliy force-pushed the claude/update-ai-generation-tools-JUgLC branch from 810f812 to e12c8a5 Compare January 10, 2026 19:52
@chaliy chaliy merged commit 9140891 into main Jan 10, 2026
1 check passed
@chaliy chaliy deleted the claude/update-ai-generation-tools-JUgLC branch January 10, 2026 19:54
chaliy added a commit that referenced this pull request May 30, 2026
## Summary

- Update README tagline to "Coding Agent friendly tool to magically
generate text and images"
- Add CI, crates.io, and coding agent friendly badges
- Add new `specs/coding-agent-design.md` documenting agent-friendly
design principles
- Update AGENTS.md top-level requirements and pre-PR checklist

## What

This PR aligns documentation with the project's mission as a coding
agent friendly tool by:

- Renaming from "Magic tool to generate things" to "Trickery" with clear
agent-friendly messaging
- Adding "Agent-Friendly Design" section highlighting key features
(error recovery, help system, JSON output)
- Creating spec documenting why design choices matter for agents
(discoverability, error recovery, predictable behavior)
- Adding pre-PR requirement to update README via prompt template

## Why

The tool already has excellent agent-friendly features (rich error
messages, full help, JSON output), but documentation didn't communicate
this clearly.

## How

Documentation-only changes across README, AGENTS.md, docs/index.md, and
new spec file.

## Risk

- Low
- Documentation only, no code changes

### Checklist
- [x] Unit tests are passed
- [x] Smoke tests are passed
- [x] Documentation is updated

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants