「index」の検索結果

Curate .unikit/MCP-RECHECK-NOTES.md — the project's log of findings about the configured engine MCP server. Four jobs: re-stamp (the server moved, so every entry is suspect), replay (reproduce a `replay: safe` finding inside a disposable sandbox to see whether it still holds), retire (offer to drop what was fixed or went upstream), and upstream (print a ready diff for the packaged INDEX.md). Use for "audit the MCP notes", "are these findings still true", "recheck the MCP traps", "clean up MCP-RECHECK-NOTES", "the server was updated — revisit the notes". Replaying mutates a live editor, so it starts by telling you how to prepare it — save your scene, open an empty one — and asks once before touching anything. Everything it creates lives under a single UNIKIT_AUDIT_<runid> prefix, is deleted in one action, and the scene is never saved. To record a NEW finding use /unikit-mcp-trap instead.

日本語の概要は準備中です。原文の説明を表示しています。

Render the GAME-DESIGN document (the GDD) into a human-readable form — read-only Markdown chapters under docs/design/ (index, systems, flows, content, economy, glossary), with facts resolved inline from GD-IDS.yaml and drafts flagged 🚧. Optional --web also renders an HTML site from the unikit-docs template (falls back to Markdown-only if the template is absent). Use to export or publish the design for people to read, e.g. "render the GDD", "export the game design to docs", "generate readable design docs", "publish the GDD", "make a design doc site". Read-only — it never edits the GDD or registry, only renders it. This renders the game DESIGN — for the project's CODE documentation (README, docs/*, modules, architecture) use /unikit-docs.

日本語の概要は準備中です。原文の説明を表示しています。

Add a short, project-specific rule, convention, or override to .unikit/RULES.md — the quick-capture inbox for this project's rules (common rules always load; topic files in .unikit/rules/ load when the work matches), automatically loaded by /unikit-implement (later promotable via /unikit-memory migrate-rules). Works only with a rule typed as a prompt — it does NOT read files, folders, URLs, or PDFs. Cross-checks against the knowledge base (RULES_INDEX.md) to avoid duplicating core/stack entries. Use for fast, one-line conventions and corrections: "add a rule", "remember this", "convention", "always do X", "never use Y", "from now on do Z", or when the user corrects agent behavior and wants it remembered; also "split the rules into topics" (optimise), "clean up the rules" (prune), "shorten RULES.md" (compact). If the user points to a source (file, folder, URL, PDF, article, book) or wants to research/document framework usage, use /unikit-memory; for architecture decisions use ARCHITECTURE.md.

日本語の概要は準備中です。原文の説明を表示しています。

ออกแบบ schema normalize indexing optimize query migration safety — Postgres MySQL MongoDB

日本語の概要は準備中です。原文の説明を表示しています。

One-command setup for cqs in a new project — skills, tears infrastructure, CLAUDE.md, init, index.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose common cqs issues — stale index, model download, schema mismatch, connection issues.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

日本語の概要は準備中です。原文の説明を表示しています。

Index of DecisionsAI browser automation, computer-use, browser QA, and workflow integration across Codex, Cursor, Claude, and Pi.

日本語の概要は準備中です。原文の説明を表示しています。

Index for Corey Haines marketing skills — use product-marketing first, then pull other skills from the reference clone without duplicating all 44 into the harness.

日本語の概要は準備中です。原文の説明を表示しています。

Master index for DecisionsAI harness setup — ECC, Ponytail, Fallow, RTK, browser/content skills, and IDE thread tools.

日本語の概要は準備中です。原文の説明を表示しています。

SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research.

日本語の概要は準備中です。原文の説明を表示しています。

Manages the Morphir knowledge base under kb/ — OKF bundles and concept documents. Use when adding content to a bundle, creating a new bundle, checking the knowledge base for conformance or provenance drift, building or querying its SQLite index, managing intent through its lifecycle, recording or reading architectural decisions as Decision Records, or navigating, searching and listing its bundles, concepts and links.

