Technical Writing

Use when refining an architecture or design document based on new learnings, before a rewrite. Use when you have an existing doc and related docs to cross-check against. Use when you need systematic section-by-section validation of decisions.

Comprehensive code documentation standards and guidelines for maintaining up-to-date documentation across Python, HTML, CSS, and JavaScript codebases. Use when creating or modifying code to ensure proper documentation practices and maintainable code.

Enhanced documentation unified validation with AI-powered features

Autonomous agent creation skill that generates specialized agent definitions from templates. Use when you need to create new Claude Code agents for specific tasks like code review, deployment automation, testing, documentation, security analysis, or general-purpose research. This skill automates the creation of agent definition files (.md) with proper structure, workflow instructions, and tool access patterns following Miyabi framework standards.

Creates comprehensive ServiceNow change request documentation when users request CR creation, need to generate change requests, ask to prepare deployment documentation, or mention creating release documentation. Automatically analyzes git history, queries functional requirements from BigQuery, generates technical change summaries, and creates properly formatted YAML files for L'Oréal BTDP deployments.

Canonical Claude Code skill authoring kit covering agent Skills, sub-agent templates, custom slash commands, orchestration patterns, hooks, memory, settings, and IAM permission rules aligned with official documentation.

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

This skill should be used when creating Galaxy Hub news posts, writing content for galaxyproject.org/news, or converting content to Galaxy Hub markdown format.

Write strategic, behavior-focused tests for core user flows and critical functionality using Vitest for unit tests and Playwright for end-to-end testing. Use this skill when writing test files, testing utilities, or implementing test coverage for critical paths. When working on Vitest test files (.test.ts, .spec.ts), Playwright E2E test suites, test setup and configuration files (vitest.config.ts, test-setup.ts), mock implementations for external dependencies, testing utility functions or test helpers, component test files using React Testing Library, API route test files, or integration tests for Content Collections and data fetching logic.

"Am I *doing* or just *describing* that I should do?" - Counters documentation-over-action patterns. Triggers when: (1) about to say "should create", "need to fix", "I recommend" instead of acting, (2) end of work blocks before reporting completion, (3) reporting success while failures exist, (4) creating docs/plans without executing, (5) explaining fixes instead of implementing. Enforces ACT FIRST, DOCUMENT AFTER. Does NOT trigger for: genuine planning phases, user-requested documentation, or blocked situations requiring input.

CSS/XPath selector best practices for web automation (dropdowns, dynamic tables, nested components). Use when: writing selectors, handling dynamic content, React apps, robust attributes, dynamic element handling, selector maintenance.

Implement robust error handling with user-friendly messages, specific exception types, centralized error boundaries, and graceful degradation strategies. Use this skill when writing try-catch blocks, handling exceptions and errors, creating error messages for users, implementing error boundaries in React or other frameworks, validating input and checking preconditions, handling API errors and external service failures, implementing retry strategies with exponential backoff, cleaning up resources in finally blocks, designing graceful degradation for non-critical failures, or preventing technical details and security information from being exposed to users. Apply this skill when handling errors in any code file, implementing error recovery mechanisms, or reviewing error handling approaches for robustness and security.

Use when migrating skills between repositories or extracting skills from a project into a reusable form. Handles copying, cleanup of project-specific references, and genealogy documentation.

Apply SQL optimization patterns including index usage, query rewriting, JOIN optimization, and window functions. Use when improving query performance or analyzing slow queries. This skill provides comprehensive SQL optimization patterns and best practices: - N+1 query elimination - Index optimization strategies - JOIN vs subquery performance - Window functions for complex aggregations - Query execution plan analysis Triggers: "optimize SQL", "slow query", "improve performance", "SQL最適化", "クエリ改善", "パフォーマンス向上"

Expert knowledge for Technology Layer modeling in Documentation Robotics

Comprehensive TypeScript best practices including type imports, security patterns, code structure, and early returns. Use when writing TypeScript code, reviewing for quality, implementing error handling, or ensuring type safety.

Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.

Patterns for writing effective, maintainable tests

AndroidアプリのセキュリティレビューをOWASP Mobile Top 10 2024およびMASVS (Mobile Application Security Verification Standard) の観点で実施し、Markdownレポートを生成する。 Use when: (1) Androidアプリのセキュリティ監査/レビュー依頼時 (2) 「セキュリティチェック」「脆弱性診断」「OWASP」「MASVS」キーワード時 (3) Androidプロジェクトのコードレビューでセキュリティ観点が必要な時 (4) 金融・医療アプリのセキュリティ評価時

Transform project ideas into requirements documentation focusing on user outcomes and functionality, not implementation. Use when partner describes a new project or feature idea and needs a PRD capturing requirements before implementation, when unclear what to build but not yet ready for technical planning