1,990 件 ・ 関連度順
概要と使いどころ
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use language-specific skills), or infrastructure setup (use deployment-engineer).
日本語の概要は準備中です。原文の説明を表示しています。
Manage knowledge graph for autonomous coding. Use when storing relationships, querying connected knowledge, building project understanding, or maintaining semantic memory.
日本語の概要は準備中です。原文の説明を表示しています。
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.
日本語の概要は準備中です。原文の説明を表示しています。
Route plain-language requests for Pi, Claude Code, Codex, OpenCode, Gemini CLI, or ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read this skill first, then use only `sessions_spawn` for thread creation.
日本語の概要は準備中です。原文の説明を表示しています。
Manage persistent memory for autonomous coding. Use when storing/retrieving knowledge, managing Graphiti integration, persisting learnings, or accessing episodic memory.
日本語の概要は準備中です。原文の説明を表示しています。
Main orchestrator for autonomous coding operations. Use when running autonomous sessions, coordinating components, managing the full lifecycle, or orchestrating implementations.
日本語の概要は準備中です。原文の説明を表示しています。
Technical guide for creating a new Galyarder Framework agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
日本語の概要は準備中です。原文の説明を表示しています。
houtu-dependencies enterprise-grade Spring Cloud microservice foundational framework complete usage guide. GroupId is io.github.lujiafa, covering unified response, exception handling, parameter parsing, session authentication, permission control, signature verification, anti-replay, distributed lock, rate limiting, database field encryption, config decryption, access logging, canary routing, weighted load balancing, Feign enhancement, Sentinel circuit breaking, service discovery, Swagger documentation, crypto utilities, HTTP client, monitoring metrics, and other enterprise-grade capabilities. When the project build file (pom.xml or build.gradle/build.gradle.kts) contains io.github.lujiafa or houtu-related dependencies, or when the user mentions houtu or houtu-dependencies, this Skill must be read and code must be generated strictly following framework conventions. Even if the user is simply doing regular Spring Boot development (e.g., writing Controller, Service, Feign), as long as the project includes houtu, the houtu approach must be used instead of native Spring. When the user explicitly wants to use the houtu framework and the project has not yet included it, proactively add the BOM and required Starters; when the project already includes it, proactively identify and import required module dependencies based on business scenarios during coding, naturally integrating framework capabilities to enhance business services based on business semantics, rather than waiting for the user to specify each one.
日本語の概要は準備中です。原文の説明を表示しています。
Super Base Context — project doc loader & synchronizer. Triggers even without explicit "load docs"/"sync docs." READ MODE — load architecture/modules/coding/decision docs when work references project state: code work (write/modify/remove); design (features/APIs/schemas/architecture); review (modules, past solutions); tech selection; ADR research; migration/refactor planning; performance/security analysis; tests; code reviews; any spec/plan/design/ADR referencing project. WRITE MODE — NET DELTA vs. last doc sync: additions/modifications/REMOVALS/deprecations of previously-synced code or decisions (docs revert: delete BCU file/ADR), AND rollbacks. User signals: sync docs/done/ready to commit/pre-commit/record decision. Auto-fires before final task-completion reply. WRITE MODE does NOT fire on: brainstorming, generic/read-only Q&A, in-session try-and-undo with no net change, already-synced.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Grounded Theory (Glaser and Strauss) to build theory inductively from qualitative data through open, axial, and selective coding. Use this skill when the user needs to develop new theory from data rather than test existing hypotheses, conduct theoretical sampling and constant comparison, determine when theoretical saturation is reached, or when they ask 'what theory explains this phenomenon', 'how do I code qualitative data systematically', or 'when do I stop collecting data'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.".
日本語の概要は準備中です。原文の説明を表示しています。
Implement features with code, tests, and documentation. Use when building features from approved designs following TDD and project coding standards.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging playbook for the Forge agentic loop (src/core/loop.ts and src/agents/executor.ts). Use when a task is stuck, looping, or producing wrong tool calls.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Forge subagent (planner/architect/executor/reviewer/debugger/memory-style).
日本語の概要は準備中です。原文の説明を表示しています。
Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Every bead must be executable without reopening the plan. Use after the plan has converged.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new model provider for Forge — class implementation, registry wiring, providerEnum entry, local-catalog classification, and unit test with mocked transport. Use for anything under src/models/.
日本語の概要は準備中です。原文の説明を表示しています。
End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.
日本語の概要は準備中です。原文の説明を表示しています。
Run Forge's canonical verification chain (format:check + lint + typecheck + build + test). Use before claiming any task done or opening a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.
日本語の概要は準備中です。原文の説明を表示しています。
Deep review — random exploration + cross-agent review, alternating. Finds integration bugs that self-review misses. Run every 30–60 min during active implementation.
日本語の概要は準備中です。原文の説明を表示しています。
End-of-session ritual — close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.
日本語の概要は準備中です。原文の説明を表示しています。
Remove AI-writing tells from README, docs, and user-facing text. Must be done line-by-line, no regex. Use after agents write any user-visible prose.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-release checklist for Forge — verify, version bump, changelog, docs, docker build, smoke test. Run before tagging v*.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Forge tool end-to-end — implementation, registration, permission/risk metadata, sandbox routing, and a unit test.
日本語の概要は準備中です。原文の説明を表示しています。