「writing」の検索結果

Use when you need to apply functional programming principles in Java — including writing immutable objects and Records, pure functions, functional interfaces, lambda expressions, Stream API pipelines, Optional for null safety, function composition, higher-order functions, pattern matching for instanceof and switch, sealed classes/interfaces for controlled hierarchies, Stream Gatherers for custom operations, currying/partial application, effect boundary separation, and concurrent-safe functional patterns. This should trigger for requests such as Improve the code with Functional Programming; Apply Functional Programming; Refactor the code with Functional Programming; Refactor Java code to use streams or Optionals safely; Improve immutability and pure functions in Java. Part of Plinth Toolkit

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

Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should trigger for requests such as Apply TDD; Use test-driven development; Drive this Java change with tests; Write the failing test first; Red-green-refactor this feature. Part of Plinth Toolkit

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

Create, repair, audit or consolidate agent skills (SKILL.md packages). Use when: writing or fixing a skill, its description or structure. Not for one-off lessons; use Memory.

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

Write or update READMEs, docs, repo instructions and handoff notes, checked against source. Use when: documenting something, writing a README or leaving a session handoff.

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

Write or assess tests that prove behavior and would fail without the fix. Use when: writing tests, TDD, or asked whether a green test is enough.

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

Writes, reviews, and improves SwiftData code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use SwiftData.

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

Remove AI-generated jargon and restore human voice to text. Built from analyzing 1,000+ AI vs human content pieces.

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

Shell scripting best practices and patterns. Use when writing bash/zsh scripts, automating tasks, creating CLI tools, or debugging shell commands.

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

Project-wide coding standards and conventions specialist. Use PROACTIVELY when writing code, making architectural decisions, or establishing project conventions. Covers coding style, commenting, error handling, validation, tech stack consistency, and project conventions across all languages and frameworks.

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

Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.

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

Create and validate YAML diagram files. Use when writing new diagrams or troubleshooting YAML syntax.

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

React 19 and TypeScript coding standards for Portfolio Buddy 2. Use when: writing new components, reviewing code, refactoring, or ensuring consistency. Contains component patterns, TypeScript rules, and best practices.

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

Iterative worker-reviewer cycle that spawns a critic subagent to score work 1-10 and provide actionable feedback, then revises until a quality gate is met. Use when implementing features, writing specs, reviewing existing code, or completing any task where quality matters more than speed. Trigger phrases: "use review-loop", "polish this", "iterate on this", "/review-loop", "review with feedback loop".

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

Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.

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

This skill should be used when writing tests, validating features, or needing to verify code works. Triggers on "write tests", "add test coverage", "validate feature", "integration test", "end-to-end", "e2e test", "mock", "unit test". Enforces scenario-driven testing with real dependencies in .scratch/ directory.

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

PostgreSQL database documentation - SQL queries, database design, administration, performance tuning, and advanced features. Use when working with PostgreSQL databases, writing SQL, or managing database systems.

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

Trigger for: writing, revising, converting, or descoping a federal Statement of Work, Performance Work Statement, SOW, PWS, or SOO; develop executable requirements; define contract scope; create measurable performance standards; or prepare requirements before an IGCE. Produce a contract-file-ready .docx plus separate chat-only staffing and Section B handoffs. Never place FTEs, SOC codes, staffing estimates, IGCE content, CLINs, or pricing schedules inside the SOW/PWS body. Do NOT use for the IGCE, market research report, acquisition plan, QASP, or clause-selection matrix.

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

Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).

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

Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.

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

Use when reading or writing TypeScript or JavaScript files (.ts, .tsx, .js, tsconfig.json).

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

Use when reading or writing Go files (.go, go.mod).

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

Use when reading or writing React components (.tsx, .jsx files with React imports).

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Use when reading or writing Python files (.py, pyproject.toml, requirements.txt).

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