2,059 件 ・ 関連度順
概要と使いどころ
Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.
日本語の概要は準備中です。原文の説明を表示しています。
Initialise a project for knowledge base use. Appends the [Knowledge Base] section to the project's CLAUDE.md, creates the library/ directory structure, optionally seeds with three example library files from the Agentic SDLC research, and reports next steps. Run once after installing sdlc-knowledge-base.
日本語の概要は準備中です。原文の説明を表示しています。
Mock skill shipped by the sample bundle for installer testing
日本語の概要は準備中です。原文の説明を表示しています。
Manage the project's layer vocabulary — list allowed layers with file counts, add new layers, or safely remove unused layers. Reads the shelf-index for usage data; writes CLAUDE.md atomically. No agent dispatch.
日本語の概要は準備中です。原文の説明を表示しています。
Apply React and Next.js performance optimization guidelines from Vercel Engineering — 40+ rules covering components, data fetching, bundle optimization, and rendering. Triggers on React components, Next.js pages, bundle optimization, performance improvements, refactoring React code.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Claude Code の SubAgent（agents/*.md）を正しく定義するためのベストプラクティスガイド。 YAML frontmatter、ツール選択、3-Phase 構造、コンテキスト受け渡し、アンチパターンを網羅。 Use when: agents/*.md を書く、SubAgent 定義を改善する、エージェントの動作が想定外、 コンテキストが渡らない、ツール選択に迷う。 Triggers: "subagent", "agent definition", "agents/*.md", "エージェント定義", "サブエージェント", "3-Phase", "context passing", "コンテキスト渡し", "tool selection", "ツール選択", "subagent_type", "bypassPermissions"
Assess and improve garden soil through testing, amendment, composting, and biodynamic preparations. Covers jar test, spade test, earthworm count, amendment by soil type (clay, sandy, depleted, compacted), composting methods (hot, cold, vermicomposting), no-till practices, cover cropping, and biodynamic preparations 500-508. Use when starting a new garden bed, when plants underperform despite adequate water and light, when transitioning to organic or biodynamic practice, when soil has become compacted or depleted, or when building a composting system.
日本語の概要は準備中です。原文の説明を表示しています。
Purify water from wild sources using boiling, filtration, and chemical methods. Covers source assessment and priority ranking, sediment pre-filtering, method selection (boiling, chemical, UV, filter), altitude-adjusted boiling procedure, chemical treatment dosages, and safe storage practices. Use when needing drinking water in a wilderness setting, when available water sources are of unknown quality, in an emergency survival situation where dehydration is a risk, or when making water safe for cooking or wound cleaning.
日本語の概要は準備中です。原文の説明を表示しています。
Preserve and conserve library and archival materials. Covers environmental controls (temperature, humidity, light), handling procedures, book repair techniques (torn pages, loose spines, foxing), acid-free storage, digitization for preservation, and disaster recovery planning. Use when establishing preservation practices for a new or existing collection, when materials show signs of deterioration, when setting up environmental controls for storage, when planning digitization to preserve fragile originals, or when creating a disaster recovery plan for a library or archive.
日本語の概要は準備中です。原文の説明を表示しています。
Implement cloud cost optimization strategies for Kubernetes workloads using tools like Kubecost for visibility, right-sizing recommendations, horizontal and vertical pod autoscaling, spot/preemptible instances, and resource quotas. Covers cost allocation, showback reporting, and continuous optimization practices. Use when cloud costs are growing without proportional business value, when resource requests are misaligned with actual usage, when manual scaling leads to over-provisioning, or when implementing showback and chargeback for internal cost accountability.
日本語の概要は準備中です。原文の説明を表示しています。
Organize, track, and value a trading card game collection. Covers inventory methods, storage best practices, grade-based valuation, want-list management, and collection analytics for Pokemon, MTG, Flesh and Blood, and Kayou cards. Use when starting a new collection and setting up inventory tracking, cataloging an existing collection that has grown beyond casual knowledge, valuing a collection for insurance or sale, or deciding which cards to submit for professional grading based on value potential.
日本語の概要は準備中です。原文の説明を表示しています。
Alluvial gold recovery using panning, sluicing, and classification. Covers site reading (geological indicators, stream dynamics, pay streak location), panning technique, sluice box operation, and responsible extraction practices. Use when prospecting in an area with known or suspected alluvial gold deposits, sampling a stream to test for gold presence, maximizing recovery during recreational panning, or assessing a site's gold potential before investing more effort.
日本語の概要は準備中です。原文の説明を表示しています。
Identify and safely gather edible and useful wild plants. Covers safety rules and deadly plant recognition, habitat reading, multi-feature identification methodology, the universal edibility test, sustainable harvesting practices, preparation methods, reaction monitoring, and building knowledge with beginner-friendly universal species. Use when supplementing food supply in a wilderness or survival setting, needing medicinal or utility plants, identifying plants around camp for safety, or in long-term scenarios where foraging extends available rations.
日本語の概要は準備中です。原文の説明を表示しています。
Establish Service Level Objectives (SLO), Service Level Indicators (SLI), and Service Level Agreements (SLA) with error budget tracking, burn rate alerts, and automated reporting using Prometheus and tools like Sloth or Pyrra. Use when defining reliability targets for customer-facing services, balancing feature velocity against system reliability through error budgets, migrating from arbitrary uptime goals to data-driven metrics, or implementing Site Reliability Engineering practices.
日本語の概要は準備中です。原文の説明を表示しています。
Evolve an existing agent definition by refining its persona in-place or creating an advanced variant. Covers assessing the current agent against best practices, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes to skills, tools, capabilities, and limitations, updating version metadata, and synchronizing the registry and cross-references. Use when an agent's skills list is outdated, user feedback reveals capability gaps, tool requirements have changed, an advanced variant is needed alongside the original, or the agent's scope needs sharpening after real-world use.
日本語の概要は準備中です。原文の説明を表示しています。
Doctrine ORM best practices for Symfony: entity mapping as source of truth, repositories, DQL/QueryBuilder with parameters, N+1 prevention with fetch joins, relations (cascade/fetch/orphanRemoval), lifecycle events, batch processing, and generated migrations. Apply when: writing or reviewing Doctrine entities, repositories, and queries. Activated automatically by symfony-plugin/stack.md as a convention skill for the development and database phases. Do NOT use this skill for: - PHP language idioms — see php-foundation:php-conventions. - Controllers/services/forms — see symfony-plugin:symfony-conventions.
日本語の概要は準備中です。原文の説明を表示しています。
pytest testing patterns for any Python project: test structure, fixtures, parametrize, conftest.py, monkeypatch, tmp_path, markers, unittest.mock (MagicMock, patch), pytest-cov coverage, and best practices. Stack-agnostic — referenced by every Python plugin in the marketplace. Use this skill to: - Organise tests with conftest.py shared fixtures and a clear test/src layout. - Write parametrized tests to cover multiple inputs without duplication. - Mock external dependencies (HTTP, DB, filesystem) with unittest.mock and monkeypatch. - Measure and enforce code coverage with pytest-cov. Do NOT use this skill for: - Framework-specific test types (Django TestCase / WebTestCase, FastAPI TestClient, Flask test client — see framework plugin skills). - Language idioms — see python-foundation:python-conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Eloquent ORM best practices: query builders, scopes, relations, N+1 prevention, batch operations, soft deletes, model events, raw queries when needed. Apply when: writing or reviewing Eloquent queries and model interactions. Activated automatically by laravel-plugin/stack.md as a convention skill for the development phase.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Use when C code is written or audited and needs a pure-C baseline: standard, undefined behavior, integer and buffer safety, sanitizers, fuzzing, build flags. Not for C++: use modern-cpp-practices.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user, especially a new hire, asks for mentoring, guidance, or explanation of infrastructure or engineering practices. Not for code changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, editing, cleaning, or refactoring Tailwind classes, components, or configuration. Not for read-only audits of Tailwind code, or general CSS without Tailwind.
日本語の概要は準備中です。原文の説明を表示しています。
Use when modeling a domain, encoding a state machine, hardening APIs, making invalid states unrepresentable, or parsing instead of validating. Not for TypeScript: use typescript-best-practices.
日本語の概要は準備中です。原文の説明を表示しています。