Repository navigation
docs: Add AI Integration page and Copy Markdown chip - #228
Merged
Merged
Conversation
Add a small dropdown in the top-right of every /docs and /api page that opens the current page in ChatGPT or Claude pre-filled with "Read <page-url>, I want to ask questions about it.". Also add a Guides > LLMs.txt page (en + ko) that documents the existing /llms.txt, /llms-full.txt, /ai.txt endpoints and how to use them from assistants. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Switch the top-right chip on /docs and /api pages to a split button: - left click fetches the page's raw .mdx from raw.githubusercontent.com and copies it to the clipboard (no build pipeline required) - caret opens the existing ChatGPT / Claude shortcuts dropdown Update the LLMs.txt guide (en + ko) to describe both actions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replace the placeholder geometric icons with the actual OpenAI monoblossom and Claude wordmark glyphs as inline SVG paths. Both use fill="currentColor" so the theme's light/dark colors flow through naturally. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Trim the OpenAI SVG viewBox to the path's bounding box so it renders at the same visual size as the Claude glyph. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Add docs sidebar group "AI for Agents" (en) / "AI 에이전트용" (ko) alongside the existing Guides and Learn More groups - Move llms-txt.mdx from Guides to the new group - Rewrite the page: H1 is now "AI Integration" / "AI 통합", drop the License and Cursor/VS Code stub sections, split ChatGPT and Claude into their own headers, and add a leading positioning line about grounding agents in the real API surface - Clarify that /llms.txt, /llms-full.txt, /ai.txt are English-only and that per-page Markdown in either language comes from the Copy Markdown button Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Restructure the page to mirror es-toolkit's AI integration layout: each endpoint gets its own H3, the page closes with a "Using these endpoints" subsection that shows a one-line prompt example. Use the friendlier "~해요" style in the Korean copy to match the rest of the docs and not sound machine-generated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
@qkraudghgh is attempting to deploy a commit to the Toss Team on Vercel. A member of the Team first needs to authorize it. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #228 +/- ##
=======================================
Coverage 99.85% 99.85%
=======================================
Files 15 15
Lines 1340 1340
Branches 262 262
=======================================
Hits 1338 1338
Misses 2 2
🚀 New features to boost your workflow:
|
jungpaeng
approved these changes
Jun 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Surface an AI-friendly entry point in the docs.
Documentation > AI for Agents(한국어:AI 에이전트용) with a single page that documents the existing/llms.txt,/llms-full.txt,/ai.txtendpoints already shipping under/public/. The page follows es-toolkit's AI Integration layout and uses the docs' usual~해요voice in Korean./docsand/apipage:.mdxfromraw.githubusercontent.comand copies it to the clipboard — no build pipeline required.Read <page-url>, I want to ask questions about it.fill="currentColor", so light/dark themes flow through naturally.Screenshots
Copy Markdown chip (closed)
Copy Markdown chip (dropdown open)
AI Integration page (English)
AI 통합 page (Korean)
Test plan
yarn lintpasses/docs/*and/api/*, hidden on landing pages.mdxto the clipboardAI for Agents > LLMs.txtrenders in both English and Korean