「existing」の検索結果

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

Start a project on the Visual Stack — a multi-step setup form captures what's being built, recommends a stack, and either instantiates the vstack-template-base template, sets up a specs-and-design-only workspace, or records an existing codebase without touching it. Use when the user wants to start a new project, scaffold a repo, set up a codebase from the Cavalry template, pick a stack or add-ons, run Day-1 setup, or bring an existing app onto the visual stack.

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

Build pages using ONLY existing atomic-design components. REQUIRES atomic-design skill. Use for composing pages, creating views/features from existing components.

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

Build an evidence-backed working model of an existing codebase. Use when you must orient in a large or unfamiliar repository; explain architecture or a subsystem; trace a request, runtime, control, or data flow for a concrete question or bug; analyze a branch, commit, diff, or pull request for behavioral impact and blast radius; or assess AI-generated or changed code against requirements, contracts, invariants, tests, and runtime evidence. Default to read-only investigation. Do not trigger only because a coding task touches an existing repository; use when understanding or verification is the requested outcome or a substantial prerequisite.

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

Initialize a new Convex project from scratch or add Convex to an existing app. Use when starting a new project with Convex, scaffolding a Convex app, or integrating Convex into an existing frontend.

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

Draft edits to existing specs (or a new spec if no existing one fits) from the card description

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

新しいプロジェクトまたは既存リポジトリに Claude 用の kickoff 文脈を導入するスキル。 テンプレートとリポジトリ証跡、ユーザー入力をもとに `CLAUDE.md`、`docs/PROJECT_BRIEF.md`、 `docs/SKILL_ROUTING.md`、`docs/QUALITY_GATES.md`、`docs/TEST_STRATEGY.md`、 `docs/DECISION_LOG.md`、`docs/HIDDEN_CONTRACT_REGISTER.md`、 `docs/CROSS_MODULE_CONSISTENCY_MATRIX.md`、`.claude/rules/*`、 `.claude/commands/project-kickoff.md` を必要に応じて作成・更新する。 Use when starting a new project, retrofitting AI project context into an existing repository, bootstrapping Claude memory, or standardizing kickoff documents, rules, and slash-command scaffolding. Distinct from project-manager / project-plan-creator (which plan work), and from completion-quality-gate-designer / hidden-contract-investigator / safe-by-default-architect / cross-module-consistency-auditor / production-parity-test-designer (which deeply refine individual artifacts after bootstrap).

既存コード・既存関数・既存モジュールの暗黙契約を抽出するスキル。 戻り値型、副作用、例外、前提条件、境界条件、環境依存挙動を確認し、 reuse前のリスクを可視化する。名前やコメントではなく実際の挙動から 契約を読み取り、不一致を分類し、再利用可否を判定する。 Use when reusing legacy code, verifying actual behavior of existing functions, or extracting implicit contracts before implementation. Covers: hidden contract, implicit contract, reuse risk, legacy behavior, 暗黙契約, 既存資産調査. Analyzes return types, side effects, exceptions, preconditions, boundary conditions, and environment-dependent behavior.

Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).

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

Use when adding a test to an existing codebase for behavior that is already implemented. Ensures the test is meaningful by mutation-verifying it — breaking the production code to confirm the test fails for the expected reason. Triggers when the user says "add a test for existing behavior", "backfill test coverage", "the test passes on first run", or any scenario where a test is written without a corresponding new production change.

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

Structured 6-step procedure for improving, renovating, or rebuilding existing pipelines, individual project folders, documentation structures, or software stacks. Addressable as "pipeline optimizer" (for whole topic pipelines, e.g. a software, research, or game-dev pipeline) or "project-folder optimizer" (for individual project folders within a pipeline, e.g. a single software tool or paper project). Triggers on tasks like "improve pipeline X", "optimize the stack", "rebuild Y", "renovation", "pipeline refactoring", "clean up project folder", "improve folder structure", "unify conventions", "documentation consolidation", "integrate into existing system", or any substantial intervention in established structures. Delivers building-stock analysis, purpose clarification, ideal sketch, gap plan, empirical pain-point identification, and retests with fresh subagents. Prevents parallel standards, duplication, and pipeline breaks.

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

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.

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

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

