121 件 ・ 関連度順
概要と使いどころ
Polish, restructure, or translate academic prose into Nature-leaning English using writing-strategy principles, curated Nature/Nature Communications article patterns, and phrase-level support from Academic Phrasebank. Use whenever the user asks to polish a manuscript paragraph, abstract, introduction, results, discussion, conclusion, title, methods section, or Chinese academic draft for publication-quality English.
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite existing pages so AI assistants can extract, quote, and cite them. Claude restructures your content into answer-ready blocks — direct answers, comparison tables, stats with sources, schema — without wrecking the human reading experience. Platform: AI visibility.
日本語の概要は準備中です。原文の説明を表示しています。
Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the agent creates, writes, moves, or renames a file in a team/delegate (shared) workspace, OR when the user asks to organize, clean up, restructure, audit, or find files in any workspace or the Vault, OR when starting a multi-file task or named project. Enforces a purpose-based folder convention (flat mode: notes/, data/, outputs/, scripts/, archive/; project mode: projects/<slug>/{docs,assets,source,reports,research}/), per-agent namespacing under shared/<agent_key>/, and pre-write discovery via memory_search, vault_search, knowledge_graph_search to surface related files and avoid duplicates. Trigger before any write_file or exec at workspace root, when starting a project, generating reports/assets/exports, delegating, or when the user says "messy", "where did I save", "tổ chức lại", "dọn workspace", "tạo report", "find related", "search vault". Do NOT trigger for read-only ops, edits inside an existing project tree (cloned repo), or short-lived files deleted in the same turn.
日本語の概要は準備中です。原文の説明を表示しています。
Plan vault restructuring from config changes. Compares config.yaml against derivation.md, identifies dimension shifts, shows restructuring plan, executes on approval. Triggers on "/refactor", "restructure vault".
日本語の概要は準備中です。原文の説明を表示しています。
Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.
日本語の概要は準備中です。原文の説明を表示しています。
Create, edit, improve, tidy, review, audit, or restructure memmy-agent skills and SKILL.md files.
日本語の概要は準備中です。原文の説明を表示しています。
Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.
日本語の概要は準備中です。原文の説明を表示しています。
Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.
日本語の概要は準備中です。原文の説明を表示しています。
Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.
日本語の概要は準備中です。原文の説明を表示しています。
Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer analytics reads through. Use this to design or restructure a warehouse, model a new source, decide on grain or table structure, build a semantic or metric layer, or diagnose why queries are slow, wrong, or impossible to write.
日本語の概要は準備中です。原文の説明を表示しています。
Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the analysis that says whether to scale or stop. Use this to set up or restructure campaigns, write and iterate ad creative, diagnose rising costs or falling performance, decide budget allocation, or judge whether a channel is working.
日本語の概要は準備中です。原文の説明を表示しています。
Build or restructure a course syllabus from a topic list or reading list — course description + prerequisites, week-by-week schedule (topic → readings → deliverables), measurable learning objectives, an assessment scheme + rubric, standard policies (late work, AI use, academic integrity, accessibility), and a per-week work-list to hand to `/create-lecture`. Use when user says "build a syllabus", "structure my course", "turn this reading list into a schedule", "draft a course outline", "make a syllabus for Econ 7xx", or "map weeks to lectures". Economics-aware (PhD metrics/micro/macro sequences, undergrad); generic enough for any field.
日本語の概要は準備中です。原文の説明を表示しています。
Optimizes or restructures CLAUDE.md/AGENTS.md with progressive disclosure and zero information loss. Use when the user asks to optimize, audit, 精简/瘦身/重构, or split instruction files, asks for their best practices (最佳实践), sees Memory files taking a large share of /context, reports rules in instruction files being ignored, or a task starts moving instruction sections. Not for generic task drift unless instruction files are in scope; not for moving memory entries into docs (use claude-code-ops-router).
日本語の概要は準備中です。原文の説明を表示しています。
Review what an LLM feature or agent actually puts in its context window — and find what's bloating, missing, or fighting itself. Use when asked to review a system prompt and context assembly, cut token usage without losing quality, debug an agent that ignores instructions, or audit how retrieval results, history, and tool definitions are packed into the window. Produces a context inventory with a keep/cut/restructure verdict per component, ordering and caching fixes, and a token budget. For wording-level prompt tuning use prompt-optimizer.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure or clean up code with no behavior change, proved by before-and-after checks. Use when: asked to clean up, extract, dedupe or simplify, even one function.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnosis before prescription: reproduce, hypothesize, isolate, fix root cause, add a regression test; refactor mode maps deps, coupling and blast radius. Triggers: bug, error, fix, broken, not working, crashed, stack trace, exception, refactor, restructure, coupling, dependency map.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an Advanced Materials manuscript must be fit to its article-type format — Communication versus Research Article — where word count and display items are budgeted together against a typeset page limit. Manages the length budget; does not restructure the science or polish prose line by line.
日本語の概要は準備中です。原文の説明を表示しています。
Use when polishing the prose of an Advanced Materials manuscript for Wiley house style, concision, precise materials nomenclature and units, and readability across materials subfields. Polishes language; does not restructure the advance or manage the length budget.
日本語の概要は準備中です。原文の説明を表示しています。
Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system level. Triggers on sitemap, site structure, navigation, IA, information architecture, URL structure, content types, taxonomy, categorization, breadcrumbs, hub pages, faceted navigation, site search, labeling. Also triggers when content is being created without a structural plan, or when an existing site's structure is being audited or restructured.
日本語の概要は準備中です。原文の説明を表示しています。
Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations. Use this skill when planning a CMS migration, replatforming, consolidating sites, changing URL structures, or merging content from multiple sources. Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop. Also triggers when planning a launch that involves moving existing content.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a customized Customer Agreement starting from the Y Combinator standard form SaaS template. Tailors the agreement through structured intake questions covering fee structure, data handling, ML rights, implementation services, and more. Applies 18 always-on defaults that transform the raw YC form into a professional starting point (renamed to "Customer Agreement", data privacy section added, warranty restructured, consolidated SLA/support exhibit, etc.). Produces a clean .docx and a lawyer-facing memo explaining every change from the YC standard. Use when user says "draft a SaaS agreement", "YC SaaS", "startup SaaS contract", "customer agreement", "SaaS subscription agreement", or "I need a SaaS agreement starting from the YC form". Also trigger when the user is a startup founder discussing SaaS contracting, even if they don't mention YC specifically.
日本語の概要は準備中です。原文の説明を表示しています。