メニュー
Use when scaffolding or extending MCP servers, adding tools/resources/prompts, or hardening MCP tool schemas and handlers. AE.LTD workflow tuned for production-ready MCP delivery.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Diligence-grade product and technical analysis for the ae.ltd proof-agent concept, including comparison against Cursor and Omnara, MVP and production architecture, red-team review, and build-vs-buy evaluation. Use when Codex needs to create or critique PRDs, tech specs, competitive diligence, leadership memos, or multi-agent evaluation packs for agent-runtime, demo-agent, or proof-agent products.
Use when creating or upgrading CLAUDE.md instructions and selecting the right template baseline for repo size, architecture, and team constraints. AE.LTD template decision workflow.
Use when coding decisions depend on current library/framework APIs and you need version-accurate docs before implementation. AE.LTD workflow tuned for fast, verifiable doc grounding.
Use when unit tests look green but confidence is low and mutation testing is needed to expose weak assertions. AE.LTD workflow for targeted mutation runs and actionable test hardening.
Use when converting plain-language automation goals into production-ready n8n workflow JSON with retries, error paths, and credential-safe placeholders. AE.LTD automation blueprint workflow.
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when building custom skills, generating skill templates, fixing naming issues, or understanding the Claude Skills specification.
| name | ae-ltd-mcp-foundry |
| description | Use when scaffolding or extending MCP servers, adding tools/resources/prompts, or hardening MCP tool schemas and handlers. AE.LTD workflow tuned for production-ready MCP delivery. |
Scaffolds and hardens MCP (Model Context Protocol) servers with strict contracts and validation. Niche gem source: model-context-protocol plugin from awesome-claude-code-toolkit.
User: "Create an MCP server for file operations"
→ Confirm context → Lock contracts → Scaffold → Validate → Test → Document
Confirm server context.
Path, language, transport (stdio or sse), and whether this is new or existing.
Lock contract first. Define tool names, descriptions, and input/output schema before writing handlers.
Scaffold or extend. Create server structure (if new), then add tool/resource registration and handler wiring.
Validate hard. Use Zod (TS) or Pydantic (Python). Reject invalid input early with useful error text.
Test one happy-path and one failure-path per tool. Prefer runnable tests or lightweight CLI/integration checks.
Document usage for agent callers. Keep descriptions explicit so models can invoke tools correctly.
stdio unless user asks otherwise.