Given the product offering and existing page inventory, create new core landing and resource pages (homepage refresh, features, solutions, pricing, comparison, resource hubs, about) that capture core product intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn pages", "generate landing pages", "create marketing pages", "build a pricing page", "add a solutions page", "build out the site", "fill in missing pages", or wants new top-level marketing/product pages. Output is one new page per route in the project's native file format (component or markdown), matching the existing page style and framework idiom.

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

Evaluate and improve an existing Claude Code skill using explicit success criteria and small controlled changes. Use when the user asks to optimize a skill, reduce over-triggering or under-triggering, improve reliability, tighten instructions, or add evals for a skill. Also trigger on "スキルを改善して", "スキルを最適化して", "スキルの品質を確認して".

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

Design a test strategy around product risk, business invariants, failure modes, and existing controls, deciding what deserves testing and at which boundary rather than maximising coverage. Use whenever the user asks how to test something, wants a test plan or strategy, is deciding between unit/integration/contract/E2E/property/concurrency testing, or wants to know whether existing tests actually protect what matters. Prefer this over writing tests immediately. Part of the audit suite; inherits the shared constitution while its own job is proving risk coverage.

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

Marp形式プレゼンテーションの専門レビュー・評価・改善スキル。 10軸スコアリング（100点満点）で品質を定量評価し、具体的な改善コード付きで提案する。 Use when the user asks to: - Review, evaluate, or critique a Marp presentation / プレゼンをレビュー / 評価 / 添削 - Improve, polish, or upgrade existing slides / スライドを改善 / ブラッシュアップ - Check slide quality, score slides, or audit a deck / スライドの品質チェック / 採点 - "このプレゼンどう？" "スライドを見てほしい" "プレゼン資料のフィードバック" Reads .md files with Marp frontmatter, scores across 10 dimensions, and outputs a detailed review report with concrete before/after code improvements. Works as a companion to the marp-slides skill (generation → review → improvement cycle).

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

Validates custom dotnet new templates for correctness before publishing. Catches missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes that cause templates to fail silently. USE FOR: checking template.json files for errors before publishing or testing, diagnosing why a template doesn't appear after installation, reviewing template parameter definitions for type mismatches and missing defaults, finding shortName conflicts with dotnet CLI commands, validating post-action and constraint configuration. DO NOT USE FOR: finding or using existing templates (use template-discovery), creating projects from templates (use template-instantiation), creating templates from existing projects (use template-authoring).

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

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding or comparing templates (use template-discovery), authoring custom templates (use template-authoring), modifying existing projects or adding NuGet packages to existing projects.

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

Analyze and improve existing Ozor.ai video prompts for better output quality. Use this skill whenever the user has an Ozor prompt that produced mediocre results, wants to improve a video prompt, needs help debugging why a video didn't turn out well, or wants expert feedback on their prompt before running it. Trigger on phrases like 'improve this prompt', 'optimize my Ozor prompt', 'why did my video look bad', 'fix this prompt', 'make this prompt better', 'review my Ozor prompt', 'the video didn't turn out right', 'prompt feedback', 'better results from Ozor', or any request to refine, debug, or enhance an existing Ozor video prompt.

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

Use when the team lead points Architect at a prior agistra.dev hub path and asks it to check for or perform additional migration — trigger phrasing such as 'migrate my data from <path>', 'check what didn't get migrated', 'did we miss anything from my old hub', or 'do a completeness pass on <path>'. Walks the prior hub's full directory tree read-only, diffs it against the fixed scripted migration scope plus any existing migration report, and asks the team lead one clear question at a time about anything a scripted migration would never have discovered. Never writes or copies anything itself — every confirmed item is delegated to the existing migration primitives. Do not use for the first-run scripted migration prompt during `npm run setup` — that is unrelated, already-automated flow this skill does not replace.

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