日本語の概要は準備中です。原文の説明を表示しています。

End-of-session pass that persists durable facts from the CURRENT session into .claude/memory/. Runs IN-SESSION in the main agent (never via Task — a subagent starts cold with no transcript), prompted by the Stop hook's nudge. Triggers on "persist durable facts from this session", "run memory-extraction", "flush session memory", or "extract memory before close". Reads the in-context transcript plus existing memory, applies the durable-fact predicate below, and writes one file per fact plus one MEMORY.md index line — append-or-update, never clobbering a consumer's existing memory.

日本語の概要は準備中です。原文の説明を表示しています。

Uses the local pruner indexer to gather relevant code context before making changes, debugging, refactoring, or answering questions about this repository.

日本語の概要は準備中です。原文の説明を表示しています。

Generate code context for coding tasks. Run before code changes, bug fixes, or refactoring to get execution paths, key files, symbols, tests, and snippets.

日本語の概要は準備中です。原文の説明を表示しています。

Design or change dygo Entity metadata, Fields, Record Collections, links, naming, routes, indexes, and constraints. Use when a business data model or metadata contract is the main task.

日本語の概要は準備中です。原文の説明を表示しています。

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

日本語の概要は準備中です。原文の説明を表示しています。

Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.

日本語の概要は準備中です。原文の説明を表示しています。

Handle MindIE-SD documentation, governance, contributor workflow, commit or PR conventions, history cleanup, template changes, and version-policy updates with minimal context, fixed review steps, and deterministic output. Use this skill whenever the task touches docs/ 或文档站点内容与配置（Sphinx / Read the Docs / conf.py / index.md / 目录导航 / 首页）、中英文双语配套、治理文档、贡献流程说明、PR/MR 模板或标题正文规范、提交历史整理、版本策略与发布规则。即使用户只说「改个文档」「双语要同步」「commit message 怎么写」「PR 模板加一项」「把提交压一下」「rebase 冲突怎么理」而未提治理规范，也应触发。不负责通用工程实现与仓库默认工作流定义（后者以 AGENTS.md 为准）；Python 格式见 code-standards，Markdown 格式见 markdown-lint。

日本語の概要は準備中です。原文の説明を表示しています。

Produces an attorney-ready memo from a corpus of legal documents supplied by the user. Use when a user shows up with a folder, zip, or vault of case documents and asks for a case summary, case evaluation, litigation package, intake memo, matter overview, or "can you summarize this case for me." The skill ingests the corpus into a searchable index, OCRs anything non-searchable, inventories and diagnoses the practice area, loads the appropriate practice-area playbook module(s) (PI/tort, commercial litigation, IP infringement, or user-authored extensions), iteratively searches the corpus across eight core dimensions plus any module-specific dimensions, defers specialized document clusters (depositions, medical records, discovery, liens) to dedicated sibling skills, and synthesizes a cited memo.

日本語の概要は準備中です。原文の説明を表示しています。

Design and safely evolve data models, schemas, migrations, queries, indexes, and ORM data-access boundaries. Discover the existing engine and migration source before proposing syntax.

日本語の概要は準備中です。原文の説明を表示しています。

Generate llms.txt files from project docs per the llmstxt.org spec, for AI-friendly documentation indexes and discoverability. Use to create or update llms.txt for AI assistants.

日本語の概要は準備中です。原文の説明を表示しています。

Capture, gate, query, and render long-term project knowledge through the gated `mewkit wiki` subsystem. Use to create a wiki, propose/approve candidates (scanner-gated), hand off a skill's terminal artifact as a scanned candidate, recall context, search the FTS index, or list pages. Agents may only PROPOSE candidates; canonical pages are written only via human approve. NOT for short-lived JSON memory (see mk:memory); NOT for fetching external sources (see mk:wiki-research); NOT for HTML snapshots (see mk:wiki-render).

日本語の概要は準備中です。原文の説明を表示しています。