nekomario28/gxkit
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
Agent-native review loops for creative artifacts: inspect code-as-artifacts (charts, game levels, state machines, schemas, shaders, rendered video) with stable codes, exit codes and a storyboard.
概要
Its job is simple: let an AI check its own work before you have to. Write the artifact as code, inspect it, get problems with stable codes and an exit code, fix them, and ship — with a storyboard image as the evidence. Paste into Claude Code, Codex, or Cursor — the agent installs and runs it: One core, sixteen domains. The 3D is rendered with ManimGX — the renderer gxkit's framegx inspects. Most people have one kind of artifact, and most of these tools read a file you already have — a chart script, a rendered video, a published API spec — with no declaration to write. Install the one tool you need (from the repository until the first release; afterwards the same commands are uvx chartgx …): None of these needs a gxkit-specific declaration: chartgx runs the script and reads the figure it builds, apigx and schemagx and flowgx convert the document and apply the same codes as a declaration, and framegx probes the encoded file. Want all sixteen?
README
以下は原文 README の抜粋です。原文を見る。
gxkit
Agent-native review loops for creative artifacts. Its job is simple: let an
AI check its own work before you have to. Write the artifact as code,
inspect it, get problems with stable codes and an exit code, fix them, and
ship — with a storyboard image as the evidence.
Set up with a prompt. Paste into Claude Code, Codex, or Cursor — the agent installs and runs it:
Follow https://raw.githubusercontent.com/nekomario28/gxkit/main/llms.txt. Install gxkit, then inspect .
One core, seventeen domains. The 3D is rendered with ManimGX — the renderer gxkit’s framegx inspects.
Start with one tool
Most people have one kind of artifact, and most of these tools read a file you
already have — a chart script, a rendered video, a published API spec — with no
declaration to write. Install the one tool you need (from the repository until
the first release; afterwards the same commands are uvx chartgx …):
uv tool install "git+https://github.com/nekomario28/gxkit#subdirectory=packages/chartgx"
chartgx inspect my_chart.py
Then point it at what you already have:
| tool | reads | the check only it makes |
|---|---|---|
chartgx inspect chart.py |
a plain matplotlib script | a bar chart whose baseline is not zero |
apigx inspect openapi.json |
the OpenAPI 3 spec your service publishes | a mutating route with no authentication |
schemagx inspect schema.sql |
the DDL your database runs | a foreign key to a non-primary-key column |
flowgx inspect README.md |
the state diagram a document draws | a state nothing can reach |
framegx inspect clip.py |
the video your renderer wrote | a render that is frozen or black |
None of these needs a gxkit-specific declaration: chartgx runs the script and
reads the figure it builds, apigx and schemagx and flowgx convert the
document and apply the same codes as a declaration, and framegx probes the
encoded file.
Want all seventeen? Install the family instead — the contract is identical:
uvx --from "git+https://github.com/nekomario28/gxkit#subdirectory=packages/gxkit" gxkit tools
The loop
Every tool has the same contract, so an agent learns it once:
推奨ツール
別のキーワードを試すか、フィルタを外してください。
インストール
npx skillfish add nekomario28/gxkit