メニュー
Answer questions about a project's context, issues, and domain by searching docs. Use when the user asks any question about project-level knowledge scoped to a named project folder under docs/.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/asteasolutions/ai-toolkit --skill project-contextコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Grounded research. Traceability-first research workflow for evidence, reliability, product, policy, technical, sentiment, complaint, review, public-opinion, and source-backed questions. Use when the user asks for grounded research, rigorous research, exact source traceability, text fragment links, citations, verification, fact-checking, adversarial review, counterevidence, confidence labels, source hierarchy, or a claim-to-source evidence map. Also use when another skill needs source-backed claims checked against primary sources, current product/tool information, community sentiment, or contested evidence.
Evidence discipline for factual claims. Receipts before claims, no guessing, unknown is an allowed answer. Use as the baseline standard when citing sources, files, or command output, and when the user asks you to re-check an answer you already gave because they cannot verify it themselves.
use when the user wants a simple worded reply, or expresses that your speech is too complex, jargon-heavy, hard to understand etc. Or when they say "keep it simple"
SKILL.md を表示中
| name | project-context |
| description | Answer questions about a project's context, issues, and domain by searching docs. Use when the user asks any question about project-level knowledge scoped to a named project folder under docs/. |
node .claude/skills/project-context/scripts/check-freshness.js <project>
"Docs for [project] were last synced [X hours/days] ago. They may be out of date — run /docs-generator to refresh.""No docs found for [project]. Run /docs-generator to generate them first."
Continue regardless — stale docs are better than no answer.node .claude/skills/project-context/scripts/search-project-docs.js <project> "<keyword>"
--fuzzy (matches the keyword's characters in order, tolerating typos or partial recall) before concluding there's nothing relevant.
One search is usually enough. Only run a second exact search with a related term if the first returns fewer than 5 results.check-freshness.js <project>
project Folder name under docs/
Output: staleness status — "ok", "stale", or "missing" — with age in hours.
Exit 0 always (stale docs are still usable).
search-project-docs.js <project> [keyword] [--fuzzy] [--case-sensitive]
project Folder name under docs/
keyword Optional. Search term. Matches file name or content.
--fuzzy Subsequence match instead of substring — use as a fallback when an
exact search returns nothing, to tolerate typos or partial recall.
--case-sensitive Disable the default case-insensitive matching.
Output: matching file paths + first matching line with context.
Exit 1 if the project folder does not exist.