「naming」の検索結果

How to write a Grafema batch-mode plugin that reads the graph and filesystem, then writes new edges/nodes directly to RFDB. Use when: (1) need to add project-specific edges that generic analyzers can't produce, (2) need to read config files (JSON/YAML) and trace values into code, (3) implementing framework-specific resolvers (Django settings, Express routes, pipeline configs). Covers: grafema.config.yaml plugin config, RFDB field naming (src/dst NOT source/target), addEdges/addNodes API, RFDBServerBackend connection pattern.

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

Code quality guidelines and best practices for writing clean, maintainable code. Covers naming, structure, error handling, testing, and code review standards. Use when writing code, reviewing, refactoring, or asking "how should I name this", "best practice for", "clean code".

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

Correct naming for a PR

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

Go code refactoring with automated tools: gofmt -r, gopatch, and rsc.io/rf. Use this skill when performing mechanical rewrites across a codebase — renaming identifiers, migrating API calls, moving types between packages, rewriting expressions, or replacing deprecated patterns. Triggers when the task involves bulk code transformation, API migration, structural rewrite, or the user mentions gofmt -r, rf, gopatch, coccinelle-style patching, or large-scale rename/move in Go.

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

Run the Upstash CLI (`upstash`) from a terminal, shell script, or CI job when no Upstash MCP tools are in the session. Do not load this skill when Upstash MCP tools are available (the Upstash plugin registers mcp.upstash.com) - they already cover creating, listing, renaming, and deleting Redis databases, running Redis commands, usage stats, backups, Vector and Search indexes, QStash schedules and messages, Blob buckets, and Box, so call them directly. Use this skill for shell work the MCP does not do - a CI step or provisioning script that needs `upstash` commands with JSON output, piping results into other commands, `upstash auth login` and API-key setup, team and member management, changing plans, regions, TLS, eviction, auto-upgrade, or budgets, minting temporary S3 credentials for a Blob bucket, connecting a coding agent to Upstash with `upstash setup` (the Upstash plugin, or the remote MCP server plus skills), or when the user explicitly asks for the CLI or for managing Upstash without the console.

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

Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.

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

Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema, payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed.

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

Use this skill whenever the user wants to use AI agents to work with Penpot design files via the Penpot MCP Server. Triggers include: using Penpot through an AI agent, design files, design systems, design tokens, Penpot MCP, design-to-code, generating UI from design, auditing a design system, creating components/variants, renaming layers, exporting assets from Penpot, adding flows, interactions, animations, overlays, or prototyping in Penpot, or prompting an AI agent to read/modify a Penpot file. Also triggers when the user wants to set up Penpot MCP, connect any MCP-compatible AI agent or IDE to Penpot, or produce production-ready HTML/CSS/React from a Penpot design. Use this skill for Penpot-agent workflows — design, code, audit, prototyping, or setup.

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

Generates Claude Code plugin agent .md files: writes YAML frontmatter (name, model, color, tools, hooks, disallowedTools), crafts system prompts, and creates triggering example blocks with context and commentary. Validates agent structure against naming, length, and format constraints. Use when the user asks to create an agent, add an agent, write a subagent, configure agent frontmatter, design agent system prompts, set agent tools or colors, build an autonomous agent, or add agent hooks.

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

Develops comprehensive threat actor profiles for APT groups, criminal organizations, and hacktivist collectives by aggregating TTP documentation, historical campaign data, tooling fingerprints, and attribution indicators from multiple intelligence sources. Use when briefing executives on sector-specific threats, updating threat model assumptions, or prioritizing defensive controls against specific adversaries. Activates for requests involving MITRE ATT&CK Groups, Mandiant APT profiles, CrowdStrike adversary naming, or sector-specific threat briefings.

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

Lightweight design smell review for modules and APIs—coupling, cohesion, naming, boundaries, and unnecessary complexity. Use before large refactors or when code feels hard to change. Complements gstack/review (diff-focused).

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

"Apply BCG Growth-Share Matrix to analyze a product or business unit portfolio for resource allocation decisions. Use this skill when the user needs to prioritize investments across multiple products, decide which products to grow vs harvest vs divest, or evaluate a portfolio's balance — even if they say 'which products should we invest in' or 'portfolio strategy' without naming BCG.".

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

"Apply Porter's Five Forces framework to assess industry competitive dynamics and attractiveness. Use this skill when the user needs to analyze an industry's profitability structure, evaluate market entry barriers, assess supplier or buyer bargaining power, or understand competitive intensity — even if they say 'industry analysis' or 'is this market worth entering' without naming Porter's explicitly.".

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

"Conduct SWOT analysis with TOWS matrix for strategic planning. Use this skill when the user needs to evaluate a company, product, or project by identifying strengths, weaknesses, opportunities, and threats, or wants to generate strategic options from internal and external factors. Also use when the user mentions competitive positioning, strategic assessment, or asks 'what are our advantages and risks', even without naming SWOT explicitly.".

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

Design agent tools and CLI surfaces—schemas, naming, errors, idempotency, and discoverability for LLM callers. Use when defining tools for agents, SDKs, or AI-native CLIs.

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

Claude-native review of code for quality, structure, naming, and maintainability (no external AI). Use when reviewing a file or diff for code quality before committing. Trigger on "review this code", "code review", "is this well-written". For security, use /security-verify; for companion-AI review, use /review.

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

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

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

Use when writing or reviewing tests, designing test data, naming a test, choosing what to assert, or writing test helpers/mocks/fixtures

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

Use when writing or reviewing functions, classes, naming, or non-trivial logic (≥3 lines)

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

Use when introducing, reviewing, or renaming a top-level type, table, or domain concept; or choosing where state lives (in-memory vs persistent)

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

Frappe DocType creation and form UX guidance. Use when creating, reviewing, or redesigning DocTypes, including field choice, tabs, sections, columns, required fields, naming, child tables, and form usability.

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

Design token architecture - primitive/semantic/component tiers, naming grammar, CSS custom property delivery, and DTCG build pipelines

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

Turborepo, workspaces, package architecture, @repo/* naming, exports, tree-shaking

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

Use when creating or editing Storybook stories (*.stories.tsx, React or React Native) — story layout, docs source type, controls, and export naming conventions.

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